GNOME Bugzilla – Bug 459966
crash in Chess: just entered glchess in ...
Last modified: 2007-07-25 00:16:51 UTC
What were you doing when the application crashed? just entered glchess in terminal and pressed enter Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.5 2007-07-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Blubuntu 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 (35 sec old) --------------------- Adding plugin rotate (rotate) Adding plugin crashhandler (crashhandler) Initializing core options...done Initializing move options...done Initializing annotate options...done Initializing svg options...done Initializing decoration options...done Initializing expo options...done Initializing ring o/usr/bin/compiz.real (blur) - Warn: No stencil buffer. Region based blur disabled /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format /usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. PID TTY TIME CMD /usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. /usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. /usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. -------------------------------------------------- Traceback (most recent call last):
+ Trace 150266
start_game()
app = main.Application()
self.ui = UI(self)
self.controller = gtkui.GtkUI(self)
tooltip.tip_window.ensure_style()
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 459740 ***