GNOME Bugzilla – Bug 491984
crash in Image Viewer:
Last modified: 2007-10-31 14:02:35 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.20-2931.fc7xen #1 SMP Mon Aug 13 10:12:37 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 61202432 vsize: 61202432 resident: 23363584 share: 17432576 rss: 23363584 rss_rlim: 4294967295 CPU usage: start_time: 1193811411 rtime: 99 utime: 81 stime: 18 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208744224 (LWP 13669)] [New Thread -1231832176 (LWP 13671)] [New Thread -1210844272 (LWP 13670)] (no debugging symbols found) 0x00d78402 in __kernel_vsyscall ()
+ Trace 174097
Thread 2 (Thread -1231832176 (LWP 13671))
----------- .xsession-errors (29 sec old) --------------------- ** (eog:12956): WARNING **: Error in parse: Unexpected tag 'Groups', tag 'RecentItem' expected ** (eog:12956): WARNING **: Error while parsing the .recently-used file: Unexpected tag 'Groups', tag 'RecentItem' expected ** (eog:12949): WARNING **: Error in parse: Unexpected tag 'Groups', tag 'RecentItem' expected ** (eog:12949): WARNING **: Error while parsing the .recently-used file: Unexpected tag 'Groups', tag 'RecentItem' expected ** ERROR **: file eog-window.c: line 1415 (job_save_handle_error): should not be reached aborting... Xlib: unexpected async reply (sequence 0x160a)! --------------------------------------------------
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 ***