GNOME Bugzilla – Bug 488289
crash in Deskbar: Searching for a file usi...
Last modified: 2007-10-19 15:13:24 UTC
What were you doing when the application crashed? Searching for a file using Deskbar (with Tracker) on Ubuntu 7.10 Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 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 (3757 sec old) --------------------- alarm-queue.c:581 (load_alarms_for_today) - From Fri Oct 19 09:14:38 2007 to Fri Oct 19 09:14:38 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80ec5f8: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80cfba8: Received at thread b5531b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0xb4c01d00 alarm-queue.c:581 (load_alarms_for_today) - From Fri Oct 19 0/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format CalDAV Eplugin starting up ... ** (evolution:5621): DEBUG: mailto URL command: evolution %s ** (evolution:5621): DEBUG: mailto URL program: evolution ** (trackerd:5423): CRITICAL **: check_directory: assertion `tracker_is_directory (uri)' failed cairo context error: out of memory -------------------------------------------------- Traceback (most recent call last):
+ Trace 171426
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 ***