Bug 697606

Summary: Gnome 3 interface for Network Manager makes it difficult to do some important things
Product: [Fedora] Fedora Reporter: cam <camilo>
Component: control-centerAssignee: Control Center Maintainer <control-center-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: control-center-maint, dcbw, gatlinsullivan, jklimes, marco.laverdiere, pmrpla, rstrode, xintx.ua
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-14 00:57:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description cam 2011-04-18 18:18:59 UTC
Description of problem:
When testing NM in F15 I found that I was unable to delete remembered details of networks. If it is possible at all it wasn't obvious how to do it. This is important as can be seen in BZ697605 where incorrect details are remembered.


Version-Release number of selected component (if applicable):
NetworkManager-0.8.998-2.git20110406.fc15.i686


How reproducible:
100%

Steps to Reproduce:
1.put newbie in front of NM
2.ask user to delete a stored wireless network details
3.
  
Actual results:
User can't see how to do it

Expected results:
It should be possible to delete the entries, so long as it's possible for them to be incorrect or overly abundant.

Additional info:
The Gnome 2 interface to Network Manager used to allow deleting connections relatively intuitively. This is just one of many ways Gnome 3 has been made... :)

Comment 1 cam 2011-04-19 06:34:27 UTC
I have found (thanks to Paul Frields for pointing it out) that you can still access the old NM connection manager by searching for it - 'connections'. From there you can delete and edit as before. Work is in progress to integrate the features in the GUI.

Comment 2 gatlibs 2011-10-05 20:06:46 UTC
This bug should be re-opened. Using Fedora 16 Beta, I still cannot figure how to delete a "remembered connection". There is an option to configure; Click the wireless status in the top right, Network Settings, Configure. There isn't a delete in the configuration.
Name        : gnome-shell
Arch        : x86_64
Version     : 3.2.0
Release     : 2.fc16

Comment 3 cam 2011-10-06 05:15:59 UTC
NetworkManager-gnome-0.9.1.90-3.git20110927.fc16.i686
It is still possible to connect to an open AP accidentally, and the configuration options now include removing the automatic connection ability, but not removing or 'blacklisting' the open AP.

An open AP might be malicious and it might be desirable to treat them with more contempt than leaving them in the list.

It's still possible to open the network connections dialog as described in comment 1, but there doesn't seem to be an easy link to it from the NM GUI.

I am reopening this as F16 does not seem to have addressed the problem.

Comment 4 Jirka Klimes 2011-10-06 12:08:06 UTC
*** Bug 697884 has been marked as a duplicate of this bug. ***

Comment 5 Jirka Klimes 2011-10-06 12:25:48 UTC
There are some deficiencies with gnome-control-center network panel's design. 
There should be a means of running connection editor from the panel for all
connections. 
Nonetheless, you can simply invoke the editor from Applications->Other->Network
Connections.

The main problem appears to be that instead of one GUI of Gnome 2 (nm-applet),
there are now more places to deal with NM - shell indicator, control-center
network panel and connection editor.

See also description http://live.gnome.org/ControlCenter/SystemSettings/Network

Comment 6 Fedora End Of Life 2013-01-16 22:26:14 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Fedora End Of Life 2013-02-14 00:57:44 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.