GNOME Bugzilla – Bug 525657
crash in Gimmie: Writing in the toolbar s...
Last modified: 2008-04-13 14:59:03 UTC
What were you doing when the application crashed? Writing in the toolbar search Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Gion 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 (777 sec old) --------------------- xkill: killing creator of resource 0x3000b7a Initializing nautilus-open-terminal extension Initializing gnome-mount extension (nautilus:8274): Liboobs-WARNING **: There was an unknown error communicating with the backends: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mess (file-roller:8377): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (gnome-terminal:8632): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400103 (End User L) Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400103 (End User L) Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- Gimmie Version: 0.2.8 Traceback (most recent call last):
+ Trace 193950
printer.connect("attributes_changed", lambda *args: self.emit("reload"))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 475020 ***