GNOME Bugzilla – Bug 532489
crash in Deskbar: waiting while beagle ind...
Last modified: 2008-05-10 17:32:36 UTC
What were you doing when the application crashed? waiting while beagle indexed my hardrives. I upgraded my installation, haveing my home directory on a seperate partion. I do not format my home partion, to keep my settings and configurations accross installs. It looks like those panel short cuts from my last system were not removed properly during the upgrade. 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: Enabled GTK+ Theme: UbuntuStudio Icon Theme: UbuntuStudio 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 (2558 sec old) --------------------- /usr/bin/compiz.real (core) - Warn: pixmap 0x5019d7a can't be bound to texture Unable to open desktop file /usr/share/applications/gnomesword.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/kde/konqbrowser.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/gnomesword.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/kde/konqbrowser.desktop for panel launcher: No such file or directory ** (<unknown>:6766): WARNING **: Failed to send buffer ** (<unknown>:6766): WARNING **: Failed to send buffer ** (<unknown>:6766): WARNING **: Failed to send buffer ** (<unknown>:6766): WARNING **: Failed to send buffer ** (<unknown>:6766): WARNING **: Failed to send buffer -------------------------------------------------- Traceback (most recent call last):
+ Trace 197377
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 ***