network-manager doesn't show info about connected network xenial regression

Bug #1574268 reported by Jaime Pérez
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have suspended system and then restored. I logged in and network manager says that I'm connected, but it doesn't say at which network. I have connection to the Internet, but nm doesn't show info.

In dmesg

[ 6208.740068] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[ 6224.190017] wlp3s0: deauthenticating from 30:b5:c2:26:7e:0e by local choice (Reason: 3=DEAUTH_LEAVING)
[ 6224.251418] cfg80211: World regulatory domain updated:
[ 6224.251423] cfg80211: DFS Master region: unset
[ 6224.251424] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 6224.251427] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 6224.251429] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 6224.251431] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 6224.251433] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 6224.251436] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 6224.251438] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 6224.251439] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 6224.251441] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 6232.648624] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 6232.684722] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 6233.698777] wlp3s0: authenticate with 30:b5:c2:26:7e:0e
[ 6233.712867] wlp3s0: send auth to 30:b5:c2:26:7e:0e (try 1/3)
[ 6233.717549] wlp3s0: authenticated
[ 6233.721067] wlp3s0: associate with 30:b5:c2:26:7e:0e (try 1/3)
[ 6233.727328] wlp3s0: RX AssocResp from 30:b5:c2:26:7e:0e (capab=0x431 status=0 aid=2)
[ 6233.727401] wlp3s0: associated

This didn't happened in trusty

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
Uname: Linux 4.4.8-040408-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sun Apr 24 16:03:35 2016
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-04-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.1.1 dev wlp3s0 proto static metric 600
 169.254.0.0/16 dev wlp3s0 scope link metric 1000
 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.137 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 Jazztel_885461 18a3b86a-fc9d-46e3-a447-24e75ce60db4 /org/freedesktop/NetworkManager/ActiveConnection/7
 enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- --
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
Jaime Pérez (jaime-91) wrote :
tags: added: regression-release
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.