On my Mageia 1 i586 it works fine, even 3D works.
I had, however, already upgraded to kernel 2.6.38.8-desktop-5.mga, glchess version is the same, python is 2.7.1-6.1

CC: (none) => m.van.waes

I cannot recreate the problem here, using the ati driver.

Can you try using the vesa driver, to see if it's a problem between
glchess and the radeon driver.

CC: (none) => davidwhodgins

(In reply to comment #2)
> I cannot recreate the problem here, using the ati driver.
> 
> Can you try using the vesa driver, to see if it's a problem between
> glchess and the radeon driver.

@ jp jps

I'm curious, too, did you try that?

Excuse me but my practices of Gnu-Linux and english are too poor for me to work in this bugzilla.

I was prompted by "david.david@MLO" to report this bug from MLO to here. I sent him a message to help me because i was not even sure that i was supposed to do something. "david.david" never answered me. Here is the message 

-------------------------------------------------------------------------------------------------------------------------------------
C'est bien de m'encourager à bugziller. Mais ils me poursuivent maintenant !

[url=https://bugs.mageia.org/show_bug.cgi?id=2849]https://bugs.mageia.org/show_bug.cgi?id=2849
[/url]

Je ne sais pas comment fonctionne ce traitement de bug, je ne sais pas si c'est à moi qu'il s'adresse et si c'est à moi de faire le test. Que je ne comprends pas d'ailleurs : je ne sais pas ce qu'est son "vesa driver".

J'ai lancé glchess sur une autre machine, mêmes versions mais driver Nvidia et le symptôme est le même.
[jps@localhost ~]$ cat /etc/issue
Mageia release 1 (Official) for i586
Kernel 2.6.38.8-desktop586-5.mga on an i686 / \l
[jps@localhost ~]$ su
Mot de passe :
[root@localhost jps]# urpmi -qa glchess
Le paquetage glchess-2.32.1-2.mga1.i586 est déjà installé
[root@localhost jps]# urpmi -qa python
Le paquetage python-2.7.1-6.1.mga1.i586 est déjà installé
Le paquetage demandé ne peut pas être installé :
python-2.7.1-6.mga1.i586 (afin de garder python-2.7.1-6.1.mga1.i586)
Désirez-vous tout de même continuer ? (O/n)


Que fais-je ?

Bonsoir, pour faciliter les choses je parle en français, mais normalement ca ne se fait pas.

Lorsque vous reportez un bug, et l'on vous demande plus d'info ou de faire d'autre test, oui c'est bien a vous que cela s'adresse. En effet vous voyez bien qu'ici personne n'est susceptible de reproduire le bug (pas forcement le matériel). Donc cela ne sert à rien un bug auquel vous n'avez aucun suivit.

Dave vous suggère de prendre le driver VESA a la place de celui que vous utilisez actuellement - lequel d'ailleurs ? - (juste pour le test). Cela peut-être fait à partir de XFdrake si ma mémoire est bonne.

Reprise de la discussion en anglais (vu que les autres participants ne comprenne pas ou peu le français. Merci. (des phrases simple en anglais suffise largement ;) )

(for non-french speakers, Manuel answered in french exceptionnally for the bug reporter to understand, they concluded with "back to english now")

CC: (none) => stormi

in /usr/lib/python2.7/site-packages/glchess/display.py try to change
    def updatePiecesStyle(self):
        piecesStyle = config.get('piece_style')
        self.scene.controller.setPiecesStyle(piecesStyle)
to
    def updatePiecesStyle(self):
        piecesStyle = config.get('piece_style')
        print piecesStyle
        self.scene.controller.setPiecesStyle(piecesStyle)

CC: (none) => krytarowski

Check please if your file /usr/lib/python2.7/site-packages/glchess/scene/cairo/__init__.py is present and if yes then attach it..

Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.

@ jp jps

did you see comment 7 and 8 ? could you please reply to them

@ Jani

Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. Don't change anything if you want to be pinged by me in this report again ;)

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested in comment 7 and comment 8, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released.

Users who have experienced this problem are encouraged to upgrade to version 2 of Mageia, and if this issue turns out to still be reproducible in a fully updated Mageia 2, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD