After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 449584 - crash in Sudoku: I opened the wrong windo...
crash in Sudoku: I opened the wrong windo...
Status: RESOLVED DUPLICATE of bug 409172
Product: gnome-games-superseded
Classification: Deprecated
Component: gnome-sudoku
unspecified
Other All
: High critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-20 19:48 UTC by launchpad
Modified: 2007-06-20 20:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description launchpad 2007-06-20 19:48:16 UTC 
What were you doing when the application crashed?
I opened the wrong window so I closed it. Apparently the Bug reporting tool takes this as crashing even though it was not. I don't know if that's a bug or not. I'm filing this just in case.


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 Thu Jun 7 20:19:32 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Human

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 (344244 sec old) ---------------------
[00000341] alsa audio output debug: opening ALSA device `hw:0,0'
[00000341] main audio output debug: thread 2912295824 (aout) created at priority 0 (alsa.c:662)
[00000341] main audio output debug: using audio output module "alsa"
[00000341] main audio output debug: output 's16l' 44100 Hz Stereo frame=1 samples/4 bytes
[00000341] main audio output debug: mixer 'fl32' 44100 Hz Stereo frame=1 samples/8 bytes
[00000341] main audio output debug: filter(s) 'fl32'->'s16l' 44100 Hz->44100 Hz Stereo->Stereo
[00000342] main private debug: looking for audio filter module: 24 candidates
[00000342] main private debug: using audio filter module "float32tos16"
[00000341] main audio output debug: found a filter for the whole conversion
[00000341] main audio output debug: looking for audio mixer module: 3 candidates
[00000341] main audio output debug: using audio mixer module "float32_mixer"
[00000341] main audio output debug: input 'mpga' 44100 Hz Stereo frame=1152 samples/1053 bytes
[00000341] main audio output debug: filter(s) 'mpga'->'fl32' 44100 Hz->44100 Hz Stereo->Stereo
...Too much output, ignoring rest...
--------------------------------------------------
Traceback (most recent call last):

+ Trace 142506

  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py", line 544 in quit_cb 
    self.sudoku_tracker.save()
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku_maker.py", line 476 in save 
    self.sudoku_maker.save()
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku_maker.py", line 425 in save 
    ofi)
  • File "pickle.py", line 1362 in dump 
    Pickler(file, protocol).dump(obj)
  • File "pickle.py", line 224 in dump 
    self.save(obj)
  • File "pickle.py", line 286 in save 
    f(self, obj) # Call unbound method with explicit self
  • File "pickle.py", line 649 in save_dict 
    self._batch_setitems(obj.iteritems())
  • File "pickle.py", line 663 in _batch_setitems 
    save(v)
  • File "pickle.py", line 286 in save 
    f(self, obj) # Call unbound method with explicit self
  • File "pickle.py", line 649 in save_dict 
    self._batch_setitems(obj.iteritems())
  • File "pickle.py", line 661 in _batch_setitems 
    for k, v in items:
RuntimeError: dictionary changed size during iteration 






Comment 1


Thomas Andersen





          2007-06-20 20:01:28 UTC
        



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 409172 ***