The verification of the Stable Release Update for kbd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

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

Status in kbd package in Ubuntu:
  Fix Released
Status in kbd source package in Xenial:
  Fix Released
Status in kbd source package in Yakkety:
  Fix Released

Bug description:
  [SRU Justification]
  On ppc64el, console keyboard maps will not be set at boot time because of a 
bug in detecting which VT is "safe" to use for setting the map.  This problem 
does not affect amd64 purely by chance, or because of which toolchain version 
or toolchain options were used to build the binary on each architecture; a 
rebuild of the kbd package could also introduce the problem on amd64.

  [Test case]
  1. On ppc64el, run 'sudo loadkeys /etc/console-setup/cached.kmap.gz'
  2. Confirm that you are shown an error, "Couldn't get a file descriptor 
referring to the console".
  3. Install the kbd package from xenial-proposed.
  4. Run 'sudo loadkeys /etc/console-setup/cached.kmap.gz' again.
  5. Confirm that no error message is shown and the command exits with staus 0.
  6. Repeat steps 3-6 on amd64.

  [Regression potential]
  Since keymap settings are currently not being applied on ppc64el, it's 
possible that someone who has configured a non-default keymap on a ppc64el 
system will be surprised after upgrade that their keymap has changed.

  
  == Comment: #1 - Application Cdeadmin <> - 2016-08-23 15:05:14 ==
  ==== State: Open by: knodelk on 23 August 2016 14:00:43 ====

  Seeing the following error message in the Ubuntu dmesg log following
  IPL to Ubuntu on system with Ubuntu 16.04.1 installed:

  # dmesg -T --level=alert,crit,err
  [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap.

  This appears to be something that can be ignored so manufacturing will
  be ignoring this message until directed otherwise.

  ==> all systemd related messages:
  # dmesg -T | grep systemd
  [Tue Aug 23 09:20:12 2016] systemd[1]: systemd 229 running in system mode. 
(+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
  [Tue Aug 23 09:20:12 2016] systemd[1]: Detected architecture ppc64-le.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Set hostname to <rcx2d406>.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Device-mapper event 
daemon FIFOs.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Forward Password Requests to 
Wall Directory Watch.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on /dev/initctl 
Compatibility Named Pipe.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Encrypted Volumes.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Syslog Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket (/dev/log).
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target User and Group Name 
Lookups.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on fsck to fsckd 
communication Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Control Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 metadata daemon 
socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 poll daemon socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice User and Session Slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Kernel Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice System Slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting POSIX Message Queue File 
System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Slices.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create list of required 
static device nodes for the current kernel...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Nameserver information 
manager...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Monitoring of LVM2 mirrors, 
snapshots etc. using dmeventd or progress polling...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting RPC Pipe File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice 
system-serial\x2dgetty.slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Read required files in advance.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Load Kernel Modules...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Debug File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Audit Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Journal Service...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Huge Pages File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Set up automount Arbitrary Executable 
File Formats File System Automount Point.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Uncomplicated firewall...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Set console keymap...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Debug File System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted POSIX Message Queue File 
System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Huge Pages File System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Create list of required static 
device nodes for the current kernel.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Nameserver information manager.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Uncomplicated firewall.
  [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Main process 
exited, code=exited, status=1/FAILURE
  [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap.
  [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Unit entered 
failed state.
  [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Failed with 
result 'exit-code'.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted RPC Pipe File System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Load Kernel Modules.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Configuration File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Apply Kernel Variables...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting FUSE Control File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started LVM2 metadata daemon.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create Static Device Nodes in 
/dev...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted FUSE Control File System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Configuration File System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Apply Kernel Variables.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Create Static Device Nodes in 
/dev.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting udev Kernel Device Manager...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Journal Service.
  [Tue Aug 23 09:20:12 2016] systemd-journald[7090]: Received request to flush 
runtime journal from PID 1

  ===> OS LEVEL
         ver 1.5.4.3 - OS, HTX, Firmware and Machine details

                             OS: GNU/Linux
                     OS Version: Ubuntu 16.04.1 LTS \n \l
                 Kernel Version: 4.4.0-31-generic

  ===> attaching the full dmesg output
  = Comment: #2 - Application Cdeadmin <> - 2016-08-23 15:05:17 ==

  == Comment: #5 - Application Cdeadmin <> - 2016-08-25 12:15:34 ==
  ==== State: MoreInfo by: knodelk on 25 August 2016 11:10:22 ====

  Here is the requested command output:

  # systemctl status -l console-setup.service
  * console-setup.service - Set console font and keymap
     Loaded: loaded (/lib/systemd/system/console-setup.service; static; vendor 
pre

     Active: active (exited) since Thu 2016-08-25 10:51:24 CDT; 5h 12min ago
       Docs: man:loadkeys(1)
    Process: 8017 ExecStart=/bin/setupcon --save (code=exited, status=0/SUCCESS)
   Main PID: 8017 (code=exited, status=0/SUCCESS)
      Tasks: 0
     Memory: 0B
        CPU: 0
     CGroup: /system.slice/console-setup.service

  Aug 25 10:51:23 rcx2e517 systemd[1]: Starting Set console font and keymap...
  Aug 25 10:51:24 rcx2e517 systemd[1]: Started Set console font and keymap.
  lines 1-13/13 (END)

  and /var/log/kern.log is attached
  ==== State: MoreInfo by: byrneadw on 05 September 2016 16:47:10 ====

  We collected the data again. kern.log doesn't have any logs that
  related to the dmesg error

  The error can be recreated by doing a cold boot, it won't recreate
  with a reboot.

  == Comment: #13 - Application Cdeadmin <> - 2016-09-08 09:05:40 ==
  ==== State: Open by: byrneadw on 08 September 2016 07:56:07 ====

  This is the default keyboard layout.

  root@rcx2d407:~# cat /etc/default/keyboard
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="us"
  XKBVARIANT=""
  XKBOPTIONS=""

  BACKSPACE="guess"
  root@rcx2d407:~#

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to