GNOME Bugzilla – Bug 601117
crash in Sudoku: No applications were run...
Last modified: 2009-11-08 01:27:59 UTC
Version: 2.24.1 What were you doing when the application crashed? No applications were running, foreground or background. I was simply starting Sudoku for the first time today. Distribution: openSUSE 11.1 (x86_64) Gnome Release: 2.24.1 2009-06-02 (SUSE) BugBuddy Version: 2.24.1 System: Linux 2.6.27.37-0.1-default #1 SMP 2009-10-15 14:56:58 +0200 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: Gilouche 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 (125 sec old) --------------------- Default Sample Specification: s16le 2ch 44100Hz Default Sink: alsa_output.pci_8086_284b_sound_card_0_alsa_playback_0 Default Source: alsa_input.pci_8086_284b_sound_card_0_alsa_capture_0 Cookie: 00cb4da9 Currently in use: 1 blocks containing 63.9 KiB bytes total. Allocated during whole lifetime: 138 blocks containing 4.2 MiB bytes total. Sample cache size: 0 B User name: PhilEO Host Name: linux-4l3v Server Name: pulseaudio Server Version: 0.9.14 Default Sample Specification: s16le 2ch 44100Hz Default Sink: alsa_output.pci_8086_284b_sound_card_0_alsa_playback_0 Default Source: alsa_input.pci_8086_284b_sound_card_0_alsa_capture_0 Cookie: 00cb4da9 -------------------------------------------------- Traceback (most recent call last):
+ Trace 218919
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 ***