[Pkg-utopia-maintainers] Bug#762740: No network devices available

[Michal Hocko]

On Fri, Sep 26, 2014 at 02:52:02PM +0200, Michal Hocko wrote:
> On Wed, Sep 24, 2014 at 10:31:41PM +0200, Michal Hocko wrote:
> > Package: network-manager
> > Version: 0.9.4.0-10
> > Severity: serious
> > 
> > Hi,
> > it seems that network-manager stopped being able to handle my lan and
> > wlan devices properly after last series of updates (which don't seem to
> > be directly related to the nm packages). Although I can get connected to
> > both wired and wireless (to the system wide saved networks) nm-applet
> > (network-manager-gnome package) claims that there are "No network
> > devices available" so it doesn't give me access to neither of the
> > saved networks nor to the saved VPN configurations.
> > 
> > I originally wanted to report this agains network-manager-gnome package
> > but I think this comes from network-manager and the applet simply relays
> > to information.
> 
> Hmm, it seems this is applet related after all. I have installed kde nm
> widget and it seems to be working properly showing both lan and wlan
> setups.

Sorry to come back after such a long time but I didn't have much time to
look into this (auto connection to known system connection still works
so I could live with the current state but I cannot add new connections
so it is getting more and more annoying). The KDE applet turned out
being non functional as well.  Although it shows networks it cannot
neither attach to nor detach from them. So both applets merely show the
current connection state but cannot do anything about it.

$ nmcli nm
RUNNING         STATE           WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
running         connected       enabled         enabled    enabled         disabled

$ nmcli dev status
DEVICE     TYPE              STATE
$ nmcli dev list
$

$ nmcli con status
NAME                      UUID                                   DEVICES    DEFAULT  VPN   MASTER-PATH                                 
not set                   not set                                not set    not set  not set not set

This all while network-manager seems to be the one who connected me to a
system connection automatically:
Oct 11 15:32:58 tiehlicka NetworkManager[22665]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 11 15:32:58 tiehlicka NetworkManager[22665]: <info> Activation (wlan0/wireless): connection 'mameluci' has security, and secrets exist.  No new secrets needed.
Oct 11 15:32:58 tiehlicka NetworkManager[22665]: <info> Config: added 'ssid' value 'mameluci'
Oct 11 15:32:58 tiehlicka NetworkManager[22665]: <info> Config: added 'scan_ssid' value '1'
Oct 11 15:32:58 tiehlicka NetworkManager[22665]: <info> Config: added 'key_mgmt' value 'NONE'
Oct 11 15:32:58 tiehlicka NetworkManager[22665]: <info> Config: added 'wep_key0' value '<omitted>'
Oct 11 15:32:58 tiehlicka NetworkManager[22665]: <info> Config: added 'wep_tx_keyidx' value '0'
Oct 11 15:32:58 tiehlicka NetworkManager[22665]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 11 15:32:58 tiehlicka NetworkManager[22665]: <info> Config: set interface ap_scan to 1
Oct 11 15:33:01 tiehlicka wpa_supplicant[3571]: wlan0: SME: Trying to authenticate with c0:4a:00:f1:48:f2 (SSID='mameluci' freq=2412 MHz)
Oct 11 15:33:01 tiehlicka kernel: [67355.323176] wlan0: authenticate with c0:4a:00:f1:48:f2
Oct 11 15:33:01 tiehlicka kernel: [67355.325813] wlan0: send auth to c0:4a:00:f1:48:f2 (try 1/3)
Oct 11 15:33:01 tiehlicka wpa_supplicant[3571]: wlan0: Trying to associate with c0:4a:00:f1:48:f2 (SSID='mameluci' freq=2412 MHz)
Oct 11 15:33:01 tiehlicka NetworkManager[22665]: <info> (wlan0): supplicant interface state: inactive -> authenticating
Oct 11 15:33:01 tiehlicka kernel: [67355.328743] wlan0: authenticated
Oct 11 15:33:01 tiehlicka kernel: [67355.328956] iwlwifi 0000:02:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
Oct 11 15:33:01 tiehlicka kernel: [67355.331256] wlan0: associate with c0:4a:00:f1:48:f2 (try 1/3)
Oct 11 15:33:01 tiehlicka NetworkManager[22665]: <info> (wlan0): supplicant interface state: authenticating -> associating
Oct 11 15:33:01 tiehlicka kernel: [67355.334146] wlan0: RX AssocResp from c0:4a:00:f1:48:f2 (capab=0x431 status=0 aid=1)
Oct 11 15:33:01 tiehlicka wpa_supplicant[3571]: wlan0: Associated with c0:4a:00:f1:48:f2
Oct 11 15:33:01 tiehlicka wpa_supplicant[3571]: wlan0: CTRL-EVENT-CONNECTED - Connection to c0:4a:00:f1:48:f2 completed [id=0 id_str=]
Oct 11 15:33:01 tiehlicka kernel: [67355.341174] wlan0: associated
Oct 11 15:33:01 tiehlicka kernel: [67355.341215] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Oct 11 15:33:01 tiehlicka NetworkManager[22665]: <info> (wlan0): supplicant interface state: associating -> completed
Oct 11 15:33:01 tiehlicka NetworkManager[22665]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'mameluci'.

The log still claims there are not unmanaged devices:
Oct 11 15:32:54 tiehlicka NetworkManager[22665]:    Ifupdown: get unmanaged devices count: 0
Oct 11 15:32:54 tiehlicka NetworkManager[22665]:    SCPlugin-Ifupdown: (7663376) ... get_connections.
Oct 11 15:32:54 tiehlicka NetworkManager[22665]:    SCPlugin-Ifupdown: (7663376) ... get_connections (managed=false): return empty list.
[...]
Oct 11 15:32:54 tiehlicka NetworkManager[22665]:    Ifupdown: get unmanaged devices count: 0

Why the NM claims it doesn't manage any devices when in fact it
connects to them? Is it possible this is policykit or DBUS related
and the applets cannot talk to NM?
-- 
Michal Hocko