GNOME Bugzilla – Bug 487010
crash in Deskbar: Entering In search terms...
Last modified: 2007-10-16 02:12:39 UTC
What were you doing when the application crashed? Entering In search terms in Deskbar 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 (2642 sec old) --------------------- ** (nm-applet:5285): WARNING **: <WARN> nma_dbus_device_properties_cb(): dbus returned an error. (org.freedesktop.NetworkManager.DeviceNotFound) The requested network device does not exist. ** (nm-applet:5285): WARNING **: <WARN> nma_dbus_device_properties_cb(): dbus returned an error. (org.freedesktop.NetworkManager.DeviceNotFound) The requested network device does not exist. current dist not found in meta-release file current dist not found in meta-release file GNOME_SUDO_PASS sudo: 1 incorrect password attempt SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS -------------------------------------------------- Traceback (most recent call last):
+ Trace 170462
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 ***