Bug 651322 – crash in Chess: changing settings

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 651322 - crash in Chess: changing settings


Summary:	crash in Chess: changing settings


Status:	RESOLVED DUPLICATE of bug 629125

Product:	gnome-games-superseded
Classification:	Deprecated
Component:	BugBuddyBugs
Version:	2.32.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	GNOME Games maintainers
QA Contact:	GNOME Games maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-05-28 12:17 UTC by frank_guz
Modified:	2011-05-28 15:43 UTC

See Also:
GNOME target:	---
GNOME version:	2.31/2.32

Description frank_guz 2011-05-28 12:17:24 UTC

Version: 2.32.0

What were you doing when the application crashed?
changing settings


Distribution: Ubuntu 10.10 (maverick)
Gnome Release: 2.32.0 2010-09-27 (Ubuntu)
BugBuddy Version: 2.31.92

System: Linux 2.6.35-28-generic #50-Ubuntu SMP Fri Mar 18 18:42:20 UTC 2011 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome
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 227293

File "/usr/lib/pymodules/python2.6/glchess/config.py", line 179 in _watch
```
function(name, value)
```
File "/usr/lib/pymodules/python2.6/glchess/display.py", line 361 in __onPiecesStyleChanged
```
self.updatePiecesStyle()
```
File "/usr/lib/pymodules/python2.6/glchess/display.py", line 429 in updatePiecesStyle
```
self.scene.controller.setPiecesStyle(piecesStyle)
```

AttributeError: Scene instance has no attribute 'setPiecesStyle'



----------- .xsession-errors ---------------------
    self.scene.controller.setPiecesStyle(piecesStyle)
AttributeError: Scene instance has no attribute 'setPiecesStyle'
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1678): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
--------------------------------------------------

Comment 1 André Klapper 2011-05-28 15:43:09 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 ***