It appears that keyboard-setup.service works reliably in both xenial and
eoan. So closing this bug task now.
** Changed in: console-setup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Also affects: console-setup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: console-setup (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
This got rolled out long ago:
http://autopkgtest.ubuntu.com/packages/s/systemd/xenial/ppc64el
** Changed in: autopkgtest (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
keyboard-setup.service fails with
loadkeys[723]: Couldn't get a file descriptor referring to the console
which also happens with running "sudo loadkeys /etc/console-
setup/cached.kmap.gz" manually. So /dev/tty0 exists which signifies the
presence of ttys, but using them is broken. I added a wor
I did a manual run and reproduced the error. It also happens on a
current (July 21) xenial cloud image, not just on the rather outdated
adt image from April 20.
autopkgtest.service failing is a consequence of
https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=eff773b
-- i. e.
The most recent apparmor test
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/ppc64el/s/systemd/20160729_104947@/log.gz)
ran against the same -31.50 kernel that the same test on the same base
cloud image still succeeded. It's als
FAIL: test_no_failed (__main__.ServicesTest)
No failed units
--
Traceback (most recent call last):
File
"/tmp/autopkgtest.qQr62c/build.1BH/systemd-229/debian/tests/boot-and-services",
line 54, in test_no_failed
self.assertE
