GNOME Bugzilla – Bug 427950
crash in Gimmie: I just used the program ...
Last modified: 2007-04-12 22:32:42 UTC
What were you doing when the application crashed? I just used the program on an up-to-date Ubuntu 7.04... Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: MurrinaAquaIsh Icon Theme: Tango 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 (63 sec old) --------------------- CalDAV Eplugin starting up ... (evolution-2.10:9685): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.10:9685): e-utils-WARNING **: Plugin 'Spamassassin-Plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution-2.10:9685): DEBUG: mailto URL command: evolution %s ** (evolution-2.10:9685): DEBUG: mailto URL program: evolution (evolution-2.10:9685): e-data-server-DEBUG: Loading categories from "/home/pascal/.evolution/categories.xml" (evolution-2.10:9685): e-data-server-DEBUG: Loaded 29 categories (evolution-2.10:9685): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb65e9d30(0x86cda78) (evolution-2.10:9685): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error Fenstermanager-Warnung: last_focus_time (4269926) is greater than comparison timestamp (4269922). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACT Fenstermanager-Warnung: Treating resize request of legacy application 0x7c030d6 (WindowsXP ) as a fullscreen request -------------------------------------------------- Traceback (most recent call last):
+ Trace 126340
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 ***