GNOME Bugzilla – Bug 469512
crash in Image Viewer:
Last modified: 2007-09-08 01:40:32 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.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: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 277659648 vsize: 277659648 resident: 180916224 share: 35131392 rss: 180916224 rss_rlim: 4294967295 CPU usage: start_time: 1187856476 rtime: 292 utime: 244 stime: 48 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 -1208768800 (LWP 6549)] [New Thread -1424721008 (LWP 6551)] [New Thread -1211069552 (LWP 6550)] (no debugging symbols found) 0x00356402 in __kernel_vsyscall ()
+ Trace 157314
Thread 3 (Thread -1211069552 (LWP 6550))
----------- .xsession-errors (8 sec old) --------------------- (evolution:2876): camel-imap-provider-WARNING **: No information for message 2232 (evolution:2876): camel-imap-provider-WARNING **: No information for message 2232 (evolution:2876): camel-imap-provider-WARNING **: No information for message 2232 (evolution:2876): camel-imap-provider-WARNING **: No information for message 2232 (evolution:2876): camel-imap-provider-WARNING **: No information for message 2232 (evolution:2876): camel-imap-provider-WARNING **: No information for message 2232 ** ERROR **: file eog-window.c: line 1415 (job_save_handle_error): should not be reached aborting... Xlib: unexpected async reply (sequence 0x33de)! --------------------------------------------------
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 357405 ***