GNOME Bugzilla – Bug 457978
crash in Gimmie: I'm searching for an app...
Last modified: 2007-09-13 22:43:17 UTC
What were you doing when the application crashed? I'm searching for an application by searchbar Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22.1 #1 PREEMPT Fri Jul 13 10:15:12 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Murrina-BluePlastic Icon Theme: nuoveXT.2.1 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 (23 sec old) --------------------- (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Launched application : 14520 (avant-window-navigator:4972): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.12.12/gobject/gsignal.c:1741: instance `0x80a60a8' has no handler with id `85' (avant-window-navigator:4972): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.12.12/gobject/gsignal.c:1741: instance `0x80a60a8' has no handler with id `86' Cutting log (size: 101354, max: 100000)[Warning ]: UnmapNotify event, but couldn't find the window. (avant-window-navigator:4972): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.12.12/gobject/gsignal.c:1741: instance `0x80a60a8' has no handler with id `25' (avant-window-navigator:4972): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.12.12/gobject/gsignal.c:1741: instance `0x80a60a8' has no handler with id `26' -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 148852
return not item1 and 1 or \
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 419093 ***