GNOME Bugzilla – Bug 522785
crash in Gimmie: Typing into the search b...
Last modified: 2008-03-22 11:06:03 UTC
What were you doing when the application crashed? Typing into the search box (for the first time after install) Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human 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 (6 sec old) --------------------- ** (trackerd:6297): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800020 (Archive Ma) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Initializing gnome-mount extension /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) /usr/lib/python2.5/site-packages/GDebi/GDebi.py:93: GtkWarning: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed self.window_main.set_sensitive(False) /usr/lib/python2.5/site-packages/GDebi/GDebi.py:93: GtkWarning: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed self.window_main.set_sensitive(False) SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS (gnome-panel:6249): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80f4358 (gnome-panel:6249): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80f4358 -------------------------------------------------- Gimmie Version: 0.2.8 Traceback (most recent call last):
+ Trace 192595
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 ***