Bug 579401

Summary: Pychess fails to start - missing icon
Product: [Fedora] Fedora Reporter: David Nalley <david>
Component: pychessAssignee: Thomas Spura <tomspur>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: michel, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-05 00:27:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Nalley 2010-04-04 23:57:50 UTC
Description of problem: pychess doesn't start


Version-Release number of selected component (if applicable): pychess-0.10-0.3.20100214svn.fc13.noarch


How reproducible: Everytime


Steps to Reproduce:
1. start pychess from commandline
2. see traceback
3.
  
Actual results:
[ke4qqq@nalleyx60 ~]$ pychess 
Traceback (most recent call last):
  File "/usr/bin/pychess", line 45, in <module>
    import pychess.Main
  File "/usr/lib/python2.6/site-packages/pychess/Main.py", line 15, in <module>
    from pychess.widgets import newGameDialog
  File "/usr/lib/python2.6/site-packages/pychess/widgets/newGameDialog.py", line 46, in <module>
    ipeople = it.load_icon("stock_people", 24, gtk.ICON_LOOKUP_USE_BUILTIN)
glib.GError: Icon 'stock_people' not present in theme

Expected results:
chess game

Additional info:

Comment 1 Thomas Spura 2010-04-05 00:27:54 UTC
Thanks for the bug report.

Unfortunately this is a known bug and it will take some time to fix this.
(Also see bug 577570)

There is already some work going at:
http://code.google.com/p/pychess/issues/detail?id=546

But because I'm not familiar with glade and the complete gtk internals of pychess, I require further help from upstrem. Don't know when they will try to fix this...

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