No wireless networks after starting system

Bug #1573359 reported by Dawid Wróbel
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After booting the system, there are no networks reported in Network Manager applet. After restarting network-manager service, it picks up the pre-configigured network and connects straight away.

This has not been like this before and only started about 2 weeks ago.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 21 22:29:46 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-04-24 (1094 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
IpRoute:
 default via 192.168.1.1 dev wlp58s0 proto static metric 600
 169.254.0.0/16 dev wlp58s0 scope link metric 1000
 172.16.53.0/24 dev vmnet1 proto kernel scope link src 172.16.53.1
 172.16.138.0/24 dev vmnet8 proto kernel scope link src 172.16.138.1
 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.202 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to xenial on 2016-03-23 (29 days ago)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 you_gonna_make_me_pregnant 1 991de0b1-f4d3-4ead-9706-bea9979248f5 /org/freedesktop/NetworkManager/ActiveConnection/0
 vmnet1 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- --
 vmnet8 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/3 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

Revision history for this message
Dawid Wróbel (dawidw) wrote :
Revision history for this message
Dawid Wróbel (dawidw) wrote :

Fresh after booting, following is suspicious in syslog:

dell kernel: [ 9.232325] brcmf_add_if: ERROR: netdev:wlp58s0 already exists
dell kernel: [ 9.232347] brcmf_add_if: ignore IF event

and in dmesg:

[ 9.232325] brcmf_add_if: ERROR: netdev:wlp58s0 already exists
[ 9.232347] brcmf_add_if: ignore IF event
[ 9.236112] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[ 9.242258] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[ 9.246334] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready

After restarting nm service, dmesg says:

[ 168.481449] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[ 168.685438] userif-2: sent link down event.
[ 168.685442] userif-2: sent link up event.
[ 168.793376] brcmf_add_if: ERROR: netdev:wlp58s0 already exists
[ 168.793380] brcmf_add_if: ignore IF event
[ 168.828171] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[ 175.118508] IPv6: ADDRCONF(NETDEV_CHANGE): wlp58s0: link becomes ready

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
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.