Bug 151265 - knetworkmanager forgets association to AP upon reboot
Summary: knetworkmanager forgets association to AP upon reboot
Status: RESOLVED DUPLICATE of bug 148884
Alias: None
Product: knetworkmanager
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-23 23:14 UTC by Edmund Nash
Modified: 2008-06-15 11:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Edmund Nash 2007-10-23 23:14:47 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

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.'

Please note this is not the same as bug#144725 or 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
Comment 1 Will Stephenson 2008-06-15 11:27:06 UTC

*** This bug has been marked as a duplicate of 148884 ***