Description of problem: I got following traceback when running kickstart vnc installation on s390x: anaconda 22.20.1-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/UserDict.py", line 23, in __getitem__ raise KeyError(key) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/progress.py", line 172, in _get_rnotes best_lang = find_best_locale_match(os.environ["LANG"], pixmap_langs) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/progress.py", line 230, in initialize rnotes = self._get_rnotes() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/__init__.py", line 794, in _on_continue_clicked nextAction.initialize() KeyError: 'LANG' kickstart: install lang en_US.UTF-8 keyboard us reboot vnc rootpw redhat timezone --utc America/New_York # partitioning: autopart bootloader --location=mbr zerombr clearpart --all --initlabel autopart %packages @^server-product-environment %end Version-Release number of selected component (if applicable): installation source: http://s390.koji.fedoraproject.org/test/20150312/s390x/os/ anaconda-22.20.1-1 How reproducible: always on s390x Steps to Reproduce: 1. run kickstart installation with the kickstart above Actual results: traceback Expected results: successful installation Additional info: Unable to reproduce during text/cmdline kickstart installation on s390x Unable to reproduce during manual vnc/text installation on s390x Unable to reproduce on x86_64 (with F22 Alpha)
(In reply to Jan Stodola from comment #0) > Additional info: > Unable to reproduce during text/cmdline kickstart installation on s390x > Unable to reproduce during manual vnc/text installation on s390x > Unable to reproduce on x86_64 (with F22 Alpha) s390x is in the unique position of not using tmux and thus not having an initial $LANG set, is why it doesn't happen on other arches.
anaconda-22.20.7-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/anaconda-22.20.7-1.fc22
Package anaconda-22.20.7-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-22.20.7-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4952/anaconda-22.20.7-1.fc22 then log in and leave karma (feedback).
Package anaconda-22.20.7-1.fc22, libblockdev-0.8-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-22.20.7-1.fc22 libblockdev-0.8-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4952/libblockdev-0.8-1.fc22,anaconda-22.20.7-1.fc22 then log in and leave karma (feedback).
anaconda-22.20.7-1.fc22, libblockdev-0.8-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.