GNOME Bugzilla – Bug 495798
crash in gThumb Image Viewer: Was deleting a directory...
Last modified: 2007-11-11 10:52:56 UTC
What were you doing when the application crashed? Was deleting a directory with pictures, size around 1G 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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 110125056 vsize: 110125056 resident: 46927872 share: 19922944 rss: 46927872 rss_rlim: 4294967295 CPU usage: start_time: 1194759382 rtime: 4640 utime: 4348 stime: 292 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gthumb' (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 -1208191264 (LWP 17309)] [New Thread -1221403760 (LWP 17343)] [New Thread -1234183280 (LWP 17319)] [New Thread -1233654896 (LWP 17318)] [New Thread -1233126512 (LWP 17317)] [New Thread -1220875376 (LWP 17315)] [New Thread -1220346992 (LWP 17314)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176946
Thread 1 (Thread -1208191264 (LWP 17309))
----------- .xsession-errors (1124 sec old) --------------------- --> file:///home/alex (nautilus:17106): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) gnome-mount 0.6 ** (gnome-mount:17122): WARNING **: Drive /dev/scd0 does not contain media. ** (nautilus-cd-burner:17118): WARNING **: Unable to prepare tracks for burning --- Hash table keys for warning below: --> file:///home/alex (nautilus:17129): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ** (nautilus-cd-burner:17135): WARNING **: Unable to prepare tracks for burning --------------------------------------------------
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 (2.10.8). *** This bug has been marked as a duplicate of 492169 ***