GNOME Bugzilla – Bug 460427
crash in Gimmie:
Last modified: 2007-08-30 23:52:54 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Blubuntu Icon Theme: Gion 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 --------------------- (avant-window-navigator:5585): GLib-GObject-WARNING **: gsignal.c:1741: instance `0x80c2000' has no handler with id `88' (avant-window-navigator:5585): GLib-GObject-WARNING **: gsignal.c:1741: instance `0x80c2000' has no handler with id `89' /usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. /usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. /usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. (avant-window-navigator:5585): GLib-GObject-WARNING **: gsignal.c:1741: instance `0x80c2000' has no handler with id `88' (avant-window-navigator:5585): GLib-GObject-WARNING **: gsignal.c:1741: instance `0x80c2000' has no handler with id `89' (avant-window-navigator:5585): GLib-GObject-WARNING **: gsignal.c:1741: instance `0x80c2000' has no handler with id `88' (avant-window-navigator:5585): GLib-GObject-WARNING **: gsignal.c:1741: instance `0x80c2000' has no handler with id `89' -------------------------------------------------- Traceback (most recent call last):
+ Trace 150581
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 ***