Ubuntu
knetworkmanager package

knetworkmanager forgets association with AP after reboot

Bug #156413 reported by Macavity
10
Affects Status Importance Assigned to Milestone
knetworkmanager (Ubuntu)
Invalid
Undecided
Luka Renko

Bug Description

knetworkmanager loads at startup and will connect to APs when selected manually. However, upon reboot, knetworkmanager 'forgets' the association and one must manually select the network again. There doesn't seem to be a way to do the equivalent of Windows XP's 'Automatically connect to preferred wireless network.'

Unlike other similar bugs, knetworkmanager runs at startup, and there is no problem connecting to the AP when selected manually. It will even remember the WEP key. It just won't connect automatically!

This problem is specific to knetworkmanager. If I configure the connection manually via modifying /etc/network/interfaces, I don't see the problem.

It's not an issue with the card, as the problem occurs on two wifi cards with completely different chipsets (rt2500 and prism54).

Kubuntu Gutsy
2.6.22-14-generic
Dell Latitude C810
3Com 3CRWE154G72 PCMCIA wireless card

Revision history for this message
dopez (dopez) wrote :
Download full text (4.0 KiB)

I can confirm this, it does work when you keep your keys in kwallet but then it asks for your password after logging in.

Here is part of my daemon.log containing an error that it cannot find the key (see the <WARN>), even though it's saved in knetworkmanager's config file, after manually selecting the network it does connect without asking for the key :

Nov 24 10:37:46 p1500 NetworkManager: <info> Updating allowed wireless network lists.
Nov 24 10:37:46 p1500 NetworkManager: <info> Updating VPN Connections...
Nov 24 10:37:46 p1500 NetworkManager: <info> SWITCH: no current connection, found better connection 'eth1'.
Nov 24 10:37:46 p1500 NetworkManager: <info> Will activate connection 'eth1/bruno'.
Nov 24 10:37:46 p1500 NetworkManager: <info> Device eth1 activation scheduled...
Nov 24 10:37:46 p1500 NetworkManager: <info> Activation (eth1) started...
Nov 24 10:37:46 p1500 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Nov 24 10:37:46 p1500 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Nov 24 10:37:46 p1500 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Nov 24 10:37:46 p1500 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Nov 24 10:37:46 p1500 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Nov 24 10:37:46 p1500 NetworkManager: <info> Activation (eth1/wireless): access point 'bruno' is encrypted, but NO valid key exists. New key needed.
Nov 24 10:37:46 p1500 NetworkManager: <info> Activation (eth1) New wireless user key requested for network 'bruno'.
Nov 24 10:37:46 p1500 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Nov 24 10:37:46 p1500 NetworkManager: <info> Old device 'eth1' activating, won't change.
Nov 24 10:37:46 p1500 NetworkManager: <WARN> nm_dbus_get_user_key_for_network_cb(): nm_dbus_get_user_key_for_network_cb(): dbus returned an error. (org.freedesktop.NetworkManagerInfo.GetKeyError) org.freedesktop.NetworkManagerInfo.GetKeyError
Nov 24 10:37:46 p1500 NetworkManager: <info> Activation (eth1) failure scheduled...
Nov 24 10:37:47 p1500 NetworkManager: <info> Activation (eth1) failed for access point (bruno)
Nov 24 10:37:47 p1500 NetworkManager: <info> Activation (eth1) failed.
Nov 24 10:37:47 p1500 NetworkManager: <info> Deactivating device eth1.
Nov 24 10:37:54 p1500 NetworkManager: <debug> [1195897074.092559] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'bruno'
Nov 24 10:37:54 p1500 NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / bruno
Nov 24 10:37:54 p1500 NetworkManager: <info> Deactivating device eth1.
Nov 24 10:37:54 p1500 NetworkManager: <info> Device eth1 activation scheduled...
Nov 24 10:37:54 p1500 NetworkManager: <info> Activation (eth1) started...
Nov 24 10:37:54 p1500 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Nov 24 10:37:54 p1500 NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Nov 24 10:37:54 p1500 NetworkManager: <info> Activation (eth1) Stage 2 of 5...

Read more...

Revision history for this message
Macavity (ean25) wrote :

As a workaround for this bug, one can configure knetworkmanager to save the wireless key in kwallet, and than set a blank password for kwallet. Both knetworkmanager and kwallet will open 'silently' upon boot and the connection will activate. Obviously this isn't an ideal solution! If anyone reading this bug needs a step-by-step guide as to how to do the above I will be happy to supply one.

Revision history for this message
Luka Renko (lure) wrote :

knetworkmanager 0.2.2 is now available in Hardy and have some fixes for handling KWallet passwords that can help with your problem.
Can you check if you can reproduce this with up-to-date Hardy?

Changed in knetworkmanager:
assignee: nobody → lure
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in knetworkmanager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.