GNOME Bugzilla – Bug 537479
crash in Deskbar: trying to search for som...
Last modified: 2008-06-10 11:02:35 UTC
What were you doing when the application crashed? trying to search for something (beagle-live is enabled) Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25.4mike #3 SMP PREEMPT Mon Jun 9 08:55:11 PDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: Nuvola 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 (16096 sec old) --------------------- ** (nm-applet:3829): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.21" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:3829): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.21" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:3829): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.21" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:3829): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.21" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:3829): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.21" is not allowed to own the service "org.freedesktop.Networ ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 199973
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 ***