GNOME Bugzilla – Bug 483446
crash in Gimmie: Installed Gimme via apti...
Last modified: 2007-10-06 11:01:21 UTC
What were you doing when the application crashed? Installed Gimme via aptitude. Added it to the top pannel via the right click menu. removed the default gnome menu applet. Moved Gimme to the far left ot replace it. clicked on Linux to open the menu, clicked on Recently Used then it crashed. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 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 (281 sec old) --------------------- (evince:17693): Gtk-WARNING **: Unable to parse accelerator 'ZOOM_OUT_ACCEL' for action 'ViewZoomOut' (evince:17693): Gtk-WARNING **: Unable to parse accelerator 'FULLSCREEN_ACCEL' for action 'ViewFullscreen' (evince:17693): Gtk-WARNING **: Unable to parse accelerator 'PRESENTATION_ACCEL' for action 'ViewPresentation' Error: Can't get Fields array ** (gnome-app-install:17779): WARNING **: return value of custom widget handler was not a GtkWidget /usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1261: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed item.applications.set_default_sort_func(None) /bin/sh: /usr/bin/esd: not found /bin/sh: /usr/bin/esd: not found sh: jackd: not found -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 167768
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 ***