[Pkg-utopia-maintainers] Bug#449501: Bug#449501: Bug#449501: network-manager-gnome: nm-applet asks for the keyring password when it obviously doesn't need it

Tue Nov 6 18:26:31 UTC 2007

On Tue, Nov 06, 2007 at 11:52:34AM +0100, Michael Biebl wrote:
> Mike Hommey schrieb:
> > On Tue, Nov 06, 2007 at 11:19:55AM +0100, Michael Biebl <biebl at debian.org> wrote:
> >> Mike Hommey schrieb:
> >>> reopen 449501
> >>> thanks
> >>>
> >>> I think there *is* a n-m-g bug : why does it need the keyring while it
> >>> obviously got the key without it !
> >> That's impossible. Maybe you unlocked it using pam_keyring or
> >> libpam-gnome-keyring.
> > 
> > I wonder if it actually doesn't get help from the wireless driver, since
> > it is reassociating to the same AP with the same key it was using before
> > hibernation. And the keyring dialog does say nm-applet is requesting access
> > to the keyring.
> 
> n-m does not keep the key in memory. In addition, on suspend/hibernate
> the network devices are put to sleep, so they need the key again on
> resume. So it is to expect that n-m-g asks gnome-keyring for the key again.
> I don't yet see where the bug in n-m/n-m-g is?

Here are the logs from NetworkManager after resume from hibernation:
Nov  6 19:12:46 namakemono NetworkManager: <info>  Waking up from sleep. 
Nov  6 19:12:46 namakemono NetworkManager: <info>  Deactivating device wlan0. 
Nov  6 19:12:46 namakemono NetworkManager: <info>  Deactivating device lan0. 
Nov  6 19:12:47 namakemono NetworkManager: <info>  wlan0: Device is fully-supported using driver 'ipw2200'. 
Nov  6 19:12:47 namakemono NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start 
Nov  6 19:12:47 namakemono NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing. 
Nov  6 19:12:47 namakemono NetworkManager: <info>  Now managing wireless (802.11) device 'wlan0'. 
Nov  6 19:12:47 namakemono NetworkManager: <info>  Deactivating device wlan0. 
Nov  6 19:12:47 namakemono NetworkManager: <info>  lan0: Device is fully-supported using driver 'e100'. 
Nov  6 19:12:47 namakemono NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start 
Nov  6 19:12:47 namakemono NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing. 
Nov  6 19:12:47 namakemono NetworkManager: <info>  Now managing wired Ethernet (802.3) device 'lan0'. 
Nov  6 19:12:47 namakemono NetworkManager: <info>  Deactivating device lan0. 
Nov  6 19:12:57 namakemono NetworkManager: <info>  SWITCH: no current connection, found better connection 'wlan0'. 
Nov  6 19:12:57 namakemono NetworkManager: <info>  Will activate connection 'wlan0/xxxxxxxxxxxx'. 
Nov  6 19:12:57 namakemono NetworkManager: <info>  Device wlan0 activation scheduled... 
Nov  6 19:12:57 namakemono NetworkManager: <info>  Activation (wlan0) started... 
Nov  6 19:12:57 namakemono NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... 
Nov  6 19:12:57 namakemono NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started... 
Nov  6 19:12:57 namakemono NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... 
Nov  6 19:12:57 namakemono NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. 
Nov  6 19:12:57 namakemono NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting... 
Nov  6 19:12:57 namakemono NetworkManager: <info>  Activation (wlan0/wireless): access point 'xxxxxxxxxxxx' is encrypted, and a key exists.  No new key needed. 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant^I' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: response was 'OK' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: sending command 'AP_SCAN 1' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: response was 'OK' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: sending command 'ADD_NETWORK' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: response was '0' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 ssid 57616e61646f6f5f36376130' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: response was 'OK' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: response was 'OK' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 wep_key0 <key>' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: response was 'OK' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: response was 'OK' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: sending command 'ENABLE_NETWORK 0' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  SUP: response was 'OK' 
Nov  6 19:12:59 namakemono NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete. 
Nov  6 19:12:59 namakemono NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to access point 'xxxxxxxxxxxx'. 
Nov  6 19:12:59 namakemono NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. 
Nov  6 19:12:59 namakemono NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... 
Nov  6 19:13:00 namakemono NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction. 
Nov  6 19:13:00 namakemono NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. 
Nov  6 19:13:00 namakemono NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface wlan0 
Nov  6 19:13:01 namakemono NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface wlan0 
Nov  6 19:13:04 namakemono NetworkManager: <info>  Old device 'wlan0' activating, won't change. 
Nov  6 19:13:04 namakemono NetworkManager: <info>  DHCP daemon state is now 2 (bound) for interface wlan0 
Nov  6 19:13:04 namakemono NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled... 
Nov  6 19:13:04 namakemono NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) started... 
Nov  6 19:13:04 namakemono NetworkManager: <info>  Retrieved the following IP4 configuration from the DHCP daemon: 
Nov  6 19:13:04 namakemono NetworkManager: <info>    address xxx.xxx.xxx.xxx
Nov  6 19:13:04 namakemono NetworkManager: <info>    netmask 255.255.255.0 
Nov  6 19:13:04 namakemono NetworkManager: <info>    broadcast xxx.xxx.xxx.xxx
Nov  6 19:13:04 namakemono NetworkManager: <info>    gateway xxx.xxx.xxx.xxx
Nov  6 19:13:04 namakemono NetworkManager: <info>    nameserver xxx.xxx.xxx.xxx
Nov  6 19:13:04 namakemono NetworkManager: <info>    domain name 'xxx.xxx' 
Nov  6 19:13:04 namakemono NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... 
Nov  6 19:13:04 namakemono NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete. 
Nov  6 19:13:04 namakemono NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... 
Nov  6 19:13:05 namakemono NetworkManager: <info>  Activation (wlan0) successful, device activated. 
Nov  6 19:13:05 namakemono NetworkManager: <info>  Activation (wlan0) Finish handler scheduled. 
Nov  6 19:13:05 namakemono NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. 

So, obviously, n-m has been able to use a key it had in memory. Now, why
does n-m-g asks the keyring ?

Mike