GNOME Bugzilla – Bug 500244
crash in Tasks:
Last modified: 2007-11-28 20:10:49 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.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: 121643008 vsize: 121643008 resident: 37146624 share: 30388224 rss: 37146624 rss_rlim: 4294967295 CPU usage: start_time: 1196267604 rtime: 83 utime: 70 stime: 13 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 -1209063712 (LWP 3917)] [New Thread -1258288240 (LWP 3941)] [New Thread -1223201904 (LWP 3935)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 179986
Thread 1 (Thread -1209063712 (LWP 3917))
----------- .xsession-errors --------------------- alarm-notify.c:316 (cal_opened_cb) file:///home/fifou/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:1998 (alarm_queue_add_async) - 0xb6701b40 alarm-queue.c:585 (load_alarms_for_today) - From Wed Nov 28 17:33:18 2007 to Wed Nov 28 17:33:18 2007 alarm-queue.c:522 (load_alarms) alarm-queue.c:551 (load_alarms) - Setting Call backs alarm-notify.c:316 (cal_opened_cb) file:///home/fifou/.evolution/calendar/local/system - Calendar Status 0 alarm-queue.c:1998 (alarm_queue_add_async) - 0x847bd00 alarm-queue.c:585 (load_alarms_for_today) - From Wed Nov 28 17:33:18 2007 to Wed Nov 28 17:33:18 2007 alarm-queue.c:522 (CalDAV Eplugin starting up ... ** (evolution:3917): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3917): DEBUG: mailto URL program: evolution --------------------------------------------------
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 431459 ***