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 651836 - crash in Chess: surfing the internet wi...
crash in Chess: surfing the internet wi...
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-06-04 04:07 UTC by house666
Modified: 2011-06-04 11:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Description house666 2011-06-04 04:07:50 UTC 
Version: 2.32.1

What were you doing when the application crashed?
surfing the internet  with firfox and listening to music with banshee


Distribution: openSUSE 11.4 (x86_64)
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 x86_64
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 227375

  • 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:1699): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1699): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1699): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1699): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1699): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1699): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
*** NSPlugin Viewer  *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
*** NSPlugin Viewer  *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
*** NSPlugin Wrapper *** ERROR: NPP_Destroy() wait for reply: Connection reset by peer
*** NSPlugin Wrapper *** ERROR: NPObject 0x7f91cedbfab0 is no longer valid!
** (gnome-session:1699): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1699): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1699): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1699): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1699): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
--------------------------------------------------
Comment 1 Akhil Laddha 2011-06-04 11:59:31 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 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 ***