GNOME Bugzilla – Bug 468695
crash in Sudoku: i play on sudoku
Last modified: 2007-08-20 23:28:55 UTC
What were you doing when the application crashed? i play on sudoku Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Tangerine 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 --------------------- self._batch_setitems(obj.iteritems())
+ Trace 156704
save(v)
f(self, obj) # Call unbound method with explicit self
self._batch_setitems(obj.iteritems())
for k, v in items:
ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_plugin.so ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_plugin.so ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_plugin.so ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_plugin.so -------------------------------------------------- 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())
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 ***