GNOME Bugzilla – Bug 507388
crash in Image Viewer:
Last modified: 2008-01-05 21:20:11 UTC
Version: 2.18.2 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 159752192 vsize: 159752192 resident: 101634048 share: 22065152 rss: 101634048 rss_rlim: 4294967295 CPU usage: start_time: 1199491359 rtime: 1421 utime: 1348 stime: 73 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/eog' (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 -1209096480 (LWP 3104)] [New Thread -1255740528 (LWP 3106)] [New Thread -1211196528 (LWP 3105)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184111
Thread 1 (Thread -1209096480 (LWP 3104))
----------- .xsession-errors (51 sec old) --------------------- --> file:///home/ted (nautilus:2892): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) connection_message_func(): Callback CALLBACK: fill-authentication!!! --- Hash table keys for warning below: --> file:///home/ted (nautilus:2968): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --- Hash table keys for warning below: --> file:///home/ted (nautilus:3097): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --------------------------------------------------
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 version 2.20. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 354154 ***