Bug 197355 - Unable to start yumex on fc5
Summary: Unable to start yumex on fc5
Keywords:
Status: CLOSED DUPLICATE of bug 196522
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex
Version: 5
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-30 14:07 UTC by rich
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-07-08 06:11:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description rich 2006-06-30 14:07:02 UTC
Description of problem:
On starting yumex is get the following error

Component: yumex
Version: 1.0.2
Summary: TBe2817d01 yumexmain.py:657:setup_gui:GError: Couldn't recognize the im
age file format for file '/usr/share/pixmaps/yumex/yumex-icon.png'

Traceback (most recent call last):
  File "/usr/share/yumex/yumexmain.py", line 948, in ?
    mainApp = YumexMainApplication()
  File "/usr/share/yumex/yumexmain.py", line 469, in __init__
    self.setup_gui()
  File "/usr/share/yumex/yumexmain.py", line 657, in setup_gui
    gtk.window_set_default_icon_from_file( const.PIXMAPS_PATH + '/yumex-icon.png
' )
GError: Couldn't recognize the image file format for file '/usr/share/pixmaps/yu
mex/yumex-icon.png'

Local variables in innermost frame:
self: <__main__.YumexMainApplication instance at 0xb79d834c>

TIA Rich

Comment 1 Tim Lauridsen 2006-07-07 05:03:27 UTC
Look like a problem with the /usr/share/pixmaps/yumex/yumex-icon.png

Try removing yumex and install it again

yum remove yumex

yum install yumex



Comment 2 rich 2006-07-07 13:57:59 UTC
yes, i tried that before posting the bug. No luck.

Comment 3 Tim Lauridsen 2006-07-08 06:11:38 UTC

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

Comment 4 rich 2006-07-17 13:39:07 UTC
upgrading to gtk2.i386 2.8.20-1 solves the problem.
Thanks


Note You need to log in before you can comment on or make changes to this bug.