GNOME Bugzilla – Bug 558687
crash in Sudoku:
Last modified: 2008-11-01 12:56:19 UTC
Version: 2.24.1 What were you doing when the application crashed? 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 Fri Oct 24 06:42:44 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: BlackGarden Icon Theme: gnome 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 (10 sec old) --------------------- Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x3a00025 especificada para 0x3a0002a (Warning - ). Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x3a00025 especificada para 0x3a0002a (Warning - ). Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x3a00007 especificada para 0x3a0005d (Initial Se). Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x3a00058 especificada para 0x3a0005d (Initial Se). Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x3a00058 especificada para 0x3a0005d (Initial Se). Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x3a00058 especificada para 0x3a00080 (Question). Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x3a00058 especificada para 0x3a00080 (Question). Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x3a00058 especificada para 0x3a0005d (Initial Se). Traceback (most recent call last):
+ Trace 208973
self.toggle_timing(False)
self.tot_time_complete += end_time - self.__absolute_start_time__
-------------------------------------------------- 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 ***