+++ This bug was initially created as a clone of Bug #1274505 +++ Description of problem: In the GUI for Security settings, I see 802.1x when it should be 802.1X You can see this when using GNOME GUI or nm-connection-editor Version-Release number of selected component (if applicable): NetworkManager-1.0.6-6.fc23.x86_64 Steps to Reproduce: press the Super key to enter the Activities Overview, type control network and then press Enter. The Network settings tool appears. Select the Wired network interface from the left-hand-side menu if it is not already highlighted. click the gear wheel icon see the Identity view if using the GNOME tool or the General tab if using nm-connection-editor Actual results: Tab shows 802.1x Expected results: 802.1X Additional info: --- Additional comment from Blueowl on 2016-07-27 15:14:24 EDT --- Right, the standard is called 802.1X. The name should be shown correctly at least in the UI. Fixed in nm-connection-editor upstream: https://git.gnome.org/browse/network-manager-applet/commit/?id=92a694a1e0a54a26940c2c232b48be056e616ad9 Clone the bug for control-center [network] component to have a fix in Gnome UI. --- Additional comment from Fedora End Of Life on 2016-11-24 07:53:00 EST --- This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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. --- Additional comment from Stephen Wadeley on 2016-11-24 08:09:30 EST --- Hello checked in my Fedora 25 workstation I see its fixed in nm-connection-editor but not in control-center [network] component. Will attempt to clone as suggested. Thank you Blueowl
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora 'version' of '25'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.