GNOME Bugzilla – Bug 465018
crash in Image Viewer:
Last modified: 2007-08-09 14:23:14 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve-Lime Icon Theme: gnome Memory status: size: 72245248 vsize: 72245248 resident: 21745664 share: 10952704 rss: 21745664 rss_rlim: 4294967295 CPU usage: start_time: 1186660435 rtime: 648 utime: 554 stime: 94 cutime:11 cstime: 34 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 -1208801040 (LWP 2998)] [New Thread -1237169264 (LWP 3002)] [New Thread -1211053168 (LWP 3001)] (no debugging symbols found) 0x0053c402 in __kernel_vsyscall ()
+ Trace 153949
Thread 3 (Thread -1211053168 (LWP 3001))
----------- .xsession-errors --------------------- Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! --------------------------------------------------
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 357405 and then via bug 354327 *** This bug has been marked as a duplicate of 320206 ***