GNOME Bugzilla – Bug 482970
crash in Sudoku: Niks, ik sloot het progr...
Last modified: 2007-10-03 15:31:36 UTC
What were you doing when the application crashed? Niks, ik sloot het programma af (dit ging zonder problemen het programma is gewoon afgesloten). 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 Sun Sep 23 19:50:39 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: MacOS-X Icon Theme: MacOS-X 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 --------------------- save(v)
+ Trace 167416
f(self, obj) # Call unbound method with explicit self
self._batch_setitems(obj.iteritems())
for k, v in items:
(avant-window-navigator:8873): Wnck-WARNING **: Unhandled action type (nil) (avant-window-navigator:8873): Wnck-WARNING **: Unhandled action type (nil) (avant-window-navigator:8873): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `dest_x >= 0 && dest_x + dest_width <= dest->width' failed -------------------------------------------------- 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)
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 ***