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
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 ***