GNOME Bugzilla – Bug 432868
crash in Gimmie: I was browsing the web i...
Last modified: 2007-05-03 03:16:02 UTC
What were you doing when the application crashed? I was browsing the web in firefox when Gimmie crasched... Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gartoon 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 (1778 sec old) --------------------- 32 bits per pixel. Least significant byte first in each pixel. True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0 ReadFromRFBServer: rdr::SystemException: read: Connection reset by peer (104) ShmCleanup called Fönsterhanterarvarning: Ogiltigt WM_TRANSIENT_FOR-fönster 0x2 angivet för 0x3400011 (passwordDi). Fönsterhanterarvarning: Ogiltigt WM_TRANSIENT_FOR-fönster 0x88 angivet för 0x3a00001 (Binary fil). ** (gnome-app-install:13123): WARNING **: return value of custom widget handler was not a GtkWidget /usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1532: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed item.applications.set_default_sort_func(None) /usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1118: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed model.set_default_sort_func(None) -------------------------------------------------- Traceback (most recent call last):
+ Trace 130185
acct_doc = parse(self.accounts_path)
from xml.dom import expatbuilder
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 417988 ***