GNOME Bugzilla – Bug 482306
crash in Deskbar:
Last modified: 2007-10-02 12:10:57 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.6 2007-07-30 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome 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 --------------------- alarm-queue.c:479 (load_alarms) alarm-queue.c:508 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80cbbc8: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2008 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80d0db8: Received at thread b5deeb90 alarm-queue.c:1959 (alarm_queue_add_async) - 0x80cb570 alarm-queue.c:542 (load_alarms_for_today) - From Mon Oct 1 19:11:13 2007 to Mon Oct 1 19:11:13 2007 alarm-queue.c:479 (load_alarms) alarm-queue.c:508 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d0db8: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/primosz/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2008 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_rece -------------------------------------------------- Traceback (most recent call last):
+ Trace 166903
self.load (f)
mod_instance = getattr (mod, handler) ()
bus = dbus.SessionBus()
mainloop=mainloop)
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
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 366899 ***