GNOME Bugzilla – Bug 478051
crash in Deskbar: Searching
Last modified: 2007-09-18 16:19:33 UTC
What were you doing when the application crashed? Searching Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-11-generic #1 SMP Mon Sep 17 03:45:58 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 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 (91 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80ea8c0: Replied to GUI thread alarm-queue.c:581 (load_alarms_for_today) - From Tue Sep 18 16:26:11 2007 to Tue Sep 18 16:26:11 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80ea838: Received at thread b5e30b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e1230 alarm-notify.c:337 (alarm_msgport_replied) - 0x80e0e80: Replied to GUI thread alarm-queue.c:581 (load_alarms_for_today) - From Tue Sep 18 16:26:11 2007 to Tue Sep 18 16:26:11 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80ea838: Replied to GUI thread alarm-notify.c:349 (alarm_msg_rece -------------------------------------------------- Traceback (most recent call last):
+ Trace 163763
reply_handler(*message.get_args_list(**get_args_opts))
reply_handler = lambda hits: self.recieve_hits(qstring, hits, max),
matches.append(TrackerLiveSearchMatch (output))
self.add_all_actions (get_actions_for_uri(result['uri']))
mime = gnomevfs.get_mime_type(uri)
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 474131 ***