Proprietary Wi-Fi drivers fail to install if you go back and enable the downloading of updates during Ubuntu installation

Bug #1988101 reported by Aaron Rainbolt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Medium
Unassigned

Bug Description

Bug discovered doing RC ISO testing for Ubuntu 20.04.5.

Hardware is an HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, UEFI, no secure boot, **with a Broadcom Wi-Fi module**. You will probably need a system with a Broadcom Wi-Fi module (or possibly some other hardware with proprietary drivers like an NVidia card) in order to reproduce this issue.

Steps to reproduce:

1: Boot an Ubuntu Desktop ISO.
2: When offered to either try or install Ubuntu, click "Try Ubuntu".
3: Launch Ubiquity.
4: Proceed through the installer accepting the defaults until you get to the 'Updates and other software' screen.
5: Check the box to install proprietary drivers, and proceed to the next screen. Your Wi-Fi should start working.
6: Go back to the previous screen.
7: Connect to Wi-Fi.
8: Once connected, check the box to download updates while installing Ubuntu, then proceed to the next screen.
9: Finish the rest of the installation (using the "Erase Disk and install Ubuntu" option), then reboot when finished.

Expected result: The system's Wi-Fi should be fully functional when the newly installed OS boots.

Actual result: The system cannot see any Wi-Fi networks. Running "dpkg-query -s bcmwl-kernel-source" reveals that the Broadcom Wi-Fi drivers are not installed.

Notes:

If you skip steps 6-8 (don't go back to the previous screen to enable downloading updates during installation), the Wi-Fi will work in the newly installed system. For some reason the problem seems to trigger if you go back to enable downloading updates.

This problem occurs on Ubuntu Studio 20.04.5, as well as Ubuntu Desktop 20.04.5.

Logs will be attached later, this bug is so I can report the failure.

Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Thank you for the report! Can you check the behavior on the previous 20.04.4 images? Since I'm afraid that this might not be an actual regression.

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1988101

tags: added: iso-testing
Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

Bug also occurs on Ubuntu 20.04.4, so this is **not** a regression.

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

debug info

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

debug info

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

debug info

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

debug info

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

debug info

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

debug info

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

debug info

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

debug info

Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Brian Murray (brian-murray) wrote :

Given that we are currently working on the last point release of 20.04.5 we should set this to Won't Fix unless it can be confirmed in Kinetic or Ubuntu 22.04.1. @Aaron could you test this with either of those? Thanks again for all your testing!

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

This bug is reproducible using the latest Ubuntu Desktop Kinetic ISO at the time of this writing.

tags: added: kinetic
Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

Changed status to New as it was verified to be reproducible on a newer version of Ubuntu.

Changed in ubiquity (Ubuntu):
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.