GNOME Bugzilla – Bug 560059
crash in Sudoku: I moved the application ...
Last modified: 2008-11-09 20:03:50 UTC
Version: 2.24.1 What were you doing when the application crashed? I moved the application window from the left to the center of the screen Distribution: Ubuntu 8.10 (intrepid) Gnome Release: 2.24.1 2008-10-24 (Ubuntu) BugBuddy Version: 2.24.1 System: Linux 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10502000 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 (51767 sec old) --------------------- alarm-queue.c:1821 (check_midnight_refresh) alarm*** NSPlugin Viewer *** ERROR: NPN_GetValue() invoke: Message type invalid *** NSPlugin Viewer *** WARNING: unhandled variable 15 in NPN_GetValue() *** NSPlugin Viewer *** ERROR: NPN_GetURLNotify() invoke: Message type invalid *** NSPlugin Viewer *** ERROR: NPN_GetValue() invoke: Message type invalid *** NSPlugin Viewer *** WARNING: unhandled variable 15 in NPN_GetValue() *** NSPlugin Viewer *** ERROR: NPN_GetURLNotify() invoke: Message type invalid (npviewer.bin:12983): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed (npviewer.bin:12983): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed (npviewer.bin:12983): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 209540
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 ***