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 451316 - crash in Sudoku: I close application and ...
crash in Sudoku: I close application and ...
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-26 17:13 UTC by francuz14
Modified: 2007-06-26 17:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description francuz14 2007-06-26 17:13:44 UTC 
What were you doing when the application crashed?
I close application and then Bug Buddy was open.  I dont see any errors.


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: Human
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 ---------------------
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:3968:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default
ALSA lib confmisc.c:670:(snd_func_card_driver) cannot find card '0'
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:3968:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default
--------------------------------------------------
Traceback (most recent call last):

+ Trace 143895

  • 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-26 17:23:04 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 ***