And I've just confirmed that with the exception of this Ubuntu patch,
all calls to ioctl(..., KDGKBMODE) in the kbd source are using int*, not
long*.  So this is a bug in that patch, which surprisingly didn't bite
us on x86_64 previously but definitely means keymap setting will be
heavily dependent on memory initialization.

Results from the test program might still be interesting in case there's
another bug here, but I've at least identified /a/ bug that needs
fixing.

** Changed in: console-setup (Ubuntu)
       Status: Confirmed => Triaged

** Also affects: console-setup (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: console-setup (Ubuntu Yakkety)
   Importance: Undecided
     Assignee: Taco Screen team (taco-screen-team)
       Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621824

Title:
  MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start
  Set console keymap."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1621824/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to