394833 – knetworkmanager does not autoconnect with a wpa key

Bug 394833 - knetworkmanager does not autoconnect with a wpa key

Summary: knetworkmanager does not autoconnect with a wpa key

Status:	RESOLVED DUPLICATE of bug 391415

Alias:	None

Product:	openSUSE 11.0
Classification:	openSUSE
Component:	Network (show other bugs)
Version:	Factory
Hardware:	i586 openSUSE 11.0

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	Will Stephenson
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2008-05-27 19:16 UTC by Clovis Gladstone
Modified:	2008-05-27 21:31 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Clovis Gladstone 2008-05-27 19:16:26 UTC

I have tried to delete my profile and recreate it several times to make sure that I checked the autoconnect box, but knetworkmanager still won't autoconnect. And this is only the case with a wpa key. I use wpa2. If I use a wep key (which truthfully is not an option) autoconnect works.

Comment 1 Jörg Hermsdorf 2008-05-27 21:25:35 UTC

I can confirm that with my Lenovo ThinkPad T60p using the iwl3945 device.
Besides the fact, that knetworkmanager does not not even try to autoconnect on subsequent logins, it fails to successfully connect using the previously stored (and once working) setup when triggered manually.
I have to remove the connection setup from knetworkmanager, disable the wireless device and reenable + setup the connection (essid, wpa key, ...) again, to successfully connect to my access point.
When I logoff and relogin, it's the same game again. No autoconnect and no manually triggered connection, unless I remove the setup and resetup the connection again.

Comment 2 Jörg Hermsdorf 2008-05-27 21:31:11 UTC

Oh... there's already a bug for that.

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