GNOME Bugzilla – Bug 468881
crash in Sudoku: Nothing. It did not cras...
Last modified: 2007-08-21 17:08:33 UTC
What were you doing when the application crashed? Nothing. It did not crash. i closed it myself 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 (2335 sec old) --------------------- beryl: Couldn't bind redirected window 0x10021cb to texture beryl: pixmap 0x2c00120 can't be bound to texture beryl: Couldn't bind redirected window 0x10021cb to texture beryl: pixmap 0x2c00120 can't be bound to texture beryl: Couldn't bind redirected window 0x10021cb to texture beryl: pixmap 0x2c00120 can't be bound to texture beryl: Couldn't bind redirected window 0x10021cb to texture beryl: pixmap 0x2c00120 can't be bound to texture beryl: Couldn't bind redirected window 0x10021cb to texture beryl: pixmap 0x2c00120 can't be bound to texture beryl: Couldn't bind redirected window 0x10021cb to texture beryl: pixmap 0x2c00120 can't be bound to texture beryl: Couldn't bind redirected window 0x10021cb to texture ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 156860
self.sudoku_tracker.save()
self.sudoku_maker.save()
ofi)
Pickler(file, protocol).dump(obj)
self.save(obj)
f(self, obj) # Call unbound method with explicit self
self._batch_setitems(obj.iteritems())
save(v)
for k, v in items:
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 ***