GNOME Bugzilla – Bug 430893
ConflictError: (0, (8, 2), 6)
Last modified: 2008-08-07 23:20:49 UTC
What were you doing when the application crashed? hitting "undo" a few times too often, beyond the beginning Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-13-lowlatency #2 SMP PREEMPT Sun Mar 25 00:23:53 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 (389786 sec old) --------------------- (pavucontrol:2344): GLib-GObject-CRITICAL **: g_object_steal_data: assertion `G_IS_OBJECT (object)' failed (pavucontrol:2344): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (pavucontrol:2344): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (pavucontrol:2344): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (pavucontrol:2344): Gtk-CRITICAL **: gtk_menu_item_detacher: assertion `GTK_IS_MENU_ITEM (widget)' failed (pavucontrol:2344): GLib-GObject-CRITICAL **: g_object_steal_data: assertion `G_IS_OBJECT (object)' failed (pavucontrol:2344): GLib-GObject-CRITICAL **: g_object_set_d ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 128685
self[index].inverse()
u.perform()
self.action(*self.action_args)
lambda *args: [self.main_ui.gsd.add_value(*entry) for entry in self.main_ui.cleared.pop()],
self.grid.add(x,y,val,True)
SudokuGrid.add(self,x,y,val,*args,**kwargs)
raise ConflictError(TYPE_ROW,(x,y),val)
*** Bug 433120 has been marked as a duplicate of this bug. ***
*** Bug 433210 has been marked as a duplicate of this bug. ***
*** Bug 433521 has been marked as a duplicate of this bug. ***
*** Bug 437988 has been marked as a duplicate of this bug. ***
*** Bug 440088 has been marked as a duplicate of this bug. ***
*** Bug 442505 has been marked as a duplicate of this bug. ***
*** Bug 445194 has been marked as a duplicate of this bug. ***
*** Bug 438484 has been marked as a duplicate of this bug. ***
*** Bug 450665 has been marked as a duplicate of this bug. ***
*** Bug 458063 has been marked as a duplicate of this bug. ***
*** Bug 437762 has been marked as a duplicate of this bug. ***
*** Bug 438437 has been marked as a duplicate of this bug. ***
*** Bug 452651 has been marked as a duplicate of this bug. ***
*** Bug 459645 has been marked as a duplicate of this bug. ***
*** Bug 461127 has been marked as a duplicate of this bug. ***
*** Bug 461156 has been marked as a duplicate of this bug. ***
*** Bug 466228 has been marked as a duplicate of this bug. ***
*** Bug 466677 has been marked as a duplicate of this bug. ***
*** Bug 467613 has been marked as a duplicate of this bug. ***
*** Bug 468356 has been marked as a duplicate of this bug. ***
*** Bug 472871 has been marked as a duplicate of this bug. ***
*** Bug 473703 has been marked as a duplicate of this bug. ***
*** Bug 488768 has been marked as a duplicate of this bug. ***
*** Bug 484799 has been marked as a duplicate of this bug. ***
*** Bug 499593 has been marked as a duplicate of this bug. ***
*** Bug 500282 has been marked as a duplicate of this bug. ***
*** Bug 504316 has been marked as a duplicate of this bug. ***
Ok -- I've just committed a change that should fix this bug -- the key is to change calls to add_value() to add_value_to_ui() in those cases where we are restoring something a user had written to the grid (add_value() throws an error if a value breaks sudoku rules -- add_value_to_ui() catches this error and handles it). That said, the duplicates here represent a smorgashborg of different, related bugs. My patch gets the following cases (I admit I don't have the energy to look through *all* the dups to see if they are all accounted for -- but I did grep through the code for everything that I believe could have triggered this): * Tracker deletion undo callback * Loading a saved game In addition, an earlier patch should have fixed: * Undo after clearing the grid. This should do it this bug. Please note that not all tracebacks involving ConflictErrors are necessarily dupes of this -- there could be other things at issue. If other bugs marked as dup are not covered by the above cases, please do let me know.
*** Bug 507577 has been marked as a duplicate of this bug. ***
*** Bug 507606 has been marked as a duplicate of this bug. ***
*** Bug 508907 has been marked as a duplicate of this bug. ***
*** Bug 517138 has been marked as a duplicate of this bug. ***
*** Bug 516781 has been marked as a duplicate of this bug. ***
*** Bug 526286 has been marked as a duplicate of this bug. ***
*** Bug 521828 has been marked as a duplicate of this bug. ***
*** Bug 526578 has been marked as a duplicate of this bug. ***
*** Bug 527019 has been marked as a duplicate of this bug. ***
*** Bug 537733 has been marked as a duplicate of this bug. ***
*** Bug 530681 has been marked as a duplicate of this bug. ***
*** Bug 546282 has been marked as a duplicate of this bug. ***
Tom, reopening as per your comment #25. These bugs are all from after your fix was committed: bug # 517138 bug # 530681 bug # 546282 From the comments in those bugs it sounds related to using the Fill All Squares feature.
Never mind. I looked through the stacktraces and the only bug left is the autofill bug (bug #433521). I moved all duplicates to the first report of that bug. This one can be closed again :)