Red Hat Bugzilla – Bug 442925
Wireless edit form is ignoring changes for "Connect autom" option
Last modified: 2008-05-19 13:02:18 EDT
Description of problem:
After enable/disable "Connect automaticly" option the OK button is not enabled
when editing a wireless connection and thus cannot save.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Edit a wireless connections
2. check the "Connect automaticly" option and try to save it.
I'm running in KDE ...
Fixed with latest koji builds, can you please test?
Created attachment 303536 [details]
Problem not solved yet..
It seems this problem only occurs when there is "Auto" (dunno why it's there)
prepended to the networkname as you can see on the screenshot.
I cannot reproduce with latest koji builds. Editing an "auto" connection brings
up the editor window with an enabled OK button, and clicking the checkbox keeps
the OK button enabled. Can you verify with the latest koji build?
I can confirm bug in latest rawhide:
[root@boomer ~]# rpm -q NetowrkManager-gnome
After applying build 47742 from koji, behaviour is back to expected and you can
click 'OK'. I tried changing an 'AUTO <bssid>' access point from DHCP to static
IP addressing, 'OK' is shaded until you finish entering the gateway address then
you are able to successfully save entry.
[root@boomer ~]# rpm -q NetworkManager-gnome
Nice to see it fixed for you :) It's somehow fixed here, in other words the OK
button can be pressed now. But it seems the setting is NOT being saved. And I
ERROR:(page-wireless-security.c:407):update_connection: assertion failed:
Adding a new connection is also not being saved ...
Hmmmmm very weird, as build svn3623 as fixed this for me.
I stumbled upon this because I had an issue setting up a static IP address for
my home wireless setup. Now, I've installed those latest packages it seems to
save all the data fine and connect perfectly with a static address set.
Sorry to state the obvious :-) but did you update?
On my system:
[root@boomer ~]# rpm -qa | grep NetworkManager
You may want to reopen this bug or open a new one with the new bug you are
I tried to remove/install the rpm's but the problem still exists ...
[root@localhost ~]# rpm -qa | grep NetworkManager
Anyways I found something out, this only occurs when security is set to
"None". I don't know if it's supposed to be act this way ....
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
rpm -qa | grep NetworkManager | sort
and I'm still seeing this behavior on fresh Fedora 9 install with Intel 3945. No
matter what I try to change the OK button is inactive. I have to close the
window and when I open it for the second time the OK button is active right from
the start, even if I did not change anything. Now if I change something I can
save it, but hitting the OK button results in a crash of nm-connection-editor,
at least in 9 out of 10 attempts.
Please tell me what you need to debug this.
Christoph: can you try:
which has just been submitted as an F9 testing update.
Unfortunately I can't reproduce the issue I described in the comment above any
longer. After I managed to change the connection for the first time it now seems
to work reliably. Changes are correctly saved and applied.
Nevertheless I will try your updates because NM works really bad here. It looses
the connection after 5-10 minutes, but this is a different issue. I will try
your packages and then file another bug if necessary. This one seems fixed for me.
Ok; thanks. If your connection keeps dropping, that is more likely a kernel
driver issue than an NM issue. We can try to get some logs from wpa_supplicant
to determine what events the driver is sending that would cause the disconnect.
But as you say, that's a different bug entirely. I'll close this one.