GNOME Bugzilla – Bug 479361
crash in Deskbar: Highlighted a word in Sw...
Last modified: 2007-09-23 10:54:02 UTC
What were you doing when the application crashed? Highlighted a word in Swiftfox and pressed ALT F3 Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-12-generic #1 SMP Thu Sep 20 18:51:18 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 (878 sec old) --------------------- (yelp:10770): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup. (yelp:10770): atk-bridge-WARNING **: IOR not set. (yelp:10770): atk-bridge-WARNING **: Could not locate registry (yelp:10770): Yelp-WARNING **: YelpDocument: Attempted to add an ID mapping from x-yelp-index to x-yelp-index, but x-yelp-index is already mapped. (synaptic:5974): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (synaptic:5974): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (synaptic:5974): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) -------------------------------------------------- Traceback (most recent call last):
+ Trace 164714
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 ***