Bug 799282

Summary: ImportError: No module named keysyms
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-05 18:51:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
traceback
none
kickstart I used
none
tty1.png
none
anaconda.log
none
anaconda-yum.conf
none
ifcfg.log
none
ks.cfg
none
program.log
none
rsyslog_backend.conf
none
storage.log
none
syslog
none
X.log
none
yum.log none

Description Kamil Páral 2012-03-02 11:36:55 UTC
Created attachment 567035 [details]
traceback

Description of problem:
I discovered this error by accident when doing a kickstart install. I looked onto tty1 and it was there. No dialog popped up and informed me about the traceback.

Since I had "reboot" directive in my kickstart, I couldn't gather more information, I managed just to do a screenshot of the traceback.

I didn't succeed in reproducing this issue.

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

Comment 1 Kamil Páral 2012-03-02 11:37:48 UTC
Created attachment 567036 [details]
kickstart I used

Comment 2 Kamil Páral 2012-03-05 13:38:37 UTC
I saw the problem again, again with kicstarted install. This time I was able to collect logs during the installation.

Comment 3 Kamil Páral 2012-03-05 13:39:03 UTC
Created attachment 567612 [details]
tty1.png

Comment 4 Kamil Páral 2012-03-05 13:40:03 UTC
Created attachment 567613 [details]
anaconda.log

Comment 5 Kamil Páral 2012-03-05 13:40:07 UTC
Created attachment 567614 [details]
anaconda-yum.conf

Comment 6 Kamil Páral 2012-03-05 13:40:11 UTC
Created attachment 567615 [details]
ifcfg.log

Comment 7 Kamil Páral 2012-03-05 13:40:16 UTC
Created attachment 567616 [details]
ks.cfg

Comment 8 Kamil Páral 2012-03-05 13:40:20 UTC
Created attachment 567617 [details]
program.log

Comment 9 Kamil Páral 2012-03-05 13:40:23 UTC
Created attachment 567618 [details]
rsyslog_backend.conf

Comment 10 Kamil Páral 2012-03-05 13:40:27 UTC
Created attachment 567619 [details]
storage.log

Comment 11 Kamil Páral 2012-03-05 13:40:32 UTC
Created attachment 567620 [details]
syslog

Comment 12 Kamil Páral 2012-03-05 13:40:36 UTC
Created attachment 567621 [details]
X.log

Comment 13 Kamil Páral 2012-03-05 13:40:39 UTC
Created attachment 567622 [details]
yum.log

Comment 14 Chris Lumens 2012-03-05 18:51:02 UTC
This comes up from time to time, but we've never been able to figure out a reproducer or really what we could do about it.  Luckily, this code will all be gone when I put in the new UI for F18.