GNOME Bugzilla – Bug 438005
crash in Gimmie:
Last modified: 2007-05-26 00:58:39 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-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: Human Icon Theme: AER-OS-XK 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 (31 sec old) --------------------- adding /home/charles/google-earth for polling (poll count is 1) Inotify watch on /home/charles/google-earth/kvw has failed adding /home/charles/google-earth/kvw for polling (poll count is 2) Inotify watch on /home/charles/google-earth/linux has failed adding /home/charles/google-earth/linux for polling (poll count is 3) Inotify watch on /home/charles/google-earth/res has failed adding /home/charles/google-earth/res for polling (poll count is 4) Inotify watch on /home/charles/google-earth/lang has failed adding /home/charles/google-earth/lang for polling (poll count is 5) Inotify watch on /home/charles/google-earth/linux/mailto-scripts has failed adding /home/charles/google-earth/linux/mailto-scripts for polling (poll count is 6) Inotify watch on /home/charles/google-earth/res/paddle has failed adding /home/charles/google-earth/res/paddle for polling (poll count is 7) File /home/charles/Desktop/Google-googleearth.desktop has finished changing indexing #100 - /home/charles/google-earth/res/h-slider-zoom-thumb-norm.png -------------------------------------------------- Traceback (most recent call last):
+ Trace 133868
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 ***