ubuntustudio-bugs team mailing list archive

[Aaron Rainbolt <2084001@xxxxxxxxxxxxxxxxxx>]

Sorry for the very slow reply, been very busy and haven't been checking
my bug mail.

The keyboard layout order is determined by Calamares, or whatever it's
using to set the keyboard layouts. The first layout in that order is the
default, and the user has to explicitly hit a key combo to change it, so
it's most likely that the first one is correct.

Arguably *if* the user changes their keyboard layout with a key combo,
the chosen keyboard layout should be used. Doing that will require
significantly more complicated code however since the only way to get
the "real" current keyboard layout to my awareness is to use some C
code. This would fix the issue Skia hit.

Also, all of the above will break with Wayland. Hmm...

** Changed in: calamares-settings-ubuntu (Ubuntu)
       Status: Incomplete => New

** Also affects: calamares-settings-ubuntu (Ubuntu Plucky)
   Importance: Undecided
       Status: New

** Changed in: calamares-settings-ubuntu (Ubuntu Oracular)
       Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to calamares-settings-ubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/2084001

Title:
  fixconkeys-part1 malfunctions if more than one keyboard layout is
  active at once at installation time

Status in calamares-settings-ubuntu package in Ubuntu:
  New
Status in calamares-settings-ubuntu source package in Oracular:
  Won't Fix
Status in calamares-settings-ubuntu source package in Plucky:
  New

Bug description:
  The fixconkeys-part1 script currently uses the "layout" field of the
  output of `setxkbmap -query` to determine what keyboard layout to set
  at the console level, which makes the disk decryption prompt work. The
  problem is it assumes this field will only ever list one keyboard
  layout, when in reality it can list multiple keyboard layouts
  separated by commas. When this happen, the keyboard will silently fail
  to be properly set up.

  To fix this, only the first keyboard layout returned by `setxkbmap
  -query` should be taken into account. This isn't a perfect solution,
  but it's better than the current situation and is safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2084001/+subscriptions