[15:36] acheronuk: right now you want to look at what the KeyError was [15:36] yeah, just struggling with my deb skills [15:37] *debug [15:37] set_keyboard runs, tries to get the real name of the thing for setxkbmap or whatever else by looking it up in kbdnames.gz [15:38] probably need to try in a normal ubuntu VM to see what the correct values are, then compare [15:38] hrm, otoh, it' s normal that there might be one KeyError first, and then it tries again with "C" as the lang [15:39] wait, wtf [15:39] debconf (developer): <-- METAGET keyboard-configuration/layout choices-c [15:39] debconf (developer): --> 1 Afghani, Albanisch, Amharisch, Arabisch, Arabisch (Marokko), Arabisch (Syrien), Armenisch, Aserbaidschanisch, Bambara, Bangla, Belgisch, Berber (Algerien\\, lateinische Schrift), Bosnisch, Braille, Bulgarisch, Burmesisch, Chinesisch, Dänisch, Deutsch, Deutsch (Österreich), Dhivehi, Dzongkha, Englisch (Australien), Englisch (B [15:40] well job, debconf. this isn't -c ;) [15:41] sorry? [15:41] choices-c is supposed to be untranslated strings, I think [15:42] those are clearly in de [15:42] so something isn't quite right [15:49] I'm hoping this isn't a big deep rabbit hole, but it looks really odd, and right now I'm unable to find where choices-c might get from untranslated to translated [15:51] this must be blowing up in Gtk as well [15:54] debconf (developer): <-- METAGET keyboard-configuration/layout choices-c [15:54] ^^^ that gets the translated in gtk as well [15:54] but no keyerror [15:57] ok [15:57] still in Deutsch though? [15:58] (the GET keyboard-configuration/layout just after METAGET) [15:59] cyphermox: https://i.imgur.com/MyPJgdF.png [16:01] yeah ok, this is just python catching the error [16:01] might explain a lot of fubar setting keyboard values, tbh [16:02] odd that Kubuntu throws the error and Ubuntu does not [16:03] yeah, it' s a red herring, I think [16:03] sorry, everytime I look at this I need to start from the top, the code is really complicated :/ [16:04] cyphermox: lol. think about how I see it! :P [16:04] 1st time looking and not really sure what I'm looking at [16:04] :D [16:07] well, you try to follow the leads really, one thing at a time [16:07] so looking at UbiquityDebug there' s a whole lot of stuff [16:07] and I got tripped by the KeyError [16:07] (it' s still wrong, I' m pretty sure, but probably not why it blows up for just KDE) [16:08] CHOICES-C should really not be translated, that' s what -C is for :) [16:08] then you got the error with code 141 after it, while running sorry, everytime I look at this I need to start from the top, the code is really complicated : /usr/lib/ubiquity/console-setup/keyboard-configuration.postinst [16:08] oops [16:09] sorry about that, but the filename is good [16:09] /usr/lib/ubiquity/console-setup/keyboard-configuration.postinst [16:09] ^ there' s an error running that [16:09] right [16:09] and just afterwards, you still got some debconf GETs that look like what that script does at lines 41-51 [16:10] something just after that must be failing. [16:10] acheronuk: could you try to get to the keyboard panel in the Kubuntu installer (picking the language but not hitting Next), then open a terminal and try to run the commands in that script? [16:10] might find what is unhappy [16:11] really need a 'duh' emoji on here. I completely missed that code was from the postinst! [16:11] or run through the installer, up to the point it crashes, and check what you have in /etc/default/keyboard [16:11] hey, I didn' t remember either [16:12] I was wondering what was throwing a 141 from the ubiquity python code [16:17] ok. I may have to come back to this later, or later in the week [16:17] cyphermox: thanks so far :) [16:21] cyphermox: if I choose a non english language to start with, and so get the error, I never see the keyboard choice page :/ [16:22] skips straight to the software choices page (e.g. minimal/normal install etc) [16:25] * acheronuk pokes tsimonq2 [16:25] can haz calamares? [16:25] :P [16:28] acheronuk: yeah, as long as you get to that point it' s fine -- the keyboard page " has run" [16:30] right. I'll try to find some way to work out what in the postinst is falling over [20:38] hey all [20:40] trying to sort out an automated deployment of ubuntu 18.04, but getting confused on should I use the d-i or Ubiquity [20:40] and where do I find more information about the syntax around partitioning?