GNOME Bugzilla – Bug 461479
crash in Image Viewer:
Last modified: 2007-07-29 14:31:34 UTC
Version: 2.18.0.1 What were you doing when the application crashed? 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 113967104 vsize: 113967104 resident: 62685184 share: 6533120 rss: 62685184 rss_rlim: 4294967295 CPU usage: start_time: 1185715188 rtime: 30468 utime: 27872 stime: 2596 cutime:53 cstime: 208 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 -1209096480 (LWP 4971)] [New Thread -1239204976 (LWP 4973)] [New Thread -1211511920 (LWP 4972)] (no debugging symbols found) 0x00f28402 in __kernel_vsyscall ()
+ Trace 151360
Thread 1 (Thread -1209096480 (LWP 4971))
----------- .xsession-errors (1317 sec old) --------------------- closing closing closing closing closing closing gnome-mount 0.6 Avertissement du gestionnaire de fenêtres : Received a _NET_WM_MOVERESIZE message for 0x16007ae (Poste de t); these messages lack timestamps and therefore suck. closing closing closing Avertissement du gestionnaire de fenêtres : Fenêtre WM_TRANSIENT_FOR 0x45 non valide indiquée pour 0x164a18d (). closing gnome-mount 0.6 Avertissement du gestionnaire de fenêtres : Received a _NET_WM_MOVERESIZE message for 0x166737d (disk); these messages lack timestamps and therefore suck. --------------------------------------------------
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 320206 ***