Bug 1576976 - NetworkManger fails to connect WPA with non-alpha chars : regression
Summary: NetworkManger fails to connect WPA with non-alpha chars : regression
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 28
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-10 21:31 UTC by Federic
Modified: 2019-05-28 20:10 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-28 20:10:52 UTC
Type: Bug

Attachments (Terms of Use)

Description Federic 2018-05-10 21:31:49 UTC
Description of problem:
NetworkManger fails to connect WPA with password containing non-alpha chars eg comma or question mark.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install fedora 28 i386 XFCE spin
2. set WPA wifirouter pw to include comma and question mark characters
3. configure connection in NetworkManager
4. attempt to connect

Actual results:
after some delay the connection attempt times out. 

Expected results:
configured pw is accepted by router.

Additional info:
NM sees available networks but fails to connect. 
changing pw to contain only alpha characters fixes the problem. I did not test whether both or just one of the chars cited was the problem.

This seems to be a regression since Fed 26 since I have a 64 bit laptop which was working with the original , more secure password.

Comment 1 Ben Cotton 2019-05-02 21:48:37 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.

Comment 2 Ben Cotton 2019-05-28 20:10:52 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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

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.