All updates must go through the Fedora QA (Quality assurance system). So, this update is now in “testing”. It needs users to test and confirm the fix—by providing positive or negative karma. When it receives the required karma, it will automatically be pushed to “stable” for all users to use.
I’ll have to wait for the official update to have broadcom WiFi (BCM43142 on a HP-Notebook) working again. Hope the official update will come soon.
Doing all mentioned above failed.
Last metadata expiration check: 0:00:35 ago on Sat 11 May 2019 12:26:10 PM CEST.
No match for argument: wpa_supplicant-2.8
Error: Unable to find a match
Gives a real long list of conflicting packages. Tried to remove the old version first, but dnf wanted te remove a whole list of Python packages as so called “unused dependencies”, which they are not. So I’ll have to wait and I hope the official update will come really soon.
I like to share my experience with Fedora 30 and Broadcom drivers. I am using an Acer 5742 with a Broadcom chipset. With Fedora 29 and the ‘wl’ driver my wi-fi was unstable. Waking from sleep it would refuse to connect, I was forced to reboot. On a reboot, sometimes I had to reboot a second time before it would connect.
When Fedora 30 Beta became available, I decided to try it, and performed a clean install. All went well. Wi-Fi was stable, so I decided to see how long this would last before I would have to install the Broadcom drivers. (I had noticed that with Fedora 29, Wi-Fi was stable during the installation, and during normal use after, I had connections issues, which forced me to install the Broadcom driver from RPMFusion). However with Fedora 30 beta and subsequently with the official release of Fedora 30, I am still enjoying a rock solid Wi-Fi experience, without the Broadcom driver.
That has been my experience with Fedora 30 and Broadcom.
Hi all. I noticed the same problem with my MacBook Air laptop. Initially, after upgrading to FC30 my laptop wifi worked fine. A few days ago I did an update via the gui and it stopped working. Wifi turns on automatically and “sees” the available networks but it can not connect to any of them.
I read the entire thread on bugzilla.redhat.com and according to them the bug still persists.
I connected my laptop via ethernet (I have the lightning-to-ethernet adapter) and I noticed there was an update to wpa_supplicant to wpa_supplicant-2.8.2 so I figured it had been fixed in the meantime. So I did a ‘sudo dnf upgrade’ via ethernet and the problem STILL persists.
None of the workarounds listed on this page worked for me so… I wait.
Yes, I’ve tried everything above too, and it still is an official bug. A good one; all possible workarounds solve someone’s problem, but none of them work for everybody! https://bugzilla.redhat.com/show_bug.cgi?id=1703745
I ended up fixing it with the Koji build, unfortunately I ran an update and wpa_supplicant updated to the new version in the repo (2.8-2), and I’m back to where I started…
You can temporarily exclude the package from updates using the exclude=.. directive in the dnf config file (or the related repository file). More information in man dnf.conf on that. The repository files are stored in /etc/yum.repos.d/, while the dnf config file is /etc/dnf/dnf.conf. (Do rembember to undo this in the future when the correct package update has hit the repositories.)