GNOME Bugzilla – Bug 466534
crash in Sudoku:
Last modified: 2007-08-17 01:18:01 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-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 (156 sec old) --------------------- alarm-queue.c:319 (remove_queued_alarm) alarm-queue.c:348 (remove_queued_alarm) - Last Component. Removing CQA- Free=1 alarm-notify.c:337 (alarm_msgport_replied) - 0x8113be0: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x81127e0: Received at thread b3d25b90 alarm-queue.c:1056 (tray_list_remove_cqa_async) - Removing CQA 0x80cf600 from tray list alarm-queue.c:1075 (tray_list_remove_cqa_async) - 0 alarms left. alarm-notify.c:337 (alarm_msgport_replied) - 0x81127e0: Replied to GUI thread alarm-queue.c:793 (query_objects_changed_cb) - Posting a task alarm-queue.c:793 (query_objects_changed_cb) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x811c5f8: Received at thread b3d25b90 alarm-queue.c:699 (query_objects_changed_async) - Querying for object between Thu Jul 26 09:59:56 2007 to Thu Jul 26 09:59:56 2007 alarm-queue.c:724 (query_objects_changed_async) - No currently queued alarms for 439527 alarm-queue.c:447 (add_component_alarms) - Creating CQA 0x811d348 alarm-queue.c:470 (add -------------------------------------------------- Traceback (most recent call last):
+ Trace 155089
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 ***