GNOME Bugzilla – Bug 442507
crash in Sudoku: ConflictError: (1, (3, 1), 6)
Last modified: 2008-08-07 23:13:45 UTC
What were you doing when the application crashed? tried to open old game Pussel 69, started onsdag 08:34:14, 7 hours ago. 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 Wed May 23 01:46:23 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome 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 --------------------- fun(ui,*args,**kwargs)
+ Trace 136956
saver.open_game(self,puzzl)
ui.gsd.load_game(jar['game'])
self.add_value(col,row,values[index])
self.grid.add(x,y,val,True)
SudokuGrid.add(self,x,y,val,*args,**kwargs)
raise ConflictError(TYPE_COLUMN,(x,y),val)
-------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py", line 64, in _ fun(ui,*args,**kwargs)
reminds of bug 437762
*** Bug 463161 has been marked as a duplicate of this bug. ***
*** Bug 467241 has been marked as a duplicate of this bug. ***
*** Bug 475098 has been marked as a duplicate of this bug. ***
*** Bug 478467 has been marked as a duplicate of this bug. ***
*** Bug 481055 has been marked as a duplicate of this bug. ***
*** Bug 515669 has been marked as a duplicate of this bug. ***
*** Bug 524395 has been marked as a duplicate of this bug. ***
*** Bug 525678 has been marked as a duplicate of this bug. ***
*** Bug 533575 has been marked as a duplicate of this bug. ***
*** Bug 537177 has been marked as a duplicate of this bug. ***
*** Bug 539620 has been marked as a duplicate of this bug. ***
*** Bug 539798 has been marked as a duplicate of this bug. ***
I think this is a race condition. The callback is running twice over the top of itself. (Press CTRL-A twice quickly.) Use a mutex to lock the CTRL-A callback while it is running to keep it from running dups at the same time.
I'm sick of these ConflictError bugs. There are so many wrong duplicates (I made some my self) that it's hard to tell what the real issue is anymore. We really need to tidy this up a bit. E.g. the stacktrace in this bug is not from the autofill bug. It's an old bug that has been fixed already by Tom before 2.22. I'm moving Jasons comment to the first autofill bug (#433521) and marking all the real duplicates to that one. Then we can close the other ConflictError bugs as the autofill is the only one remaining. For reference this is a list of all the other bugreports for this particular bug: bug #442507 bug #433120 bug #437762 bug #439553 bug #442505 bug #452626 bug #461127 bug #463161 bug #467241 bug #475098 bug #478467 bug #481055 bug #484799