GNOME Bugzilla – Bug 651373
crash in Chess: open
Last modified: 2011-05-29 05:42:39 UTC
Version: 2.32.1 What were you doing when the application crashed? open Distribution: openSUSE 11.4 (i586) Gnome Release: 2.32.1 (null) (SUSE) BugBuddy Version: 2.32.0 System: Linux 2.6.37.6-0.5-default #1 SMP 2011-04-25 21:48:33 +0200 i686 X Vendor: The X.Org Foundation X Vendor Release: 10903000 Selinux: No Accessibility: Disabled GTK+ Theme: Sonar Icon Theme: Sonar GTK+ Modules: gnomesegvhandler, canberra-gtk-module 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 Traceback (most recent call last):
+ Trace 227300
function(name, value)
self.updatePiecesStyle()
self.scene.controller.setPiecesStyle(piecesStyle)
----------- .xsession-errors (214 sec old) --------------------- xscreensaver: 09:07:04: couldn't grab keyboard! (AlreadyGrabbed) xscreensaver: 09:07:08: couldn't grab keyboard! (AlreadyGrabbed) xscreensaver: 09:07:08: unable to grab keyboard or mouse! Blanking aborted. *** nss-shared-helper: Shared database disabled (set NSS_USE_SHARED_DB to enable). (gpk-update-icon:1546): PackageKit-DEBUG: notify::connected (gpk-update-icon:1546): PackageKit-DEBUG: refreshing task list (gpk-update-icon:1546): PackageKit-DEBUG: refreshing task list (gpk-update-icon:1546): PackageKit-DEBUG: notify::connected (gpk-update-icon:1546): PackageKit-DEBUG: notify::connected (gpk-update-icon:1546): PackageKit-DEBUG: refreshing task list (gpk-update-icon:1546): PackageKit-DEBUG: refreshing task list (gpk-update-icon:1546): PackageKit-DEBUG: notify::connected ** (pcmanfm:1541): DEBUG: icon theme changed! ** (pcmanfm:1541): DEBUG: icon theme changed! ** (pcmanfm:1541): DEBUG: icon theme changed! --------------------------------------------------
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 bug 629125 ***