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 677479 - No way to remove unsuccessful wireless connection without other working connection
No way to remove unsuccessful wireless connection without other working conne...
Status: RESOLVED DUPLICATE of bug 653296
Product: NetworkManager
Classification: Platform
Component: general
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2012-06-05 15:24 UTC by Martin Erik Werner
Modified: 2012-06-07 14:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Martin Erik Werner 2012-06-05 15:24:35 UTC 
Debian Wheezy (7), NetworkManager 0.9.4.0-4

If no wireless connections are successfully active there is no way to remove a connection (said connection may be a passphrase-infini-looping as per Bug 676278 (and 10 other reports on bugzilla regarding the constant password-nagging)).

Only when a wireless connection is successfully established is the user able to got in and edit the rest of them.

It would be very logical if it would be possible to configure network connections without needing an active connection, in particular when failed connections cause the mess they currently tend to (and hence you very often want to delete a network connection after it is unsuccessful).
Comment 1 Jiri Klimes 2012-06-07 13:37:40 UTC 
Not sure if you are talking about Gnome 3. If yes, you may be interested in bug 653296. But also, you are able to run nm-connection-editor at any time to manage your connections.
Comment 2 Martin Erik Werner 2012-06-07 14:22:18 UTC 
That's right in both cases :)

I never checked launching the application directly, since I figured what was under system settings was the only available path.

Glad to hear this has been adjusted!

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