Red Hat Bugzilla – Bug 752669
Last modified: 2013-02-13 11:08:56 EST
libreport version: 2.0.6
reason: KeyError: 'us-ctrl_capslock'
time: Thu Nov 10 04:31:35 2011
anaconda-tb-L7e4Ba: Text file, 267592 bytes
:The following was filed automatically by anaconda:
:anaconda 16.25 exception report
:Traceback (most recent call first):
: File "/usr/lib/python2.7/site-packages/system_config_keyboard/keyboard.py", line 81, in set
: kb = self.modelDict[keytable]
: File "/usr/lib/python2.7/site-packages/pyanaconda/kickstart.py", line 429, in execute
: File "/usr/lib/python2.7/site-packages/pyanaconda/kickstart.py", line 1226, in execute
: File "/usr/lib/python2.7/site-packages/pyanaconda/kickstart.py", line 1277, in doKickstart
: File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 373, in dispatch
: self.dir = self.steps[self.step].target(self.anaconda)
: File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 88, in return_false
: func(*args, **kwargs)
Created attachment 532718 [details]
Shortly after installing Fedora 15 in the distant past, I had created
and modified /etc/sysconfig/keyboard to set
in order to use the new keymap, swapping control and caps-lock keys in text mode.
When upgrading to Fedora 16 using preupgrade, after reboot into the installer
the keyboard configuration code evidently determined that it did not know
about the us-ctrl_capslock map, and so it popped up a dialog allowing me to
chose a keymap; I chose the 'us' map. However, apparently not all the software
got the word that the keymap was changed from 'us-ctrl_capslock' to 'us', and
keyboard.py got the exception above due to the unknown key.
I was able to recover by rebooting into the old Fedora 15 kernel and
removing us-ctrl_capslock.map.gz and setting the KEYBOARD back to "us" in
/etc/sysconfig/keyboard, then re-running preupgrade.
This bug probably does not affect a large number of people, but it does look
like a partial attempt was made to handle the case of a keymap unknown to the
installer, but that attempt just did not go far enough.
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.