Bug 1879405
| Summary: | Unable to connect to Wi-Fi WPA2 enterprise network via system menu | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Filip Pokryvka <fpokryvk> |
| Component: | gnome-shell | Assignee: | Florian Müllner <fmuellner> |
| Status: | CLOSED ERRATA | QA Contact: | Filip Pokryvka <fpokryvk> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.3 | CC: | fmuellner, jadahl, tpelka, tpopela |
| Target Milestone: | rc | Keywords: | Reopened, Triaged |
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gnome-shell-3.32.2-50.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-16 08:37:43 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Filip Pokryvka
2020-09-16 08:45:22 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? 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 (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? > 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
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 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. 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. 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). 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.
(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? (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. 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 |