GNOME Bugzilla – Bug 488730
crash in Image Viewer: exploring images from my...
Last modified: 2007-10-21 12:34:13 UTC
Version: 2.18.2 What were you doing when the application crashed? exploring images from my fedora 7 based pentium4 on my brother's PC, windows based Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000001 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 77291520 vsize: 77291520 resident: 25309184 share: 9822208 rss: 25309184 rss_rlim: 4294967295 CPU usage: start_time: 1192910024 rtime: 349 utime: 327 stime: 22 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 -1208490272 (LWP 9679)] [New Thread -1246250096 (LWP 9683)] [New Thread -1210590320 (LWP 9681)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 171778
Thread 2 (Thread -1246250096 (LWP 9683))
----------- .xsession-errors --------------------- (emerald:3377): Wnck-WARNING **: Unhandled action type (nil) (emerald:3377): Wnck-WARNING **: Unhandled action type (nil) connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! (emerald:3377): Wnck-WARNING **: Unhandled action type (nil) (emerald:3377): Wnck-WARNING **: Unhandled action type (nil) (emerald:3377): Wnck-WARNING **: Unhandled action type (nil) (emerald:3377): Wnck-WARNING **: Unhandled action type (nil) --------------------------------------------------
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. *** This bug has been marked as a duplicate of 357405 ***