GNOME Bugzilla – Bug 507138
crash in Tasks:
Last modified: 2008-01-04 10:17:08 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: redhat-Red Hat Enterprise Linux AS release 4 Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 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: 133947392 vsize: 133947392 resident: 35418112 share: 27701248 rss: 35418112 rss_rlim: 4294967295 CPU usage: start_time: 1199402558 rtime: 290 utime: 228 stime: 62 cutime:0 cstime: 0 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 -1208891680 (LWP 1122)] [New Thread -1229980784 (LWP 1141)] [New Thread -1250960496 (LWP 1140)] [New Thread -1217660016 (LWP 1131)] [New Thread -1240470640 (LWP 1130)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183983
Thread 1 (Thread -1208891680 (LWP 1122))
----------- .xsession-errors (15 sec old) --------------------- alarm-queue.c:1834 (check_midnight_refresh) alarm-queue.c:1834 (check_midnight_refresh) alarm-queue.c:1834 (check_midnight_refresh) alarm-queue.c:1834 (check_midnight_refresh) alarm-queue.c:1834 (check_midnight_refresh) alarm-queue.c:1834 (check_midnight_refresh) alarm-queue.c:1834 (check_midnight_refresh) alarm-queueQClipboard: Unknown SelectionClear event received. CalDAV Eplugin starting up ... ** (evolution:1122): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:1122): DEBUG: mailto URL program: evolution (evolution:1122): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:1122): camel-WARNING **: camel_exception_get_id called with NULL parameter. --------------------------------------------------
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 364700 ***