[Bug 520546] Please test proposed package

[Robie Basak]

Hello David, or anyone else affected,

Accepted console-setup into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu2.9 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Committed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Committed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Committed
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Workaround]

  Reboot (or restart X) and the problem will go away.

  [Test Case]

  [racb] Note that upgrading to the fixed package will not fix the
  problem for affected users; you must reboot (or restart X) as above.
  The fix only prevents the problem occurring again.

   * Ssh to a system or open a terminal and unset DISPLAY

      $ echo $DISPLAY

      $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same:

     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * The unfixed package sets the kbd mode to unicode:

     $  sudo kbd_mode
     The keyboard is in Unicode (UTF-8) mode
     $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this should also be tested.
   * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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