GNOME Bugzilla – Bug 428172
crash in Gimmie: nothing.
Last modified: 2007-04-12 22:31:54 UTC
What were you doing when the application crashed? nothing. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-14-generic #2 SMP Mon Apr 2 16:32:46 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: OSX 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 (773 sec old) --------------------- ** (beryl-manager:7066): CRITICAL **: can't execute beryl-xgl: Success ** (beryl-manager:7066): CRITICAL **: can't execute beryl-xgl: Success ** (beryl-manager:7066): CRITICAL **: can't execute beryl-xgl: Success ** (beryl-manager:7066): CRITICAL **: can't execute beryl-xgl: Success ** (beryl-manager:7066): CRITICAL **: can't execute beryl-xgl: Success ** (beryl-manager:7066): CRITICAL **: can't execute beryl-xgl: Success ** (beryl-manager:7066): CRITICAL **: can't execute beryl-xgl: Success ** Message: <information> You are now connected to the wired network. -------------------------------------------------- Traceback (most recent call last):
+ Trace 126512
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 ***