After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 149916 - Nautilus crashes when rendering SVG files
Nautilus crashes when rendering SVG files
Status: RESOLVED DUPLICATE of bug 122141
Product: librsvg
Classification: Core
Component: general
unspecified
Other other
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-08-11 15:27 UTC by denis
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description denis 2004-08-11 15:28:11 UTC
From: Denis Fernandez Cabrera <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.4.0
Subject: Nautilus crashes when rendering SVG files

Distribution: Fedora Core release 1 (Yarrow)
Package: librsvg
Severity: critical
Version: GNOME2.4.0 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: Nautilus crashes when rendering SVG files
Bugzilla-Product: librsvg
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:

If you have one window of the Nautilus file manager open while working
with an SVG editor (Inkscape or Sodipodi), saving the document in these
results in a nautilus crash. It seems pretty obvious that the program
has trouble rendering SVGs when the files are updated "on-the-fly".

Steps to reproduce the crash:
1. Open a Nautilus window, select your preferred folder.
2. Using the Inkscape SVG editor, create a SVG file and save it in the
folder that Nautilus is displaying.
3. That's it. Nautilus should crash at the moment you press ctrl-s in
Inkscape.

Expected Results:

Just a crash. Nautilus shuts down.

How often does this happen?

Every time you save a SVG file in a folder being displayed by Nautilus.

Additional Information:

I'm not really sure wether this bug relates to librsvg, but it is
likely.

¿Why is this bug critical? Well, this valoration is subjective, of
course. But, in my context (I'm using GNU/Linux for graphic design),
each time that Nautilus crashes (that is, every time I save a file) I
have to stop and reopen it. This is adds an incredible lag to working
speed.

Additionally, I have also found the same (?) bug without using any
vector editor -- just entering a folder with svg files. This seems to
happen much more randomly than the other one, so I don't know how to
reproduce it.

Debugging Information:

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[Thread debugging using libthread_db
enabled]
[New Thread -1084995648 (LWP 6553)]
[New Thread -1088119888 (LWP 6558)]
[New Thread -1087853648 (LWP 6557)]
[New Thread -1087587408 (LWP 6556)]
[New Thread -1087321168 (LWP 6555)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x0096cc32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 1 (Thread -1084995648 (LWP 6553))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #5 raise
    from /lib/tls/libc.so.6
  • #6 abort
    from /lib/tls/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 nautilus_icon_container_move_icon
    from /usr/lib/libnautilus-private.so.2
  • #10 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-11 11:28 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "librsvg".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was denis@glug.es.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Dominic Lachowicz 2004-08-11 15:38:59 UTC
re-assigning this to nautilus until we get some further information. strongly
recommend that the user upgrade to librsvg 2.8.0 when it becomes available.
Comment 2 Dominic Lachowicz 2004-08-11 15:39:31 UTC
really reassign...
Comment 3 Vincent Noel 2004-08-11 15:42:45 UTC
The stack trace matches the one in bug 145669, which has been marked as a dup of
bug 122141.

*** This bug has been marked as a duplicate of 122141 ***