GNOME Bugzilla – Bug 518549
crash in Tasks:
Last modified: 2008-02-28 05:40:15 UTC
Version: 2.10 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.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 132100096 vsize: 132100096 resident: 52187136 share: 35745792 rss: 52187136 rss_rlim: 4294967295 CPU usage: start_time: 1191566192 rtime: 1636 utime: 1523 stime: 113 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208277280 (LWP 3183)] [New Thread -1248695408 (LWP 4259)] [New Thread -1308619888 (LWP 4256)] [New Thread -1266070640 (LWP 3243)] [New Thread -1216820336 (LWP 3205)] (no debugging symbols found) 0x00b32402 in __kernel_vsyscall ()
+ Trace 190366
Thread 1 (Thread -1208277280 (LWP 3183))
----------- .xsession-errors (37 sec old) --------------------- QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver --------------------------------------------------
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 447591 ***