GNOME Bugzilla – Bug 489182
crash in Gimmie: searching favorites for ...
Last modified: 2007-10-22 22:23:44 UTC
What were you doing when the application crashed? searching favorites for firefox Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-11-generic #1 SMP Mon Sep 17 03:45:58 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: ClearlooksClassic Icon Theme: Human 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 --------------------- ** (nm-applet:6150): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.18" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:6150): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.18" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:6150): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.18" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:6150): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.18" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:6150): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.18" is not allowed to own the service "org.freedesktop.Networ -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 172062
printer.connect("attributes_changed", lambda p: self.emit("reload"))
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 475020 ***