unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Michael Pagan <pegzmasta@member.fsf.org>
Cc: 35725@debbugs.gnu.org
Subject: bug#35725: 26.2; Fatal error 11: Segmentation fault; Crash on: (find-file "any.svg")
Date: Mon, 13 May 2019 18:04:58 -0700	[thread overview]
Message-ID: <1ac79901-d3a1-3c3f-1590-d3fc753e4bac@cs.ucla.edu> (raw)
In-Reply-To: <87zhnq567e.wl-pegzmasta@member.fsf.org>

Thanks for the bug report. I don't see the problem with Emacs 26.2 on my
platform (Fedora 30, x86-64, configured with './configure --with-xft
--with-x-toolkit=gtk3 --without-rsvg'.

I suggest configuring --with-rsvg, so that librsvg used (instead of
ImageMagick) to display SVG files. I vaguely remember proposing that we
disable ImagicMagick by default; perhaps we should get around to doing
that. ImageMagick is a continuing source of bugs.

If librsvg doesn't fix the problem, please follow the instructions in
etc/DEBUG to build a debugging version of Emacs that will give you a
decent backtrace.






  reply	other threads:[~2019-05-14  1:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 22:40 bug#35725: 26.2; Fatal error 11: Segmentation fault; Crash on: (find-file "any.svg") Michael Pagan
2019-05-14  1:04 ` Paul Eggert [this message]
2019-05-14  1:21   ` Glenn Morris
2019-05-14  3:59     ` Michael Pagan
2019-05-14  7:58       ` Lars Ingebrigtsen
2019-05-14  8:00         ` Lars Ingebrigtsen
2019-05-14 16:04         ` Eli Zaretskii
2019-05-14 16:16           ` Paul Eggert
2019-05-15  0:49             ` Lars Ingebrigtsen
2019-05-15 18:45               ` Alan Third
2019-05-16  3:47                 ` Lars Ingebrigtsen
2019-05-14  6:08     ` Paul Eggert
2019-05-15  0:42       ` Glenn Morris
2019-05-18 17:12         ` Paul Eggert
2019-05-15  4:07       ` Michael Pagan
2019-05-15  4:22         ` Lars Ingebrigtsen
2019-05-14  1:16 ` Noam Postavsky
2019-05-14 15:25   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1ac79901-d3a1-3c3f-1590-d3fc753e4bac@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=35725@debbugs.gnu.org \
    --cc=pegzmasta@member.fsf.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).