Bug 2076754 - Connecting to a WPA2 enterprise network that uses an encrypted .p12 certificate fails.
Summary: Connecting to a WPA2 enterprise network that uses an encrypted .p12 certifica...
Keywords:
Status: CLOSED DUPLICATE of bug 2072070
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 36
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-19 18:52 UTC by Angelo Theodorakis
Modified: 2022-05-03 12:02 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-05-03 12:02:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Angelo Theodorakis 2022-04-19 18:52:40 UTC
Description of problem:
Connecting to a WPA2 enterprise network that uses an encrypted .p12 certificate fails. The encryption password is stored in Seahorse. 

When attempting to connect to the network, a popup asks for the encryption key. 
When attempting to open the wiki settings, gnome-control-center crashes
When using CLI (nmcli connection up {wifi_name}) an error appears: Passwords or encryption keys are required to access the wireless network.

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

NetworkManager --version
1.37.91-1.fc36

How reproducible:
Always

Steps to Reproduce:
1. Select WPA2 enterprise network from list of SSIDs found in control center
2. Click on gear icon beside network name
3. System settings crash

Actual results:

Unable to connect to the wifi network. Attempting to edit network settings even crash control center

Expected results:

Successfully connect to the wifi network

Additional info:

retrace: https://retrace.fedoraproject.org/faf/reports/390072/

---------------------------------------

journalctl -xe NM_CONNECTION=36242327-f96d-47c3-abd0-8551dc53c115 + NM_DEVICE=wlp0s20f3 error: 
 (wlp0s20f3): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed')

---------------------------------------

Comment 1 Angelo Theodorakis 2022-05-03 12:02:51 UTC

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


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