GNOME Bugzilla – Bug 476146
crash in Image Viewer: switching fast between f...
Last modified: 2007-09-12 20:02:30 UTC
Version: 2.18.2 What were you doing when the application crashed? switching fast between fullscreen and normal (with F11), and moving to next/previous picture with 'enter' and 'backspace'. 'enter' and ' backspace' allone couldn't trigger the crash, but hitting 'F11' fast a lot of times could. Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 53030912 vsize: 53030912 resident: 25309184 share: 10874880 rss: 25309184 rss_rlim: 4294967295 CPU usage: start_time: 1189589707 rtime: 2500 utime: 2376 stime: 124 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225640272 (LWP 5625)] [New Thread -1243083888 (LWP 5628)] [New Thread -1228350576 (LWP 5626)] (no debugging symbols found) 0xb7f567f2 in ?? () from /lib/ld-linux.so.2
+ Trace 162294
Thread 1 (Thread -1225640272 (LWP 5625))
----------- .xsession-errors (11 sec old) --------------------- No whitepoint found No whitepoint found No whitepoint found No whitepoint found No whitepoint found No whitepoint found No whitepoint found No whitepoint found No whitepoint found No whitepoint found No whitepoint found No whitepoint found No whitepoint found No whitepoint found No whitepoint found --------------------------------------------------
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 (upcoming 2.20). You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 354154 ***