GNOME Bugzilla – Bug 433622
crash in Sudoku: opened & closed
Last modified: 2007-04-27 00:41:12 UTC
What were you doing when the application crashed? opened & closed 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: 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 --------------------- self._batch_setitems(obj.iteritems())
+ Trace 130713
for k, v in items:
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): File "/usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py", line 544, in quit_cb self.sudoku_tracker.save() File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku_maker.py", line 476, in save self.sudoku_maker.save() File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku_maker.py", line 425, in save ofi) File "pickle.py", line 1362, in dump Pickler(file, protocol).dump(obj) File "pickle.py", line 224, in dump self.save(obj) File "pickle.py", line 286, in save f(self, obj) # Call unbound method with explicit self File "pickle.py", line 649, in save_dict self._batch_setitems(obj.iteritems()) File "pickle.py", line 663, in _batch_setitems save(v) File "pickle.py", line 286, in save f(self, obj) # Call unbound method with explicit self File "pickle.py", line 649, in save_dict self._batch_setitems(obj.iteritems())
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 409172 ***