GNOME Bugzilla – Bug 494545
crash in Window List: the system has been star...
Last modified: 2007-11-13 08:54:15 UTC
Version: 2.18.0 What were you doing when the application crashed? the system has been started and we seen this bug screen 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 38191104 vsize: 38191104 resident: 8900608 share: 7335936 rss: 8900608 rss_rlim: 4294967295 CPU usage: start_time: 1194434595 rtime: 10 utime: 7 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208645920 (LWP 3027)] (no debugging symbols found) 0x00990402 in __kernel_vsyscall ()
+ Trace 176003
Thread 1 (Thread -1208645920 (LWP 3027))
----------- .xsession-errors (6 sec old) --------------------- alarm-notify.c:316 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-notify.c:316 (cal_opened_cb) file:///root/.evolution/tasks/local/system - Calendar Status 0 alarm-notify.c:316 (cal_opened_cb) file:///root/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:551 (load_alarms) - Setting Call backs alarm-queue.c:1998 (alarm_queue_add_async) - 0x95a9a30 alarm-queue.c:585 (load_alarms_for_today) - From Wed Nov 7 18:23:31 2007 to Wed Nov 7 18:23:31 2007 alarm-queue.c:522 (load_alarms) alarm-queue.c:551 (load_alarms) - Setting Call backs alarm-queue.c:1998 (alarm_queue_add_async) - 0x95ad790 alarm-queue.c:585 (load_alarms_for_today) - From Wed Nov 7 18:23:31 2007 to Wed Nov 7 18:23:31 2007 alarm-qkbuildsycoca running... --------------------------------------------------
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 403377 ***