GNOME Bugzilla – Bug 486226
crash in Deskbar: searching for document
Last modified: 2007-10-13 16:19:18 UTC
What were you doing when the application crashed? searching for document 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 Wed Oct 10 05:28:36 GMT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: glass-icons 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 (11 sec old) --------------------- *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Message timeout ** (gnome-app-install:11786): 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) did not change anything *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Message timeout *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Message timeout Launched application : 11864 *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Message timeout *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Message timeout *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Message timeout *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Message timeout *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Message timeout Launched application : 11919 -------------------------------------------------- Traceback (most recent call last):
+ Trace 169885
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)
Thank you for reporting this bug. It looks like this is the same issue as bug 474131.
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 ***