GNOME Bugzilla – Bug 489921
crash in Deskbar: typing "fire" into the S...
Last modified: 2007-10-25 10:22:31 UTC
What were you doing when the application crashed? typing "fire" into the Search: box. 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-rt #1 SMP PREEMPT RT Mon Oct 15 01:05:51 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: UbuntuStudio Icon Theme: UbuntuStudio 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 (716 sec old) --------------------- (gnome-panel:5498): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:5498): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:5498): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:5498): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed ** (gnome-system-monitor:8004): WARNING **: SELinux was found but is not enabled. ** (gnome-app-install:8086): 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) -------------------------------------------------- Traceback (most recent call last):
+ Trace 172619
reply_handler(*message.get_args_list(**get_args_opts))
self._introspect_execute_queue()
proxy_method(*args, **keywords)
**keywords)
require_main_loop=require_main_loop) MemoryError
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 478758 ***