GNOME Bugzilla – Bug 560710
crash in Sudoku: I resumed a saved game (...
Last modified: 2008-11-14 15:35:51 UTC
Version: 2.24.1 What were you doing when the application crashed? I resumed a saved game (likely saved by a previous version). When trying to edit the notes on a cell, gnome-sudoku crashed. I've gotten three crashes so far. Distribution: Ubuntu 8.10 (intrepid) Gnome Release: 2.24.1 2008-10-24 (Ubuntu) BugBuddy Version: 2.24.1 System: Linux 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche2 Icon Theme: Tango 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 (3323 sec old) --------------------- at System.Net.HttpWebRequest.GetResponse () [0x00000] at Mono.Addins.Setup.AddinStore.DownloadFile (IProgressMonitor monitor, System.String url) [0x00000] at Mono.Addins.Setup.AddinStore.DownloadObject (IProgressMonitor monitor, System.String url, System.Type type) [0x00000] at Mono.Addins.Setup.RepositoryRegistry.UpdateRepository (IProgressMonitor monitor, System.Uri baseUri, Mono.Addins.Setup.RepositoryRecord rr) [0x00000] (soffice:24432): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated ====================== libparted : 1.8.9 ====================== (Do:24438): Gnome-CRITICAL **: gnome_program_get_app_id: assertion `program != NULL' failed (Do:24438): GConf-CRITICAL **: gconf_escape_key: assertion `arbitrary_text != NULL' failed (Do:24438): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 209753
self.toggle_timing(False)
self.tot_time_complete += end_time - self.__absolute_start_time__
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 557308 ***