GNOME Bugzilla – Bug 450655
crash in Deskbar:
Last modified: 2007-06-26 17:35:09 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.4 2007-06-18 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Outdoors 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 --------------------- alarm-queue.c:508 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d2350: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80d5060: Received at thread b5d9eb90 alarm-queue.c:1959 (alarm_queue_add_async) - 0x80d05b0 alarm-queue.c:542 (load_alarms_for_today) - From Sun Jun 24 18:21:25 2007 to Sun Jun 24 18:21:25 2007 alarm-queue.c:479 (load_alarms) alarm-queue.c:508 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d5060: 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) - 0x80d16a0: Received at threaDatabase closed for thread main Checking tracker DB version...Current version is 15 and needed version is 13 updating database stats...please wait... -------------------------------------------------- Traceback (most recent call last):
+ Trace 143371
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)
self._named_service = conn.activate_name_owner(bus_name)
self.start_service_by_name(bus_name)
'su', (bus_name, flags)))
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 ***