RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1879405 - Unable to connect to Wi-Fi WPA2 enterprise network via system menu
Summary: Unable to connect to Wi-Fi WPA2 enterprise network via system menu
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-shell
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Florian Müllner
QA Contact: Filip Pokryvka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-16 08:45 UTC by Filip Pokryvka
Modified: 2023-05-16 09:58 UTC (History)
4 users (show)

Fixed In Version: gnome-shell-3.32.2-50.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-16 08:37:43 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2023:2841 0 None None None 2023-05-16 08:37:50 UTC

Description Filip Pokryvka 2020-09-16 08:45:22 UTC 
Description of problem:
Connect to WPA2 enterprise network via system menu shows error instead of new connection dialog. 

Version-Release number of selected component (if applicable):
gnome-shell-3.32.2-20.el8.x86_64
gnome-control-center-3.28.2-22.el8.x86_64

How reproducible:
always

Steps to Reproduce:
Ensure that wpa2 enterprise network is in range
1. system menu
2. Wi-Fi
3. Select Network
4. click on WPA2 enterprise network name
5. click connect

Actual results:
Notification with error is shown:
Execution of 'gnome-control-center' failed:
Array element (type filename) may not be null

Expected results:
The dialog asking for enterprise credentials should appear.

Additional info:
It is possible simulate Wi-Fi (and also WPA2 enterprise network) using script from NetworkManager-ci repo:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/blob/master/prepare/hostapd_wireless.sh
Comment 1 Filip Pokryvka 2020-09-20 11:09:25 UTC 
I noticed that also Connect to Mobile Broadband device does not work (the same error). Should I create the bug for it or is it the same fix?
Comment 3 Benjamin Berg 2021-01-11 16:31:38 UTC 
The dialog there comes from gnome-shell and the issue is that it doesn't manage to launch gnome-control-center.

To me, this looks like it may be https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/33ffdd60611e8e8d0018680dd97bcbd0e98c6b4b
Comment 4 Florian Müllner 2021-04-20 17:36:50 UTC 
(In reply to Benjamin Berg from comment #3)

> To me, this looks like it may be
> https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/
> 33ffdd60611e8e8d0018680dd97bcbd0e98c6b4b

It looks like it, but that commit is already included in gnome-shell-3.32.2-20.el8.x86_64 (the upstream fix landed in 3.30.1).


> It is possible simulate Wi-Fi (and also WPA2 enterprise network) using script from NetworkManager-ci repo:

Are there instructions somewhere how to use that script?
Comment 5 Filip Pokryvka 2021-04-20 18:56:40 UTC 
> Are there instructions somewhere how to use that script?

I would not recommend running the script on physical machine (as it restarts NetworkManager and so breaks active Wi-Fi/VPN connections), it is better to use in VM.

You need to have hostapd and kernel-modules-internal installed, and run it as following from NetworkManager-ci directory:

sudo sh prepare/hostapd_wireless.sh tmp/8021x/certs namespace

If script succeeds, new Wi-Fi card should be visible, wpa2-eap is name of the network which fails.

To cleanup (remove virtual wifi-card), you can run:

sudo sh prepare/hostapd_wireless.sh teardown
Comment 7 Filip Pokryvka 2022-02-14 10:36:20 UTC 
I have checked with latest packages, and there is a change of behavior: no error notification, however no login dialog, too.

gnome-shell-3.32.2-44.el8.x86_64
gnome-control-center-3.28.2-31.el8.x86_64
Comment 8 Filip Pokryvka 2022-02-14 10:55:21 UTC 
In RHEL9, the behavior is also different, clicking "Connect" with "wpa2-eap" selected does nothing, dialog with network list stays there, clicking connect on "wpa3-eap" (which has no GUI support yet), closes dialog but then does nothing.
Comment 9 RHEL Program Management 2022-03-16 07:27:21 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 13 Florian Müllner 2022-10-21 18:42:33 UTC 
I've never been able to reproduce the issue. The network-manager script apparently depends on packages that aren't available in the RHEL repo I am using (or EPEL), and running the JS code that gnome-shell uses to open the panels with made-up device parameters works in so far as control-center opens and displays the correct panel. I tested both spawning a gnome-control-center argv (RHEL 8) and D-Bus activating the 'launch-panel' action (RHEL 9).
Comment 14 Filip Pokryvka 2022-10-24 08:59:40 UTC 
Created attachment 1919920 [details]
notification showing error

RHEL 9 seems to work, in RHEL 8 there is just notification that launch of gnome-control-center failed. It complains that filename is null, so maybe gnome-shell is not providing required arguments? I can provide you with more logs, if you describe me which logs might be helpful.
Comment 15 Filip Pokryvka 2022-10-24 09:01:31 UTC 
(In reply to Florian Müllner from comment #13)
> I've never been able to reproduce the issue. The network-manager script
> apparently depends on packages that aren't available in the RHEL repo I am
> using (or EPEL), and running the JS code that gnome-shell uses to open the
> panels with made-up device parameters works in so far as control-center
> opens and displays the correct panel. I tested both spawning a
> gnome-control-center argv (RHEL 8) and D-Bus activating the 'launch-panel'
> action (RHEL 9).

Can you send me commands you have tested on RHEL 8?
Comment 16 Florian Müllner 2022-11-21 18:11:11 UTC 
(In reply to Filip Pokryvka from comment #14)
> RHEL 9 seems to work

Ah, I bet it's https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2194.

For good measure, we could also backport https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1385 to get the same code as in RHEL 9.
Comment 22 errata-xmlrpc 2023-05-16 08:37:43 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (gnome-shell bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2841
Note You need to log in before you can comment on or make changes to this bug.