GNOME Bugzilla – Bug 484105
crash in Open Folder:
Last modified: 2008-01-23 06:13:35 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: gnome Memory status: size: 77840384 vsize: 77840384 resident: 25382912 share: 12943360 rss: 25382912 rss_rlim: 4294967295 CPU usage: start_time: 1191641359 rtime: 1032 utime: 939 stime: 93 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c649f0 (LWP 4603)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 168301
Thread 1 (Thread 0xb6c649f0 (LWP 4603))
----------- .xsession-errors --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) warning: .dynamic section for "/usr/lib/libfam.so.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 484115 has been marked as a duplicate of this bug. ***
I can consistently reproduce this bug by right clicking on a gif image and select Properties, I don't have any problems when I do the same on a png image. This is the stack traces after installing gnome-dbg, it only has a little more info but I hope it helps. ====================== Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: gnome Memory status: size: 73207808 vsize: 73207808 resident: 25112576 share: 14020608 rss: 25112576 rss_rlim: 4294967295 CPU usage: start_time: 1191754125 rtime: 234 utime: 213 stime: 21 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6bb19f0 (LWP 4518)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 168521
Thread 1 (Thread 0xb6bb19f0 (LWP 4518))
----------- .xsession-errors (27 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: <info> You are now connected to the wireless network 'i9.dk'. --------------------------------------------------
I can still make the desktop crash by using Properties... on a gif image, do you need more that the stack trace I added in Comment #3 in order to debug this?
I have tried on a colleagues computer, it also crashed nautilus there. It is not all gif's that causes this problem, I will upload a gif that does.
Created attachment 97591 [details] gif that causes crash
Thank you for tracking down the cause of this.
Thanks for taking the time to report this bug. I cannot reproduce the crash with GNome 2.20.1 on Ubuntu Linux 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!
I have the same problem with an png file. Using Debian testing also. Backtrace: [New Thread 0xb5c88b90 (LWP 6077)] [Thread 0xb5c88b90 (LWP 6077) exited] Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... Program received signal SIGABRT, Aborted. Note: the file is : #file .face.icon .face.icon: PNG image data, 60 x 60, 8-bit/color RGBA, non-interlaced
I have reported the bug to Debian as #454297. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454297 They point to libexempi as responsible for the crash.
Bug is not in GNOME
NOTGNOME. See the debian bug for the details. I'll fix it for exempi 1.99.8 Thanks for the report.