GNOME Bugzilla – Bug 468016
crash in Sudoku: Burning audio cd's. Usin...
Last modified: 2007-08-19 00:30:34 UTC
What were you doing when the application crashed? Burning audio cd's. Using Serpentine while using bit torrent to download a torrent. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.15-28-386 #1 PREEMPT Wed Jul 18 22:50:32 UTC 2007 i586 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy 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 (15 sec old) --------------------- self._batch_setitems(obj.iteritems())
+ Trace 156197
save(v)
f(self, obj) # Call unbound method with explicit self
self._batch_setitems(obj.iteritems())
for k, v in items:
xscreensaver: 14:53:02: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received xscreensaver: 14:53:02: 0: for window 0x3600383 (gnome-btdownload / Gnome-btdownload) xscreensaver: 14:54:17: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received xscreensaver: 14:54:17: 0: for window 0x24064f2 (serpentine / Serpentine) -------------------------------------------------- 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 ***