| 2022-10-05 03:01:25 |
Mike Adams |
bug |
|
|
added bug |
| 2022-10-06 10:21:45 |
Launchpad Janitor |
dkms (Ubuntu): status |
New |
Confirmed |
|
| 2022-10-06 17:12:13 |
Eric Carvalho |
bug |
|
|
added subscriber Eric Carvalho |
| 2022-10-15 08:37:38 |
Bruno Redondi |
attachment added |
|
dkms.diff https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+attachment/5624265/+files/dkms.diff |
|
| 2022-10-15 12:27:00 |
Ubuntu Foundations Team Bug Bot |
tags |
kinetic |
kinetic patch |
|
| 2022-10-15 12:27:10 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2022-10-17 20:37:13 |
Vipul |
bug |
|
|
added subscriber Vipul |
| 2022-10-20 11:01:23 |
Chris Guiver |
bug |
|
|
added subscriber Chris Guiver |
| 2022-10-20 11:10:45 |
Ubuntu QA Website |
tags |
kinetic patch |
iso-testing kinetic patch |
|
| 2022-10-20 15:52:06 |
Brian Murray |
bug task added |
|
ubuntu-release-notes |
|
| 2022-10-20 15:54:28 |
Joe Barnett |
bug |
|
|
added subscriber Joe Barnett |
| 2022-10-20 16:50:20 |
Brian Murray |
dkms (Ubuntu): importance |
Undecided |
High |
|
| 2022-10-20 16:50:25 |
Brian Murray |
dkms (Ubuntu): status |
Confirmed |
Triaged |
|
| 2022-10-21 05:50:47 |
Guillaume Michaud |
bug |
|
|
added subscriber Guillaume Michaud |
| 2022-10-21 08:04:42 |
Marian Rainer-Harbach |
bug |
|
|
added subscriber Marian Rainer-Harbach |
| 2022-10-21 09:27:35 |
Billy Kwong |
bug |
|
|
added subscriber Billy Kwong |
| 2022-10-21 11:14:37 |
Dimitri John Ledkov |
dkms (Ubuntu): status |
Triaged |
Fix Committed |
|
| 2022-10-21 11:15:20 |
Dimitri John Ledkov |
description |
Expected on kinetic: dkms will sign built modules with MOK key if requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 |
Expected on kinetic: dkms will sign built modules with MOK key if requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7: https://github.com/dell/dkms/pull/242
---
dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue |
|
| 2022-10-23 03:37:49 |
John Ryan |
bug |
|
|
added subscriber John Ryan |
| 2022-10-25 16:00:27 |
Brian Murray |
ubuntu-release-notes: status |
New |
Fix Released |
|
| 2022-10-27 10:19:58 |
Gianfranco Costamagna |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-10-31 13:28:35 |
Aaron Rainbolt |
description |
Expected on kinetic: dkms will sign built modules with MOK key if requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7: https://github.com/dell/dkms/pull/242
---
dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue |
[Impact]
With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules.
This fix for this is in the -proposed pocket at the moment, and has been tested to work.
[Test plan]
1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.)
2. Install Ubuntu on the system, but do not enable the installation of third-party drivers.
3. When installation finishes, reboot.
4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system.
5. Enable -proposed.
6. Update *just* the DKMS package with "sudo apt install dkms".
7. Disable -proposed.
8. Reboot.
9. Run "sudo apt install bcmwl-kernel-source". The WiFi module should immediately begin working properly.
[Where problems could occur]
Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease.
---
Original bug reports:
Expected on kinetic: dkms will sign built modules with MOK key if requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7: https://github.com/dell/dkms/pull/242
---
dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue |
|
| 2022-11-01 11:19:23 |
Launchpad Janitor |
dkms (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2022-11-01 14:52:36 |
Łukasz Zemczak |
dkms (Ubuntu Kinetic): status |
New |
Fix Committed |
|
| 2022-11-01 14:52:39 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2022-11-01 14:52:45 |
Łukasz Zemczak |
tags |
iso-testing kinetic patch |
iso-testing kinetic patch verification-needed verification-needed-kinetic |
|
| 2022-11-01 17:06:35 |
Aaron Rainbolt |
description |
[Impact]
With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules.
This fix for this is in the -proposed pocket at the moment, and has been tested to work.
[Test plan]
1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.)
2. Install Ubuntu on the system, but do not enable the installation of third-party drivers.
3. When installation finishes, reboot.
4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system.
5. Enable -proposed.
6. Update *just* the DKMS package with "sudo apt install dkms".
7. Disable -proposed.
8. Reboot.
9. Run "sudo apt install bcmwl-kernel-source". The WiFi module should immediately begin working properly.
[Where problems could occur]
Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease.
---
Original bug reports:
Expected on kinetic: dkms will sign built modules with MOK key if requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7: https://github.com/dell/dkms/pull/242
---
dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue |
[Impact]
With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules.
This fix for this is in the -proposed pocket at the moment, and has been tested to work.
[Test plan]
1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.)
2. Install Ubuntu on the system, but do not enable the installation of third-party drivers.
3. When installation finishes, reboot.
4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system.
5. Enable -proposed.
6. Update *just* the DKMS package with "sudo apt install dkms".
7. Disable -proposed.
8. Run "sudo apt install bcmwl-kernel-source". The WiFi module should immediately begin working properly.
9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should begin working once Ubuntu boots.
[Where problems could occur]
Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease.
---
Original bug reports:
Expected on kinetic: dkms will sign built modules with MOK key if requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7: https://github.com/dell/dkms/pull/242
---
dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue |
|
| 2022-11-01 17:28:49 |
Aaron Rainbolt |
description |
[Impact]
With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules.
This fix for this is in the -proposed pocket at the moment, and has been tested to work.
[Test plan]
1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.)
2. Install Ubuntu on the system, but do not enable the installation of third-party drivers.
3. When installation finishes, reboot.
4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system.
5. Enable -proposed.
6. Update *just* the DKMS package with "sudo apt install dkms".
7. Disable -proposed.
8. Run "sudo apt install bcmwl-kernel-source". The WiFi module should immediately begin working properly.
9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should begin working once Ubuntu boots.
[Where problems could occur]
Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease.
---
Original bug reports:
Expected on kinetic: dkms will sign built modules with MOK key if requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7: https://github.com/dell/dkms/pull/242
---
dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue |
[Impact]
With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules.
This fix for this is in the -proposed pocket at the moment, and has been tested to work.
[Test plan]
1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.)
2. Install Ubuntu on the system, but do not enable the installation of third-party drivers.
3. When installation finishes, reboot.
4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system.
5. Enable -proposed.
6. Update *just* the DKMS package with "sudo apt install dkms".
7. Disable -proposed.
8. Run "sudo apt install bcmwl-kernel-source".
9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should begin working once Ubuntu boots.
[Where problems could occur]
Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease.
---
Original bug reports:
Expected on kinetic: dkms will sign built modules with MOK key if requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7: https://github.com/dell/dkms/pull/242
---
dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue |
|
| 2022-11-01 17:37:30 |
Aaron Rainbolt |
tags |
iso-testing kinetic patch verification-needed verification-needed-kinetic |
iso-testing kinetic patch verification-done verification-done-kinetic |
|
| 2022-11-02 14:45:56 |
Launchpad Janitor |
dkms (Ubuntu Kinetic): status |
Fix Committed |
Fix Released |
|
| 2022-11-02 14:46:01 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-10-25 10:06:04 |
Billy Kwong |
removed subscriber Billy Kwong |
|
|
|
