GNOME Bugzilla – Bug 464003
crash in Image Viewer: F11-space-space-space-F1...
Last modified: 2007-08-06 13:57:17 UTC
Version: 2.18.2 What were you doing when the application crashed? F11-space-space-space-F11 Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-3-k7 #1 SMP Mon Dec 4 17:23:11 UTC 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Kreski-Lines Memory status: size: 75051008 vsize: 75051008 resident: 47714304 share: 11366400 rss: 47714304 rss_rlim: 4294967295 CPU usage: start_time: 1186408101 rtime: 505 utime: 473 stime: 32 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 -1225705808 (LWP 12236)] [New Thread -1244927088 (LWP 12243)] [New Thread -1228412016 (LWP 12242)] (no debugging symbols found) 0xb7670ae1 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 153200
Thread 1 (Thread -1225705808 (LWP 12236))
----------- .xsession-errors (386 sec old) --------------------- ** 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: drive = 0 ** Message: volume ...Too much output, ignoring rest... --------------------------------------------------
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. Duplicate via stacktrace in Bug 354154 and then via Bug 354327 *** This bug has been marked as a duplicate of 320206 ***