GNOME Bugzilla – Bug 536737
crash in Deskbar:
Last modified: 2008-06-05 10:04:28 UTC
What were you doing when the application crashed? Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.2 2008-05-30 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-18-generic #1 SMP Wed May 28 20:27:26 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: OS X Leopard Icon Theme: Mist 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 (12 sec old) --------------------- Debug: Done reading conf from /etc/beagle/config-files/BeagleSearch.xml Debug: Done reading conf from /home/anne/.beagle/config/Daemon.xml Debug: Done reading conf from /etc/beagle/config-files/Daemon.xml /home/anne/.themes/OS X Leopard/gtk-2.0/panel.rc:58: Unable to locate image file in pixmap_path: "Panel/panel-bg-trans.png" /home/anne/.themes/OS X Leopard/gtk-2.0/panel.rc:61: Background image options specified without filename Debug: Done reading conf from /home/anne/.beagle/config/FilesQueryable.xml Debug: Done reading conf from /etc/beagle/config-files/FilesQueryable.xml Debug: Done reading conf from /home/anne/.beagle/config/Daemon.xml Debug: Done reading conf from /etc/beagle/config-files/Daemon.xml Debug: Done reading conf from /etc/beagle/config-files/BeagleSearch.xml Debug: Done reading conf from /home/anne/.beagle/config/Networking.xml Debug: Done reading conf from /etc/beagle/config-files/Networking.xml Debug: Done writing to /home/anne/.beagle/config/Networking.xml Debug: Done writing to /home/anne/.beagle/config/FilesQueryable.xml Debug: Done writing to /home/anne/.beagle/config/Daemon.xml -------------------------------------------------- Traceback (most recent call last):
+ Trace 199611
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 ***