GNOME Bugzilla – Bug 457867
crash in Tasks: went from the junk folde...
Last modified: 2007-07-29 20:11:04 UTC
What were you doing when the application crashed? went from the junk folder to a folder under Inbox 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 182976512 vsize: 182976512 resident: 80396288 share: 21270528 rss: 80396288 rss_rlim: 4294967295 CPU usage: start_time: 1184720757 rtime: 55070 utime: 50624 stime: 4446 cutime:67507 cstime: 4550 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 -1208477984 (LWP 11059)] [New Thread -1335485552 (LWP 14888)] [New Thread -1289237616 (LWP 14887)] [New Thread -1228932208 (LWP 13164)] [New Thread -1239422064 (LWP 11143)] [New Thread -1304015984 (LWP 11134)] (no debugging symbols found) 0x0054c402 in __kernel_vsyscall ()
+ Trace 148767
Thread 1 (Thread -1208477984 (LWP 11059))
----------- .xsession-errors (11608 sec old) --------------------- alarm-queue.c:541 (load_alarms) - Disconnecting old queries alarm-queue.c:551 (load_alarms) - Setting Call backs alarm-queue.c:264 (add_client_alarms_cb) - Adding (nil) alarm-queue.c:585 (load_alarms_for_today) - From Wed Jul 18 00:03:30 2007 to Wed Jul 18 00:03:30 2007 alarm-queue.c:522 (load_alarms) alarm-queue.c:541 (load_alarms) - Disconnecting old queries alarm-queue.c:551 (load_alarms) - Setting Call backs alarm-queue.c:264 (add_client_alarms_cb) - Adding (nil) alarm-quevolution-alarm-notify-Message: Setting timeout for 86191 1184817600 1184731409 evolution-alarm-notify-Message: Thu Jul 19 00:00:00 2007 evolution-alarm-notify-Message: Wed Jul 18 00:03:29 2007 --------------------------------------------------
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 433573 ***