GNOME Bugzilla – Bug 501251
crash in Tasks:
Last modified: 2007-12-03 16:33:22 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2936.fc7xen #1 SMP Fri Sep 21 11:56:20 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 737239040 vsize: 737239040 resident: 107409408 share: 45039616 rss: 107409408 rss_rlim: 18446744073709551615 CPU usage: start_time: 1196432121 rtime: 39966 utime: 21176 stime: 18790 cutime:131 cstime: 619 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496455824 (LWP 13091)] [New Thread 1147435344 (LWP 13122)] [New Thread 1136679248 (LWP 13120)] [New Thread 1105209680 (LWP 13111)] (no debugging symbols found) 0x0000003c68a0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 180553
Thread 1 (Thread 46912496455824 (LWP 13091))
----------- .xsession-errors (977 sec old) --------------------- Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character with Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character with Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character with Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character with Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character with Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character with Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character with Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character with BBDB spinning up... QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4e00003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Log level 16: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character with --------------------------------------------------
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 422742 ***