After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 657896 - crash in Chess: estaba viendo un video
crash in Chess: estaba viendo un video
Status: RESOLVED DUPLICATE of bug 629125
Product: gnome-games-superseded
Classification: Deprecated
Component: BugBuddyBugs
2.32.x
Other All
: Normal critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2011-09-01 05:57 UTC by jcamilo1020
Modified: 2011-09-01 09:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Description jcamilo1020 2011-09-01 05:57:31 UTC 
Version: 2.32.1

What were you doing when the application crashed?
estaba viendo un video


Distribution: openSUSE 11.4 (i586)
Gnome Release: 2.32.1 (null) (SUSE)
BugBuddy Version: 2.32.0

System: Linux 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10 +0100 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 228304

  • File "/usr/lib/python2.7/site-packages/glchess/config.py", line 179 in _watch 
    function(name, value)
  • File "/usr/lib/python2.7/site-packages/glchess/display.py", line 361 in __onPiecesStyleChanged 
    self.updatePiecesStyle()
  • File "/usr/lib/python2.7/site-packages/glchess/display.py", line 429 in updatePiecesStyle 
    self.scene.controller.setPiecesStyle(piecesStyle)
AttributeError: Scene instance has no attribute 'setPiecesStyle' 


----------- .xsession-errors ---------------------
** (gnome-session:1593): DEBUG: GsmManager: Client removed: /org/gnome/SessionManager/Client12
** (gnome-session:1593): DEBUG: GsmClient: disposing /org/gnome/SessionManager/Client12
** (gnome-session:1593): DEBUG: GsmXSMPClient: xsmp_finalize (0x80dc460 [firefox 106f72533a39a36337131485651788840600000015930038])
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1593): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
--------------------------------------------------
Comment 1 André Klapper 2011-09-01 09:15:32 UTC 
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 been fixed in version 3.0.
You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 629125 ***