GNOME Bugzilla – Bug 603064
crash in Sudoku: I was starting it. It br...
Last modified: 2009-11-26 19:04:28 UTC
Version: 2.24.1 What were you doing when the application crashed? I was starting it. It brought up the window with the play area black and then this window. First I hit cancel, then started it again, same result. Distribution: openSUSE 11.1 (i586) Gnome Release: 2.24.1 2009-06-02 (SUSE) BugBuddy Version: 2.24.1 System: Linux 2.6.27.29-0.1-default #1 SMP 2009-08-15 17:53:59 +0200 i686 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux 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 (5055 sec old) --------------------- Default Sample Specification: s16le 2ch 44100Hz Default Sink: alsa_output.pci_8086_293e_sound_card_0_alsa_playback_0 Default Source: alsa_input.pci_8086_293e_sound_card_0_alsa_capture_0 Cookie: 085cecd4 Currently in use: 1 blocks containing 64.0 KiB bytes total. Allocated during whole lifetime: 1109024 blocks containing 3.7 GiB bytes total. Sample cache size: 0 B User name: hmeyer Host Name: linux-p7d6 Server Name: pulseaudio Server Version: 0.9.14 Default Sample Specification: s16le 2ch 44100Hz Default Sink: alsa_output.pci_8086_293e_sound_card_0_alsa_playback_0 Default Source: alsa_input.pci_8086_293e_sound_card_0_alsa_capture_0 Cookie: 085cecd4 -------------------------------------------------- Traceback (most recent call last):
+ Trace 219308
start_game()
main.start_game()
u = UI()
if self.select_game():
ret = fun(ui,*args,**kwargs)
choice = game_selector.NewOrSavedGameSelector().run_swallowed_dialog(self.swallower)
self.setup_dialog()
self.make_saved_game_model()
sudoku.sudoku_grid_from_string(g['game'].split('\n')[1].replace(' ','')).grid,
assert(len(s)<=GROUP_SIZE**2) AssertionError
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 bug 516491 ***