GNOME Bugzilla – Bug 464850
crash in Image Viewer: Browsing through images ...
Last modified: 2007-08-09 14:20:59 UTC
Version: 2.18.2 What were you doing when the application crashed? Browsing through images (via PgUp/PgDown) in full screen mode. 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: Permissive Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Gion Memory status: size: 121229312 vsize: 121229312 resident: 36372480 share: 31186944 rss: 36372480 rss_rlim: 4294967295 CPU usage: start_time: 1186611096 rtime: 211 utime: 195 stime: 16 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 -1208424736 (LWP 3280)] [New Thread -1293923440 (LWP 3282)] [New Thread -1210524784 (LWP 3281)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 153821
Thread 1 (Thread -1208424736 (LWP 3280))
----------- .xsession-errors (853 sec old) --------------------- (org.freedesktop.DBus.Error.NoReply) Message did not receive a reply (timeout by message bus) ** (nm-applet:2892): WARNING **: <WARN> nma_dbus_net_properties_cb(): dbus returned an error. (org.freedesktop.DBus.Error.NoReply) Message did not receive a reply (timeout by message bus) ** (nm-applet:2892): WARNING **: <WARN> nma_dbus_device_get_driver_cb(): dbus returned an error. (org.freedesktop.DBus.Error.NoReply) Message did not receive a reply (timeout by message bus) ** Message: <info> You are now connected to the wireless network 'grove-home'. --------------------------------------------------
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 354327 *** This bug has been marked as a duplicate of 320206 ***