GNOME Bugzilla – Bug 498453
crash in Tasks:
Last modified: 2007-11-20 13:30:54 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.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 112496640 vsize: 112496640 resident: 44515328 share: 26636288 rss: 44515328 rss_rlim: 4294967295 CPU usage: start_time: 1195553047 rtime: 438 utime: 383 stime: 55 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 -1208338720 (LWP 29562)] [New Thread -1278792816 (LWP 30361)] [New Thread -1228932208 (LWP 29572)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178896
Thread 1 (Thread -1208338720 (LWP 29562))
----------- .xsession-errors (39 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-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-queuWARNING: DCOPReply<>: cast to 'QStringList' error WARNING: DCOPReply<>: cast to 'QString' error --------------------------------------------------
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 ***