[Pkg-utopia-maintainers] Bug#475672: network-manager: isn't playing nice with the gnome keyring

Sat May 3 10:11:16 UTC 2008

On Sat, Apr 12, 2008 at 11:50:21AM +0200, Michael Biebl wrote:
> Do other applications work correctly with gnome-keyring?

gnome-keyring prompts me to unlock my ssh private key, but I suppose
that's not the gnome keyring. gnome-keyring-manager works.

I wonder, I'm sure I've seen the option to always allow or always deny
an application access to the keyring, but I do not know where the
result of that is saved. I can't see it using keyring-manager nor
gconf-editor. Perhaps nm-applet is set to always deny?

> Could you try with a fresh keyring resp. fresh account?

A fresh user account worked fine.

> Is there anything suspicious in the NetworkManager log (run it as
> NetworkManager --no-daemon) or in the users .xsession-errors file?

nothing in xsession-errors and nothing suspicious in the output of
--no-daemon (attached with comments)
-------------- next part --------------
Script started on Sat 03 May 2008 10:03:35 BST
qusp:~# NetworkMn[Kanager --no-daemon
NetworkManager: <info>  starting...
NetworkManager: <info>  New VPN service 'vpnc' (org.freedesktop.NetworkManager.vpnc).
NetworkManager: <info>  New VPN service 'openvpn' (org.freedesktop.NetworkManager.openvpn).
NetworkManager: <info>  New VPN service 'ppp' (org.freedesktop.NetworkManager.ppp_starter).
NetworkManager: <info>  Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch
NetworkManager: <info>  eth1: Device is fully-supported using driver 'ipw2200'.
NetworkManager: <info>  eth1: driver does not support SSID scans (scan_capa 0x00).
NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start
NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info>  Now managing wireless (802.11) device 'eth1'.
NetworkManager: <info>  Deactivating device eth1.
NetworkManager: <info>  eth0: Device is fully-supported using driver 'e1000'.
NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start
NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info>  Now managing wired Ethernet (802.3) device 'eth0'.
NetworkManager: <info>  Deactivating device eth0.
NetworkManager: <info>  Wireless now enabled by radio killswitch
NetworkManager: <info>  Updating allowed wireless network lists.
NetworkManager: <info>  Updating VPN Connections...
NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth1'.
NetworkManager: <info>  Will activate connection 'eth1/traf.alcopop.org'.
NetworkManager: <info>  Device eth1 activation scheduled...
NetworkManager: <info>  Activation (eth1) started...
NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info>  Activation (eth1/wireless): access point 'traf.alcopop.org' is encrypted, but NO valid key exists.  New key needed.
NetworkManager: <info>  Activation (eth1) New wireless user key requested for network 'traf.alcopop.org'.

	this resulted in a keyring prompt which I dismissed. 

NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) complete.

	at this point, the nm icon span indefinitely, with both lights off.

	I re-selected my AP from the list to restart the process.

NetworkManager: <debug> [1209807340.446489] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'traf.alcopop.org'
NetworkManager: <info>  User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / traf.alcopop.org
NetworkManager: <info>  Deactivating device eth1.
NetworkManager: <info>  Activation (eth1): cancelling...
NetworkManager: <info>  Activation (eth1) cancellation handler scheduled...
NetworkManager: <info>  Activation (eth1): waiting for device to cancel activation.
NetworkManager: <info>  Activation (eth1) cancellation handled.
NetworkManager: <info>  Activation (eth1): cancelled.
NetworkManager: <info>  Device eth1 activation scheduled...
NetworkManager: <info>  Activation (eth1) started...
NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info>  Activation (eth1/wireless): access point 'traf.alcopop.org' is encrypted, but NO valid key exists.  New key needed.
NetworkManager: <info>  Activation (eth1) New wireless user key requested for network 'traf.alcopop.org'.

	here I was prompted for the keyring password, supplied it, was
	re prompted, dismissed the subsequent prompt, then I am prompted
	for the WPA passphrase directly. I supply it.

NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <info>  Activation (eth1) New wireless user key for network 'traf.alcopop.org' received.
NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info>  Activation (eth1/wireless): access point 'traf.alcopop.org' is encrypted, and a key exists.  No new key needed.
NetworkManager: <info>  SUP: sending command 'INTERFACE_ADD eth1		wext	/var/run/wpa_supplicant	'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'AP_SCAN 1'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'ADD_NETWORK'
NetworkManager: <info>  SUP: response was '0'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 ssid 747261662e616c636f706f702e6f7267'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 proto WPA'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 psk <key>'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'ENABLE_NETWORK 0'
CTRL-EVENT-SCAN-RESULTS 
Trying to associate with 00:90:d0:fc:dc:1b (SSID='traf.alcopop.org' freq=2412 MHz)
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Associated with 00:90:d0:fc:dc:1b
WPA: Key negotiation completed with 00:90:d0:fc:dc:1b [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:90:d0:fc:dc:1b completed (auth) [id=0 id_str=]
NetworkManager: <info>  Supplicant state changed: 1
NetworkManager: <info>  Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to access point 'traf.alcopop.org'.
NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
NetworkManager: <info>  Activation (eth1) Beginning DHCP transaction.
NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface eth1
NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface eth1
NetworkManager: <info>  Old device 'eth1' activating, won't change.
NetworkManager: <info>  DHCP daemon state is now 2 (bound) for interface eth1
NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled...
NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Get) started...
NetworkManager: <info>  Retrieved the following IP4 configuration from the DHCP daemon:
NetworkManager: <info>    address 192.168.1.66
NetworkManager: <info>    netmask 255.255.255.0
NetworkManager: <info>    broadcast 192.168.1.255
NetworkManager: <info>    gateway 192.168.1.254
NetworkManager: <info>    nameserver 192.168.1.254
NetworkManager: <info>    domain name 'config'
NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Get) complete.
NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
NetworkManager: <info>  DHCP returned name servers but system has disabled dynamic modification!
NetworkManager: <info>  Activation (eth1) successful, device activated.
NetworkManager: <debug> [1209807357.255655] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'traf.alcopop.org'
NetworkManager: <info>  Activation (eth1) Finish handler scheduled.
NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.

[1]+  Stopped                 NetworkManager --no-daemon
qusp:~# bg
[1]+ NetworkManager --no-daemon &
qusp:~# exit

Script done on Sat 03 May 2008 10:36:04 BST