GNOME Bugzilla – Bug 496801
crash in Tasks:
Last modified: 2007-11-15 14:46:03 UTC
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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 181596160 vsize: 181596160 resident: 51433472 share: 22368256 rss: 51433472 rss_rlim: 4294967295 CPU usage: start_time: 1195036316 rtime: 19405 utime: 17089 stime: 2316 cutime:1823 cstime: 225 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 -1208949024 (LWP 3175)] [New Thread -1399293040 (LWP 3661)] [New Thread -1294918768 (LWP 3199)] [New Thread -1356887152 (LWP 3196)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 177698
Thread 1 (Thread -1208949024 (LWP 3175))
----------- .xsession-errors (10312 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 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 QFont::setPointSize: Point size <= 0 (-1) QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 426807 ***