OEM install does not work when set to Spanish in neon-useredition/20180329-1021 It crashes when trying to set up the keyboard
oem-config.log https://www.flickr.com/photos/jriddell/39420266520/sizes/l
Installing in English with English UK keyboard is fine
Traceback (most recent call last): File "/usr/lib/ubiquity/plugins/ubi-console-setup.py", line 348, in set_keyboard ly = keyboard_names.layout_id(lang, misc.utf8(layout)) File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 142, in layout_id return kn.layout_id(lang, value) File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 90, in layout_id return self._layout_by_human[value] KeyError: 'Español'
Other reports https://forum.kde.org/viewtopic.php?f=309&t=151748&p=396936#p396916
Works fine in user image from February No packages are missing between the two The version of Ubiquity has changed console-setup verson has changed in the ubiquity
Problem is that /usr/lib/ubiquity/console-setup/kdbnames.gz does not contain all the tranlated names. Now whyever could that be? ...
-ubiquity (2.21.63.6+p16.04+git20180216.0106) xenial; urgency=medium +ubiquity (2.21.63.6+p16.04+git20180320.0141) xenial; urgency=medium old one works, new one does not, source has no changes
ubiquity debian/rules runs d-i/source/console-setup/Keyboard/kbdnames-maker d-i/source/console-setup/Keyboard/KeyboardNames.pl | gzip -9c > debian/kbdnames.gz This gets list of languages from xkb-data-i18n and its installed xkeyboard-config.mo files which does install fine in the latest ubiquity build
Building ubiquity locally is fine but using the docker image on drax to build it I end up with /usr/share/locale/ empty except for en en_GB which explains why kbdnames.gz is mostly empty.
This could be it cat /etc/apt/apt.conf.d/docker-no-languages Acquire::Languages "none";
Hmm there's also a 00aptitude which sets the same setting but removing them doesn't make any difference, still only en in /usr/share/locale/
Meh dunno why Docker is not installing the translations so I just did a workaround of including the keyboard names file directly in the packaging. I'm working on a n openqa test to check this problem doesn't re-occur automatially
test at https://build.neon.kde.org/job/openqa_xenial_useredition_installation_nonenglish/