MASTER [karmic] network-manager, GetSecrets dbus method call is broken - secure wireless networks don't work

[Roland Dreier]

Binary package hint: network-manager

After recent updates, my Karmic laptop won't connect to my home wifi, which is secured with WPA2 personal/PSK. The problem seems to be that I marked the network as "Available to all users" in the connection editor (so that the network comes up before I log in, so I can log in from another box to debug gdm, etc). In syslog, I see:

Sep 25 13:47:56 roland-x200 NetworkManager: <info> Activation (wlan0/wireless): access point 'Auto mynet' has security, but secrets are required.

and if I go to the connection editor and try to edit the connection, I get a dialog that says

  Error initializing editor

  Method "GetSecrets" with signature "sasb" on interface "org.freedesktop.NetworkManagerSettings.Connection" doesn't exist

I have another WPA2 enterprise network I use for the office, which I didn't mark as "Available to all users" that works, and if I try to edit it, it works fine (I get a keyring authorization dialog, and then the edit dialog).

So it seems something is wrong with shared secure connections.

ProblemType: Bug
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Fri Sep 25 13:48:30 2009
DistroRelease: Ubuntu 9.10
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.103 metric 2
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 192.168.1.1 dev wlan0 proto static
Package: network-manager 0.8~a~git.20090923t064445.b20cef2-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
SourcePackage: network-manager
Uname: Linux 2.6.31-10-generic x86_64

[Antonio Censi (accensi)]

I can confirm on a similar configuration, but only after a third or mode cycle of suspend/resume.

HP tx2-1020us notebook tablet

~$ uname -a
Linux RJASTEC-06374 2.6.31-11-generic #36-Ubuntu SMP Fri Sep 25 06:37:23 UTC 2009 x86_64 GNU/Linux

Wireless:
08:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)

Driver:
~$ modinfo wl
filename: /lib/modules/2.6.31-11-generic/updates/dkms/wl.ko
license: MIXED/Proprietary
srcversion: 0FB12E281D3D940CBD407D0

gnome-keyring version
2.28.0-0ubuntu1

syslog messages enter a loop of messages like this:
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1/wireless): access point 'ACC Home' has security, but secrets are required.
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1/wireless): access point 'ACC Home' has security, but secrets are required.
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> (eth1): device state change: 5 -> 9 (reason 7)
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) failed for access point (ACC-RC156)
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Marking connection 'ACC Home' invalid.
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) failed.
Sep 22 01:32:14 RJASTEC-06374 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Sep 22 01:32:...

[Antonio Censi (accensi)]

Complementing previous information, a power glitch that affected the AP router caused the same kind of behaviour by just disconnecting the link and reconnecting again:

from /var/log/daemon.log
Sep 27 17:26:49 RJASTEC-06374 wpa_supplicant[836]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Sep 27 17:26:49 RJASTEC-06374 NetworkManager: <info> (eth1): supplicant connection state: completed -> disconnected
Sep 27 17:26:50 RJASTEC-06374 NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning

Same information in syslog.

To return I had to remove wl module and modprobed it.

NetworkManager had a segfault after the remove/insert of wl module, but the operation recorered:

[24651.585609] NetworkManager[766]: segfault at 50 ip 00007f7fef0e9ec0 sp 00007fff561a5c38 error 4 in libnl.so.1.1[7f7fef0c6000+4c000]

Hope this information is of some help to diagnose the bug.

[Roland Dreier (roland.dreier)]

Yes, in my case it does seem related to suspend/resume too... I first saw the problem after suspending at work and coming home; when I resumed my system could not connect to my home network. A restart of the system does seem to make things work again.

By the way, this is definitely a regression from earlier in the Karmic cycle -- until recently wireless was working pretty perfectly for me.

[Alexander Sack (asac)]

are you sure you have the most recent version for network-manager-gnome too?

[Martin (agima)]

The problem ist still present in 0.8~a~git.20090923t064445.b20cef2-0ubuntu1

[Roland Dreier (roland.dreier)]

Yes, with a freshly booted completely update system (0.8~a~git.20090923t220421.1ac8ffd-0ubuntu4), I see the 'Method "GetSecrets" with signature "sasb" on interface "org.freedesktop.NetworkManagerSettings.Connection" doesn't exist' dialog when trying to edit my shared connection.

[Alexander Sack (asac)]

could you try this patch against network manager?

--- a/libnm-glib/nm-remote-connection.c
+++ b/libnm-glib/nm-remote-connection.c
@@ -186,7 +186,7 @@ get_secrets (NMSettingsConnectionInterface *connection,
        call->user_data = user_data;
        call->proxy = priv->secrets_proxy;

- call->call = org_freedesktop_NetworkManagerSettings_Connection_Secrets_get_secrets_async (priv->proxy,
+ call->call = org_freedesktop_NetworkManagerSettings_Connection_Secrets_get_secrets_async (priv->secrets_proxy,
                                                                                                  setting_name,
                                                                                                  hints,
                                                                                                  request_new,

[Alexander Sack (asac)]

secrets being broken is kind of beta blocker. checking if the simple patch is enough so we can get that in still.

[Alexander Sack (asac)]

managed to reproduce, committed the fix and checked that wireless system connections as well as modifying secrets still work. uploading

zr commit -m '* fix LP: #436884 - wireless secrets dont work in karmic; we
  cherry-pick a one-line git commit that makes the GetSecrets
  call use the right dbus proxy.
  - add debian/patches/lp436884.patch
  - update debian/patches/series' --fixes 'lp:436884'
Committing to: bzr+ssh://bazaar.launchpad.net/~network-manager/network-manager/ubuntu.head/
modified debian/changelog
added debian/patches/lp436884.patch
modified debian/patches/series
Committed revision 133.

[Alexander Sack (asac)]

Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading network-manager_0.8~a~git.20090923t064445.b20cef2-0ubuntu2.dsc: done.
  Uploading network-manager_0.8~a~git.20090923t064445.b20cef2-0ubuntu2.diff.gz: done.
  Uploading network-manager_0.8~a~git.20090923t064445.b20cef2-0ubuntu2_source.changes: done.
Successfully uploaded packages.

[Launchpad Janitor (janitor)]

This bug was fixed in the package network-manager - 0.8~a~git.20090923t064445.b20cef2-0ubuntu2

---------------
network-manager (0.8~a~git.20090923t064445.b20cef2-0ubuntu2) karmic; urgency=low

  * fix LP: #436884 - wireless secrets dont work in karmic; we
    cherry-pick a one-line git commit that makes the GetSecrets
    call use the right dbus proxy.
    - add debian/patches/lp436884.patch
    - update debian/patches/series

 -- Alexander Sack <email address hidden> Tue, 29 Sep 2009 17:11:56 +0200