GNOME Bugzilla – Bug 508695
crash in Sudoku: I opened it just for a f...
Last modified: 2008-01-11 10:32:07 UTC
What were you doing when the application crashed? I opened it just for a few seconds and closed it. After it, the Bug reporting tool opened. 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 Tue Dec 18 05:45:12 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 (1238 sec old) --------------------- playeripc: Got command GetPlayerUINT32Prop 0 length playeripc: Got command GetPlayerUINT32Prop 0 playstate playeripc: Got command GetPlayerUINT32Prop 0 position playeripc: Got command GetPlayerUINT32Prop 0 length playeripc: Got command GetPlayerUINT32Prop 0 playstate playeripc: Got command GetPlayerUINT32Prop 0 playstate playeripc: Got command GetPlayerUINT32Prop 0 playstate playeripc: Got command GetPlayerUINT32Prop 0 playstate playeripc: Got command GetPlayerUINT32Prop 0 bwavg playeripc: Got command GetPlayerUINT32Prop 0 position playeripc: Got command GetPlayerUINT32Prop 0 length playeripc: Got command GetPlayerUINT32Prop 0 playstate playeripc: Got command GetPlayerUINT32Prop 0 position playeripc: Got c ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 184899
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 ***