GNOME Bugzilla – Bug 437236
crash in Deskbar:
Last modified: 2007-05-09 22:07:46 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 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 (13 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x6d1be0: Replied to GUI thread alarm-queue.c:560 (load_alarms_for_today) - From Wed May 9 19:57:19 2007 to Wed May 9 19:57:19 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x6d8530: Received at thread 41042940 alarm-queue.c:2008 (alarm_queue_add_async) - 0x6d3940 alarm-notify.c:337 (alarm_msgport_replied) - 0x6d5d80: Replied to GUI thread alarm-queue.c:560 (load_alarms_for_today) - From Wed May 9 19:57:19 2007 to Wed May 9 19:57:19 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x6da500: Received at thread 41042940 alarm-queue.c:2008 (alarm_queue_add -------------------------------------------------- Traceback (most recent call last):
+ Trace 133313
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 for tracker. *** This bug has been marked as a duplicate of 403752 ***