GNOME Bugzilla – Bug 454512
crash in Deskbar: Logging in to Gnome. The...
Last modified: 2007-07-07 21:19:34 UTC
What were you doing when the application crashed? Logging in to Gnome. The Deskbar-applet crashes upon login. Seems to have something to do with the Tracker integration. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome-icon-theme-2.18.0 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:2008 (alarm_queue_add_async) - 0x80bcf90 alarm-queue.c:560 (load_alarms_for_today) - From Sat Jul 7 10:04:30 2007 to Sat Jul 7 10:04:30 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80c0178: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80bf9b8: Received at thread b4e67b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80c2ad0 alarm-queue.c:560 (load_alarms_for_today) - From Sat Jul 7 10:04:30 2007 to Sat Jul 7 10:04:30 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80bf9b8: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0 -------------------------------------------------- Traceback (most recent call last):
+ Trace 146295
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 ***