Bug 262183

Summary:	NetworkManager "remembers" bad wireless settings
Product:	[openSUSE] openSUSE 10.3	Reporter:	Aaron Mulder <ammulder>
Component:	Network	Assignee:	Helmut Schaa <hschaa>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Alpha 2
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Aaron Mulder 2007-04-06 20:05:24 UTC

If I try to configure my wireless security settings with NetworkManager, and the connection fails, and I select the same network to connect to again, it doesn't give me a chance to edit the settings.  So it fails again.

Under 10.2, my recollection is that it always came up with a blank settings screen if the previous attempt failed to connect.

To me, it would be ideal if it brought the security settings screen up again, but with the previous values populated as defaults (perhaps leaving the passphrase blank if that's a security concern).

As it is now, I seem to have to log out and log back in again in order to be able to change the settings and try again.

Comment 1 Aaron Mulder 2007-04-10 17:10:22 UTC

Oops, I just noticed that this was assigned to the GNOME team and I neglected to mention that I'm using KDE and KNetworkManager.  Not sure if it makes a difference.

Comment 2 Kai Zimmer 2007-07-16 12:27:12 UTC

Here the network manager doesn't remember it was configured to use a static adress (and uses dhcp instead). Maybe that's related to the above mentioned bug... But it works fine if i use the "traditional" ifup-method...

Comment 3 JP Rosevear 2007-07-26 20:16:02 UTC

I believe its up to the knetworkmanager front end to store/re-ask the credentials.

Comment 4 Timo Hoenig 2007-07-27 09:04:19 UTC

Helmut, can you please comment?  Thanks!

Comment 5 Helmut Schaa 2007-07-30 11:07:24 UTC

> To me, it would be ideal if it brought the security settings screen up again,
> but with the previous values populated as defaults (perhaps leaving the
> passphrase blank if that's a security concern).

That's how it works for me.

Aaron, can you please give a bit more information on how to reproduce this issue? Can you please attach /var/log/NetworkManager?

Thanks

Comment 6 Helmut Schaa 2007-08-29 08:59:53 UTC

Aaron, any news on this topic?
Did you try with a 10.3 beta yet?

Comment 7 Helmut Schaa 2007-10-19 10:57:27 UTC

Closing this one as FIXED as it is most likely fixed in 10.3.

Please reopen if you experience the same problems in 10.3.