GNOME Bugzilla – Bug 536096
crash in Deskbar: typing in a search for p...
Last modified: 2008-06-02 09:34:38 UTC
What were you doing when the application crashed? typing in a search for pidgin, I was at "pid". Also, this happens every time, and it won't really crash, but bug buddy seems to think so. According to the crash details, it couldn't find beagle, wich is right, because I removed beagle: it kept going nuts on my memory, hanging my pc. Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.2 2008-05-27 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-17-generic #1 SMP Thu May 1 14:31:33 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome 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 (330 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** (gnome-system-monitor:15125): WARNING **: SELinux was found but is not enabled. (gtk-window-decorator:6029): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gtk-window-decorator:6029): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or d Please ask your system administrator to enable user sharing. -------------------------------------------------- Traceback (most recent call last):
+ Trace 199341
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
self.beagle.send_request_async(self.beagle_query)
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 530057 ***