The fix here breaks installing custom kernels, at least on xenial (dkms
(2.2.0.3-2ubuntu11.7) xenial): the redirection of stdout was to there to
fix a problem with dkms output contaminating debconf's input - see
#292606 for details. To be specific, during package install (either via
dpkg or
This bug was fixed in the package dkms - 2.6.1-4ubuntu2.1
---
dkms (2.6.1-4ubuntu2.1) disco; urgency=medium
* Do not invoke dkms_autoinstaller from /etc/kernel/header_postinst.d/dkms
with redirection to /dev/null (LP: #1827697), this caused debconf dialog
to not be shown.
This bug was fixed in the package dkms - 2.3-3ubuntu11.1
---
dkms (2.3-3ubuntu11.1) cosmic; urgency=medium
* Do not invoke dkms_autoinstaller from /etc/kernel/header_postinst.d/dkms
with redirection to /dev/null (LP: #1827697), this caused debconf dialog
to not be shown.
This bug was fixed in the package dkms - 2.3-3ubuntu9.3
---
dkms (2.3-3ubuntu9.3) bionic; urgency=medium
* Do not invoke dkms_autoinstaller from /etc/kernel/header_postinst.d/dkms
with redirection to /dev/null (LP: #1827697), this caused debconf dialog
to not be shown.
--
This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.7
---
dkms (2.2.0.3-2ubuntu11.7) xenial; urgency=medium
* Do not invoke dkms_autoinstaller from /etc/kernel/header_postinst.d/dkms
with redirection to /dev/null (LP: #1827697), this caused debconf dialog
to not be
@juliank
The reproduced dkms version on bionic is 2.3-3ubuntu9.2, while the verified
version is 2.3-3ubuntu9.3.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1827697
Title:
Enroll key
xenial:
> Regression in autopkgtest for dahdi-linux (s390x): test log
> Regression in autopkgtest for iscsitarget (armhf): test log
I looked at those and they seem to be failing a lot for other uploads
too, so do not seem to be regressions.
--
You received this bug notification because you are
@buo-ren-lin thanks!
xenial: I verified that ubuntu11.6 was broken, and ubuntu11.7 is fine in
the same way as the others.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you
cosmic: Installed kernel header, got the hang; Updated dkms to
-ubuntu11.1 from -ubuntu11; installed different kernel header, got
prompt. Verifed.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member
disco: I reproduced the bug by installing linux headers -17-generic
which hang and then upgrading dkms to 2.6.1-4ubuntu2.1 and installing
linux-headers -16-generic (purging and reinstalling the 17 headers did
nothing it seems, so, don't care ..) which had a working prompt.
To "revoke" the key,
You have not stated the versions tested in bionic, hence the
verification is not valid. Can you check that and state which versions
you tested?
One test run needs about 30 mins to an hour (install ubuntu in a VM,
then try to reproduce), so if I can avoid one, that'd be great :)
** Tags removed:
** Description changed:
I noticed that sometimes the system upgrade is blocked in the kernel
header package's configure phase, in the process manager I found that it
is blocked by the "Configuring Secure Boot" whiptail prompt started by
`update-secureboot-policy --enroll-key` which
@juliank
To trigger the bug:
1. Install any out-of-tree dkms packages (like bbswitch-dkms)
2. Un-enroll keys from MOK, ensure `mokutil --test-key
/var/lib/shim-signed/mok/MOK.der` command returns
"/var/lib/shim-signed/mok/MOK.der is not enrolled"
3. Ensure SecureBoot is enabled
4. Install any
I have applied the updates on bionic and can no longer reproduce it.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
The regressions in rdep autopkgtests are not caused by this upload, but
also present in other runs:
xenial:
Regression in autopkgtest for dahdi-linux (s390x)
Regression in autopkgtest for iscsitarget (armhf)
Still can't actually verify the bug, as I can't trigger it.
--
You received this bug
Hello ๆๅไป(Buo-ren, or anyone else affected,
Accepted dkms into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.6.1-4ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package dkms - 2.6.1-4ubuntu4
---
dkms (2.6.1-4ubuntu4) eoan; urgency=medium
* Do not invoke dkms_autoinstaller from /etc/kernel/header_postinst.d/dkms
with redirection to /dev/null (LP: #1827697), this caused debconf dialog
to not be shown.
--
Now it's fine, maybe changelog entry was broken and dpkg's error
handling was crazy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1827697
Title:
Enroll key whiptail prompt blocks
xenial I don't know what to do: It's all fine importing the patch into
the package, but as soon as I add the changelog entry to
debian/changelog, building fails with
dpkg-source: info: using patch list from debian/patches/series
patching file dkms_common.postinst
Hunk #1 FAILED at 146.
1 out of 1
** Tags added: id-5cce6e8af572b90e81d1e5cf
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1827697
Title:
Enroll key whiptail prompt blocks kernel header package upgrades
Status in dkms
ok based on the process tree I've identified the source of the trouble,
/etc/kernel/header_postinst.d/dkms invokes dkms_autoinstaller with
>/dev/null. So this is a similar symptom to other bugs that have been
fixed, but is a separate unfixed bug.
Note that a workaround for this problem is to run
21 matches
Mail list logo
