GNOME Bugzilla – Bug 437865
crash in Deskbar: I'm using tracker as sea...
Last modified: 2007-05-12 17:37:33 UTC
What were you doing when the application crashed? I'm using tracker as search backend. Now the deskbar applet keeps crashing on startup, but tracker seems to work fine. 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-lowlatency #2 SMP PREEMPT Sun Apr 15 06:20:10 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Silicon Icon Theme: Tango 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-notify.c:337 (alarm_msgport_replied) - 0x6b96b0: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x6bbe30: Received at thread 42044940 alarm-queue.c:2008 (alarm_queue_add_async) - 0x6bce20 alarm-queue.c:560 (load_alarms_for_today) - From Sat May 12 13:00:15 2007 to Sat May 12 13:00:15 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x6bbe30: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x6ba940: Received at thread 42044940 alarm-queue.c:2008 (alarm_queue_add_async) - 0x6b8f60 alarm-queue.c:560 (load_alarms_for_today) - From Sat May 12 13:00:15 2007 to Sat May 12 13:00:15 2007 alarm-queue.c:497 (load_alarupdating database stats...please wait... -------------------------------------------------- Traceback (most recent call last):
+ Trace 133773
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 ***