GNOME Bugzilla – Bug 497056
crash in Home Folder: Try to open Property dia...
Last modified: 2007-11-15 15:05:09 UTC
What were you doing when the application crashed? Try to open Property dialog on a Webdav folder Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 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: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: H2O-gtk2-Saphire Icon Theme: gartoon Memory status: size: 84631552 vsize: 84631552 resident: 34988032 share: 15482880 rss: 34988032 rss_rlim: 4294967295 CPU usage: start_time: 1195135918 rtime: 230 utime: 208 stime: 22 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 0xb6e136b0 (LWP 6118)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 177877
Thread 1 (Thread 0xb6e136b0 (LWP 6118))
----------- .xsession-errors --------------------- ** 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: Failed to close thumbnail pixbuf loader for /home/barmeier/fax000000001.tif: TIFF-Bild konnte nicht geladen werden ** Message: Failed to close thumbnail pixbuf loader for /home/barmeier/fax000000001.tif: TIFF-Bild konnte nicht geladen werden 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... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 440988 ***