GNOME Bugzilla – Bug 467619
crash in Image Viewer:
Last modified: 2007-11-09 15:15:26 UTC
Version: 2.18.2 What were you doing when the application crashed? 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: Clearlooks Icon Theme: Fedora Memory status: size: 85544960 vsize: 85544960 resident: 36790272 share: 20107264 rss: 36790272 rss_rlim: 4294967295 CPU usage: start_time: 1187348726 rtime: 2046 utime: 1808 stime: 238 cutime:26 cstime: 51 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 -1209162016 (LWP 27321)] [New Thread -1245373552 (LWP 27324)] [New Thread -1211462768 (LWP 27323)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 155886
Thread 2 (Thread -1245373552 (LWP 27324))
----------- .xsession-errors (43414 sec old) --------------------- fixme:winsock:WSACancelAsyncRequest (0xdee6),stub fixme:winsock:WSACancelAsyncRequest (0xdee7),stub fixme:shell:DllCanUnloadNow stub fixme:winsock:WSACancelAsyncRequest (0xdee8),stub fixme:winsock:WSACancelAsyncRequest (0xdee9),stub fixme:shell:DllCanUnloadNow stub fixme:shell:DllCanUnloadNow stub fixme:shell:DllCanUnloadNow stub fixme:shell:DllCanUnloadNow stub fixme:shell:DllCanUnloadNow stub fixme:shell:DllCanUnloadNow stub fixme:shell:DllCanUnloadNow stub fixme:shell:DllCanUnloadNow stub ...Too much output, ignoring rest... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 320206 ***
*** Bug 495217 has been marked as a duplicate of this bug. ***