GNOME Bugzilla – Bug 482626
crash in Sudoku:
Last modified: 2007-10-02 15:59:52 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 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 (4553 sec old) --------------------- Oct 2 14:18:08 ubiquity: 'resize_min_size': 3200000000.0}, Oct 2 14:18:08 ubiquity: u'/var/lib/partman/devices/=dev=sda//32256-27217451519': {'acting_filesystem': 'ntfs', Oct 2 14:18:08 ubiquity: 'can_resize': True, Oct 2 14:18:08 ubiquity: 'detected_filesystem': 'ntfs', Oct 2 14:18:08 ubiquity: 'dev': u'=dev=sda', Oct 2 14:18:08 ubiquity: 'display': u'> Nr. 1 prim\xe4r 27.2 GB B K ntfs /media/sda1\xa0\xa0', Oct 2 14:18:08 ubiquity: 'existing': '', Oct 2 14:18:08 ubiquity: 'filesystem': 'ntfs', Oct 2 14:18:08 ubiquity: 'id': u'32256-27217451519', Oct 2 14:18:08 ubiquity: 'method': 'keep', Oct 2 14:18:08 ubiquity: 'method_choices': [(u'25filesystem', Oct 2 14:18:08 ubiquity: u'ext3', Oct 2 14:18:08 ubiquity: u'Ext3-Journaling-Dateisystem'), ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 167157
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 ***