Wireless network immediately disconnects after updating to 19.04

Bug #1822565 reported by arturo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

When trying to connect through wifi it keeps disconnecting and trying to connect again. The output from dmesg shows repeatedly:

[ 237.763532] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b4 (capab=0x411 status=0 aid=3)
[ 237.770669] wlp3s0: associated
[ 237.949148] wlp3s0: deauthenticating from 78:81:02:8f:b7:b4 by local choice (Reason: 1=UNSPECIFIED)
[ 238.080024] wlp3s0: authenticate with 78:81:02:8f:b7:b6
[ 238.084439] wlp3s0: send auth to 78:81:02:8f:b7:b6 (try 1/3)
[ 238.089443] wlp3s0: authenticated
[ 238.092096] wlp3s0: associate with 78:81:02:8f:b7:b6 (try 1/3)
[ 238.093446] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b6 (capab=0x11 status=0 aid=1)
[ 238.095034] wlp3s0: associated
[ 238.120780] wlp3s0: deauthenticating from 78:81:02:8f:b7:b6 by local choice (Reason: 1=UNSPECIFIED)
[ 238.271261] wlp3s0: authenticate with 78:81:02:8f:b7:b4
[ 238.274585] wlp3s0: send auth to 78:81:02:8f:b7:b4 (try 1/3)
[ 238.280295] wlp3s0: authenticated
[ 238.284119] wlp3s0: associate with 78:81:02:8f:b7:b4 (try 1/3)
[ 238.288600] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b4 (capab=0x411 status=0 aid=3)
[ 238.290668] wlp3s0: associated
[ 238.472343] wlp3s0: deauthenticating from 78:81:02:8f:b7:b4 by local choice (Reason: 1=UNSPECIFIED)
[ 238.612923] wlp3s0: authenticate with 78:81:02:8f:b7:b6
[ 238.615663] wlp3s0: send auth to 78:81:02:8f:b7:b6 (try 1/3)
[ 238.617052] wlp3s0: authenticated
[ 238.620101] wlp3s0: associate with 78:81:02:8f:b7:b6 (try 1/3)
[ 238.621631] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b6 (capab=0x11 status=0 aid=1)
[ 238.623148] wlp3s0: associated
[ 238.649560] wlp3s0: deauthenticating from 78:81:02:8f:b7:b6 by local choice (Reason: 1=UNSPECIFIED)

Looking for similar errors some posts suggest to disable the wpa_supplicant service as it might be clashing with NetworkManager starting it on it's own but disabling it doesn't seem to have any effect.

This seems to happen only when connecting to a particular router, a vodafone EasyBox (which worked fine before updating to ubuntu 19.04) connecting to some other router seems to not have this problem

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: network-manager 1.15.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 1 11:30:05 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-12-10 (111 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
IpRoute:
 default via 192.168.42.129 dev enp0s20u9 proto dhcp metric 100
 169.254.0.0/16 dev enp0s20u9 scope link metric 1000
 192.168.42.0/24 dev enp0s20u9 proto kernel scope link src 192.168.42.112 metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to disco on 2019-03-31 (0 days ago)
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.15.2 connected started full enabled enabled enabled enabled enabled

Revision history for this message
arturo (arturo-openframeworks) wrote :
Revision history for this message
arturo (arturo-openframeworks) wrote :

This seems to be fixed with latest update

Revision history for this message
Sebastien Bacher (seb128) wrote :

Great, thanks for the status update. Closing but feel free to reopen if you get the issue again

Changed in network-manager (Ubuntu):
importance: Undecided → Low
status: New → Fix Released
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.