GNOME Bugzilla – Bug 532877
crash in Deskbar: searching with the deskb...
Last modified: 2008-05-13 11:59:18 UTC
What were you doing when the application crashed? searching with the deskbar applet. Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.1 2008-04-30 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: OSX-theme Icon Theme: LeopardX 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 (8 sec old) --------------------- Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Error: Screen isn't composited. Please run compiz (-fusion) or another compositing manager. Screen is composited. GConf backend: There is an unsupported value at path /apps/compiz/plugins/scale/allscreens/options/initiate_edge. Settings from this path won't be read. Try to remove that value so that operation can compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format (avant-window-navigator:6097): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (avant-window-navigator:6097): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (avant-window-navigator:6097): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (avant-window-navigator:6097): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (avant-window-navigator:6097): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 197589
self._on_hit_added(query, container, qstring, qmax)
self.counter[qstring][hit.get_type()] += 1
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 527023 ***