GNOME Bugzilla – Bug 429800
crash in Deskbar:
Last modified: 2007-06-10 23:49:07 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-generic #2 SMP Sat Apr 14 00:54:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: T-ish-Ubuntulooks Icon Theme: OSX 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 (18 sec old) --------------------- to Sat Apr 14 23:22:51 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80dcab0: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80dc178: Received at thread b559db90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80be5d0 alarm-queue.c:560 (load_alarms_for_today) - From Sat Apr 14 23:22:51 2007 to Sat Apr 14 23:22:51 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80dc178: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/joteroar/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm -------------------------------------------------- Traceback (most recent call last):
+ Trace 127816
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 the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 403752 ***
*** Bug 445991 has been marked as a duplicate of this bug. ***