Bug 745435 - NM: inconsistent VPN connection naming
Summary: NM: inconsistent VPN connection naming
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 16
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-12 11:09 UTC by Stefan Assmann
Modified: 2013-02-13 13:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 13:03:25 UTC
Type: ---


Attachments (Terms of Use)
vpn-name.png (452.92 KB, image/png)
2011-10-12 11:09 UTC, Stefan Assmann
no flags Details

Description Stefan Assmann 2011-10-12 11:09:41 UTC
Created attachment 527673 [details]
vpn-name.png

Description of problem:
Creating a vpn connection with the default naming "VPN connection 1" results in
connection name of "VPN connection 1 VPN" in the network settings dialog. It looks ok when clicking on the NM icon.
Screenshot attached.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.0-1.fc16.x86_64

How reproducible:
always
  
Actual results:
inconsistent vpn connection naming.

Expected results:
vpn connections should show up with the exact same name everywhere.

Comment 1 Jirka Klimes 2011-10-19 09:57:53 UTC
The names are the same. The "VPN" suffix just denotes the connection is of VPN type.
We could argue it may be marked better. Nonetheless, it's up to the designers of gnome-control-center and thus it would be better to file that upstream.

Comment 2 Fedora End Of Life 2013-01-16 12:40:53 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 3 Fedora End Of Life 2013-02-13 13:03:28 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.


Note You need to log in before you can comment on or make changes to this bug.