GNOME Bugzilla – Bug 558999
crash in Sudoku: Double clicking to enter...
Last modified: 2008-11-03 19:50:44 UTC
Version: 2.24.1 What were you doing when the application crashed? Double clicking to enter a note in the field. 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 Thu Oct 30 04:18:38 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Moomex 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 --------------------- self.theme["sun"+ self.get_icon(int(weather[6]["dayicon"])) + ".svg"].render_cairo(ctx) ValueError: invalid literal for int() with base 10: '' Traceback (most recent call last):
+ Trace 209125
self.toggle_timing(False)
self.tot_time_complete += end_time - self.__absolute_start_time__
(bug-buddy:19618): Gtk-WARNING **: Error parsing gtk-icon-sizes string: 'panel-menu=24,24 panel=20,20 gtk-button=18,18 gtk-large-toolbar=24,24' -------------------------------------------------- Traceback (most recent call last):
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 Thu Oct 30 04:18:38 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Moomex 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 --------------------- self.theme["sun"+ self.get_icon(int(weather[6]["dayicon"])) + ".svg"].render_cairo(ctx) ValueError: invalid literal for int() with base 10: '' Traceback (most recent call last):
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 ***