"Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources

Bug #1968109 reported by Samuel Santaella
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
software-properties (Ubuntu)
Triaged
High
Unassigned

Bug Description

I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009 MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of the box.

What I expect to happen is something I can do successfully in Ubuntu Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that version. In KDE Settings I click on "Driver Manager", which automatically opens Software Sources (that's the only way I know how to get there). It finds and shows my [proprietary Broadcom] Wi-Fi driver; I click on it, then the "Apply Changes" button is enabled after a second or two. I click that, wait about half a minute with a progress bar in action below, and then the Wi-Fi options appear the notification area, allowing me to connect.

I attached a screen record of what actually happens in Ubuntu Studio 22.04 beta (thankfully this distro comes with screen recording software out of the box). When I click on "Driver Manager", a "xterm" window (version 372-1ubuntu1 I think?) opens unexpectedly with some code showing up in it (the code is in the screen record), shortly before Software Sources (version 0.99.20) opens as expected. The same driver still appears on the list. When I click on the driver, it seems to still take that second or two to transition, with some more code appearing in "xterm", but the "Apply Changes" button never enables itself. It remains disabled so I can't click it. The "revert" button directly next to it is also disabled. Thus, I can't connect my computer to Wi-Fi in 22.04 beta.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-qt 0.99.20
ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
Uname: Linux 5.15.0-22-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: KDE
Date: Fri Mar 18 17:00:53 2022
LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Samuel Santaella (samuelitooooo) wrote :
Revision history for this message
Samuel Santaella (samuelitooooo) wrote :

Forgot to add: the date in the screen record file is not correct because this laptop doesn't have a battery (that's on me; I'm working on that). I don't remember exactly when I took the screen record itself, but the recorded "last modified" time is April 2, 2022 at 7:33 PM. I transferred it to my smartphone offline (via cable) before transferring it to another computer (again via cable; it was the easy option for me) to send this bug report. This is the Ubuntu Studio 22.04 "beta" ISO, not a daily release.

In Ubuntu Studio 21.10, I can get the correct time after I connect to the Internet, *because* I can do so.

Revision history for this message
brianzad1998tptagth (brianzad1998tptagth) wrote (last edit ):

Me, too. GUI tool not working. Apply changes button greyed out. Jammy, 22.04. LXQt Desktop.

Resolution is to install via command line.
Find your hardware with proprietary drivers, "sudo ubuntu-drivers list".
In my case, bcmwl-kernel-source.
Install with, sudo apt install bcmwl-kernel-source

Revision history for this message
Julian Andres Klode (juliank) wrote (last edit ):

Qt frontend broken, seems to access self.cache[module_packages] where module_packages is not a string or pair of strings, causing a TypeError. Don't know if anyone actively maintains that.

Changed in software-properties (Ubuntu):
importance: Undecided → High
status: New → Triaged
tags: added: foundations-triage-discuss
Revision history for this message
Julian Andres Klode (juliank) wrote :

I encourage flavours using Qt to fix this if they care about it.

tags: removed: foundations-triage-discuss
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.