After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 564454 - nm-connection-editor always reports Invalid wireless security
nm-connection-editor always reports Invalid wireless security
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: nm-applet
0.7.x
Other All
: Normal major
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2008-12-14 09:19 UTC by Pacho Ramos
Modified: 2009-05-10 20:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
conexion (533 bytes, text/plain)
2008-12-14 10:00 UTC, Pacho Ramos
Details

Description Pacho Ramos 2008-12-14 09:19:21 UTC
Please describe the problem:
When I try to add my WEP encryption key, it always fails. I paste it (8ab0faa2ee10d27ee6d94df0bb) and, even when I click on "Apply", if I reopen nm-connection-editor, the box appears still empty and the following error is shown:
** (nm-connection-editor:17582): WARNING **: Invalid setting Seguridad inalámbrica: Invalid wireless security

It works just fine with wpa_supplicant, then, I don't know why NetworkManager doesn't like it

I am using NetworkManager under gentoo with consolekit-0.2.10 and hal-0.5.11

Thanks a lot

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Pacho Ramos 2008-12-14 10:00:14 UTC
Created attachment 124631 [details]
conexion

This is my /etc/NetworkManager/system-connections file
Comment 2 Matthew Turnbull 2009-01-11 01:09:24 UTC
I can confirm this on Gentoo (consolekit-0.2.3, policykit-0.9, policykit-gnome-0.9.2, hal-0.5.11)

I have found that this happens when you have a globally configured network but the key isn't also stored in the keyring. This doesn't seem to affect being able to connect to the network, but you are unable to edit the network.

My quick workaround is to edit the network, un-share the network (un-check available to all users) and re-add the key, then apply the changes. Then edit the network again and re-share it. This should add the key to the keyring and now nm-connection-editor should work as expected.
Comment 3 Pacho Ramos 2009-03-08 15:12:53 UTC
Is this the proper way of sending bug reports or mailing list has to be used instead?
Comment 4 Dan Williams 2009-05-10 02:53:46 UTC
Fixes were committed on April 4th.  Pulling secrets from system connections should work in 0.7.1.
Comment 5 Pacho Ramos 2009-05-10 20:55:30 UTC
Thanks