GNOME Bugzilla – Bug 467868
crash in Chess: Щелкнул по иконке и полу...
Last modified: 2007-08-18 12:26:34 UTC
Version: 2.19.6 What were you doing when the application crashed? Щелкнул по иконке и получил в ответ написать багрепорт. Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.19.6 2007-08-09 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.20-gentoo-r8 #5 PREEMPT Fri Jul 27 16:24:27 MSD 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Water Vapor Icon Theme: Vista-Inspirate_1.0 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 (4880675 sec old) --------------------- SIM-IM: 22/06/2007 20:23:47 [WRN] Unknown roster type 0020 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 SIM-IM: 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 SIM-IM: 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 SIM-IM: 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 SIM-IM: 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 SIM-IM: 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 SIM-IM: 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 SIM-IM: 22/06/2007 20:23:47 [WRN] Unknown roster type 0019 -------------------------------------------------- Traceback (most recent call last):
+ Trace 156072
start_game()
app = main.Application()
self.ui = UI(self)
self.controller = gtkui.GtkUI(self)
self.defaultViewController = self.notebook.setDefault(None)
self.defaultView = chessview.GtkView(self.ui, '', feedback)
tooltip.tip_window.ensure_style()
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 459740 ***