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 456184 - Fedora crash: '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory
Fedora crash: '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory
Status: RESOLVED DUPLICATE of bug 439977
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 457811 457813 487972 488078 488379 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-07-12 10:21 UTC by vbjester
Modified: 2007-10-21 14:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description vbjester 2007-07-12 10:21:28 UTC
Version: 2.18.3

What were you doing when the application crashed?
J'ai défini sur 0,1 le temps (en minutes) entre le changement de papier-peint (avec un applet de changement de papier-peint pour Gnome), donc il y a eu 250000 messages qui se sont affichés les uns après les autres (super vite) pour m'indiquer que le papier-peint allait être changé...  La boulette... Et les messages continuent à s'afficher au moment où j'écris ce message  :D   Bon allez je vais tenter d'arrêter le processus à la main :)   Bonne journée


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 122806272 vsize: 122806272 resident: 58699776 share: 35749888 rss: 58699776 rss_rlim: 4294967295
CPU usage: start_time: 1184230664 rtime: 2110 utime: 1896 stime: 214 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208764704 (LWP 3227)]
(no debugging symbols found)
0x00425402 in __kernel_vsyscall ()

Thread 1 (Thread -1208764704 (LWP 3227))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnome-desktop-2.so.2
  • #5 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnome-desktop-2.so.2
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnome-desktop-2.so.2
  • #7 gnome_bg_create_pixmap
    from /usr/lib/libgnome-desktop-2.so.2
  • #8 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libeel-2.so.2
  • #9 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libeel-2.so.2
  • #10 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libeel-2.so.2
  • #11 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #13 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #16 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libeel-2.so.2
  • #17 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #22 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnome-desktop-2.so.2
  • #23 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libeel-2.so.2
  • #24 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libeel-2.so.2
  • #25 ??
  • #26 ??
  • #27 g_cclosure_marshal_VOID__ENUM
    from /lib/libglib-2.0.so.0
  • #28 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #29 g_cclosure_marshal_VOID__ENUM
    from /lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #31 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (21 sec old) ---------------------
warning: .dynamic section for "/usr/lib/libtiff.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libstdc++.so.6" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libhal.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 palfrey 2007-07-12 11:43:32 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!
Comment 2 André Klapper 2007-07-18 15:54:28 UTC
*** Bug 457811 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2007-07-18 15:54:43 UTC
*** Bug 457813 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2007-07-18 15:55:44 UTC
(nautilus:2935): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file
'/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory

Thanks for taking the time to report this bug.
Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] If you use Fedora, please install the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo.

More details can be found here: http://live.gnome.org/GettingTraces
Comment 5 André Klapper 2007-10-19 18:35:34 UTC
*** Bug 487972 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2007-10-19 18:35:38 UTC
*** Bug 488078 has been marked as a duplicate of this bug. ***
Comment 7 André Klapper 2007-10-19 18:35:42 UTC
*** Bug 488379 has been marked as a duplicate of this bug. ***
Comment 8 André Klapper 2007-10-21 14:22:16 UTC
this is the same issue as bug 439977 and fedora7-specific.

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