GNOME Bugzilla – Bug 438324
crash in Deskbar:
Last modified: 2007-05-14 14:44:50 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (32 sec old) --------------------- alarm-notify.c:393 (cal_opened_cb) file:///home/philipp/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80e9830: Received at thread b3539b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80dea60 alarm-queue.c:560 (load_alarms_for_today) - From Mon May 14 00:00:00 2007 to Mon May 14 00:00:00 2007 alarm-queue.c:497 (load_alarms) alarm-notify.c:393 (cal_opened_cb) file:///home/philipp/.evolution/tasks/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:393 (cal_opened_cb) webcal://people.ubuntu.com/~scott/FeistyReleaseSchedule.ics - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80e5cd0: Received at thread b3539b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80e2390 alar -------------------------------------------------- Traceback (most recent call last):
+ Trace 134105
self.load (f)
mod_instance = getattr (mod, handler) ()
self.tracker = bus.get_object('org.freedesktop.Tracker','/org/freedesktop/tracker')
follow_name_owner_changes=follow_name_owner_changes)
_dbus_bindings.UInt32(0))
reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
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 403752 ***