[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#836139: networkmanager: Fails to connect to wifi networks



Control: tag -1 + upstream
Control: clone -1 -2
Control: retitle -1 network-manager: plasma-nm wrong icon with network-manager 1.4
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=367938
Control: reassign -2 network-manager 1.4.0-3
Control: retitle -2 network-manager: PropertiesChanged signal is emitted only from org.freedesktop.DBus.Properties interface for WirelessDevice
Control: forwarded -2 https://bugzilla.gnome.org/show_bug.cgi?id=770629
Control: tag -2 + patch
Control: block -1 by -2

¡Hola Kyle!

El 2016-08-30 a las 23:04 +0200, Kyle Robbertze escribió:
Package: libkf5networkmanagerqt6 Version: 5.25.0-1 Severity: important File: networkmanager

Updating nm breaks its ability to connect to Wifi networks.

I am using a broadcom chip with the firmware-sta-dkms package installed. It worked well until I updated to 5.25.0-1 when, although it saw the wifi networks around me, it cannot connect to them (log attached)

A work around is to disable mac address randomization as described in [1].

This is reported in https://bugs.debian.org/835822
I can't reproduce the issue with 1.4.0-3, the changelog doesn't mention any change related to this so it's probably that my card wasn't affected. Could you please send a follow up on that bug with your findings?

However while using this work around, the plasma widget in the system tray shows that the network is not connected (the icon is the blank wifi symbol with a question mark), however it is actually connected and working.

I do not know if the fix that has been committed upstream [2] solves this second issue or not.

This part is reported in kde:
https://bugs.kde.org/show_bug.cgi?id=367938
And I can confirm that restarting plasmashell fixes it.

It also mentions that the network-manager issue that causes this was reported here: https://bugzilla.gnome.org/show_bug.cgi?id=770629

So, it seems that
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=923eaa6a478f95a69d1b9ccac429c7ffea3e4af4
needs to be applied in network-manager, and that might be unrelated to the issue mentioned earlier.

I'm cloning this issue so the network-manager maintainers get notified about this.

Happy hacking,
--
"Programming today is a race between software engineers striving to build
bigger and better idiot-proof programs, and the Universe trying to produce
bigger and better idiots. So far, the Universe is winning."
-- Rich Cook
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature


Reply to: