GNOME Bugzilla – Bug 502611
crash in Deskbar: I was performing a deskt...
Last modified: 2007-12-13 13:40:14 UTC
What were you doing when the application crashed? I was performing a desktop search using the native search tool. I was searching for the term "boinc" to try and find the newly-installed application. A web browser window was brought up, featuring a google search for the term. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (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 (745 sec old) --------------------- ** (nautilus:6387): WARNING **: Can not determine workarea, guessing at layout evolution-alarm-notify-Message: Setting timeout for 74983 1197244800 1197169817 evolution-alarm-notify-Message: Sun Dec 9 19:00:00 2007 evolution-alarm-notify-Message: Sat Dec 8 22:10:17 2007 Throttle level is 0 /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format ** (gnome-app-install:6730): WARNING **: return value of custom widget handler was not a GtkWidget /usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1261: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed item.applications.set_default_sort_func(None) ** (trackerd:6523): CRITICAL **: scan_directory: assertion `tracker_is_directory (uri)' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 181291
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
if text.startswith(query):
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 475351 ***