GNOME Bugzilla – Bug 448704
crash in Gimmie: Browsing myspace,
Last modified: 2007-06-23 17:02:12 UTC
What were you doing when the application crashed? Browsing myspace, 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: UbuntuStudio Icon Theme: UbuntuStudio 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 (5012 sec old) --------------------- found matching inotify pair for from /home/sean/Incomplete/downloads.dat to /home/sean/Incomplete/downloads.bak warning original file /home/sean/Incomplete/downloads.dat not found in DB no matching pair found for inotify move event for /home/sean/Incomplete/downloads.bak File /home/sean/Incomplete/downloads.dat has finished changing deleting file /home/sean/Incomplete/downloads.bak flushing all words Finished indexing. Waiting for new events... Window manager warning: last_focus_time (20219889) is greater than comparison timestamp (20219878). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_A Window manager warning: Invalid WM_TRANSIENT_FOR window 0x340006b specified for 0x34002b2 (Shutting d). found matching inotify pair for from /home/sean/Incomplete/downloads.dat to /home/sean/Incomplete/downloads.bak ERROR : prepared query UpdateFileMove failed due to SQL logic error or missing database File /home/sean/Incomplete/downloads.dat has finished changing deleting file /home/sean/Incomplete/downloads.bak flushing all words Finished indexing. Waiting for new events... -------------------------------------------------- Traceback (most recent call last):
+ Trace 141819
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 ***