GNOME Bugzilla – Bug 412513
crash in Sudoku: I was trying to figure o...
Last modified: 2007-02-27 11:26:31 UTC
What were you doing when the application crashed? I was trying to figure out if I had completed the game - the board was full, but it didn't act like I was done??? I tried reentering the last square I had completed, but it turned red, then crashed. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.17.91 2007-02-12 (Ubuntu) BugBuddy Version: 2.17.3 System: Linux 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled 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.entry_validate(linked_entry)
+ Trace 114230
self.__entries__[conflict].set_error_highlight(True)
X Error: BadDevice, invalid or uninitialized input device 167 Major opcode: 144 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 167 Major opcode: 144 Minor opcode: 3 Resource id: 0x0 Failed to open device -------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1039, in entry_callback self.remove(widget.x,widget.y) File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1146, in remove self.entry_validate(linked_entry)
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 409472 ***