GNOME Bugzilla – Bug 464431
crash in Image Viewer: Changing from fullscreen...
Last modified: 2007-08-07 20:01:29 UTC
Version: 2.18.2 What were you doing when the application crashed? Changing from fullscreen to window view 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Outcrop Icon Theme: nuoveXT.2.1 Memory status: size: 126279680 vsize: 126279680 resident: 62390272 share: 25145344 rss: 62390272 rss_rlim: 4294967295 CPU usage: start_time: 1186507212 rtime: 623 utime: 586 stime: 37 cutime:0 cstime: 1 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 -1208670496 (LWP 2755)] [New Thread -1279853680 (LWP 2757)] [New Thread -1211163760 (LWP 2756)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 153529
Thread 2 (Thread -1279853680 (LWP 2757))
----------- .xsession-errors --------------------- (bug-buddy:2766): Gtk-WARNING **: Theme directory 32x32/filesystems of theme nuoveXT.2.1 has no size field (bug-buddy:2766): Gtk-WARNING **: Theme directory 48x48/filesystems of theme nuoveXT.2.1 has no size field (bug-buddy:2766): Gtk-WARNING **: Theme directory 64x64/filesystems of theme nuoveXT.2.1 has no size field (bug-buddy:2766): Gtk-WARNING **: Theme directory 72x72/filesystems of theme nuoveXT.2.1 has no size field (bug-buddy:2766): Gtk-WARNING **: Theme directory 96x96/filesystems of theme nuoveXT.2.1 has no size field --------------------------------------------------
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 357405 and then via Bug 354327 *** This bug has been marked as a duplicate of 320206 ***