GNOME Bugzilla – Bug 428142
crash in Gimmie: starting up gaim
Last modified: 2007-04-12 22:31:45 UTC
What were you doing when the application crashed? starting up gaim 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 20:37:49 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human 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 (389 sec old) --------------------- kio_http_debug: WARNING: (8756) closeCacheEntry: error closing cache entry. (/var/tmp/kdecache-defrysk/http/b/www.bt-chat.com_rss.php_540ab93c.new) kio_http_debug: WARNING: (8755) closeCacheEntry: error renaming cache entry. (/var/tmp/kdecache-defrysk/http/b/www.bt-chat.com_rss.php_540ab93c.new -> /var/tmp/kdecache-defrysk/http/b/www.bt-chat.com_ kio_http_debug: WARNING: (8755) closeCacheEntry: error closing cache entry. (/var/tmp/kdecache-defrysk/http/b/www.bt-chat.com_rss.php_540ab93c.new) kio_http_debug: WARNING: (8753) closeCacheEntry: error renaming cache entry. (/var/tmp/kdecache-defrysk/http/b/www.bt-chat.com_rss.php_540ab93c.new -> /var/tmp/kdecache-defrysk/http/b/www.bt-chat.com_ kio_http_debug: WARNING: (8753) closeCacheEntry: error closing cache entry. (/var/tmp/kdecache-defrysk/http/b/www.bt-chat.com_rss.php_540ab93c.new) X Error: BadDevice, invalid or uninitialized input device 169 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 169 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device -------------------------------------------------- Traceback (most recent call last):
+ Trace 126483
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 ***