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 468824 - crash in Sudoku: When open gnome-sudoku h...
crash in Sudoku: When open gnome-sudoku h...
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-08-21 12:18 UTC by theory_mach
Modified: 2007-08-21 12:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description theory_mach 2007-08-21 12:18:07 UTC
What were you doing when the application crashed?
When open gnome-sudoku have bug


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.1 2007-04-10 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 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 (902 sec old) ---------------------
** Message: Missing plugin: gstreamer.net|0.10|totem|MPEG-1 Layer 3 (MP3) decoder|decoder-audio/mpeg, mpegversion=(int)1, layer=(int)3 (MPEG-1 Layer 3 (MP3) decoder)
** (gnome-codec-install:8951): WARNING **: return value of custom widget handler was not a GtkWidget
/usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1118: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed
  model.set_default_sort_func(None)
Window manager warning: Window 0x2a03b7a () sets an MWM hint indicating it isn't resizable, but sets min size 486 x 278 and max size 2147483647 x 2147483647; this doesn't make much sense.
Window manager warning: Window 0x2a03b7a () sets an MWM hint indicating it isn't resizable, but sets min size 486 x 278 and max size 2147483647 x 2147483647; this doesn't make much sense.
** Message: Missing plugins installed. Updating plugin registry ...
** Message: Plugin registry updated, trying again.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2800003 specified for 0x2800332 (Keep Resol).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2800003 specified for 0x280074b (Keep Resol).
(gnome-terminal:9302): Vte-WARNING **: Can not find appropiate font for character U+0006.
--------------------------------------------------
Traceback (most recent call last):
  • 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-08-21 12:47:08 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 ***