Bug 579708 - RuntimeError: Unable to find glade file exn.glade
Summary: RuntimeError: Unable to find glade file exn.glade
Keywords:
Status: CLOSED DUPLICATE of bug 222513
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-06 10:53 UTC by Alexander Todorov
Modified: 2010-11-09 13:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-06 13:07:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alexander Todorov 2010-04-06 10:53:43 UTC
Description of problem:
During install I saw this traceback on tty1

Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/bin/anaconda", line 971, in <lambda>
  File "/usr/lib/anaconda/exception.py", line 353, in handleException
  File "/usr/lib/anaconda/gui.py", line 1041, in exceptionWindow
  File "/usr/lib/anaconda/gui.py", line 760, in __init__
  File "/usr/lib/anaconda/gui.py", line 408, in findGladeFile
RuntimeError: Unable to find glade file exn.glade

Original exception was:
Traceback (most recent call last):
  File "/usr/lib/anaconda/gui.py", line 172, in handleShiftPrintScrnRelease
  File "/usr/lib/python2.4/site-packages/gtk-2.0/gtk/_lazyutils.py", line 32, in __getattr__
ImportError: No module named keysyms


Version-Release number of selected component (if applicable):
anaconda-11.1.2.209-1

How reproducible:
1/1

Steps to Reproduce:
1. I was performing a kickstart install from a satellite server. This is a Xen PV guest. While observing the install over VNC I've just noticed the traceback.
2.
3.
  
Actual results:
Traceback. Doesn't seem to be harmful.

Expected results:


Additional info:
Installation completes, so this is probably cosmetic. This was found while trying to reproduce bug #577334.

The original exception: ImportError: No module named keysyms was also seen in bug #577334 comment #13 and similar issue is reported against RHEL6 in bug #525065

Comment 1 Chris Lumens 2010-04-06 13:07:08 UTC
Given that the original traceback is the keysyms ImportError, I'm duping this to another one that has tracked that issue for RHEL5.  I don't trust the second traceback after that since we're already in an unusual error condition.

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


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