Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The list of available Wi-Fi networks is sometimes empty after clicking the "Select network" button, although Wi-Fi networks were available/displayed before. See steps to reproduce.
Version-Release number of selected component (if applicable):
anaconda-33.16.4.5-1.el8
How reproducible:
Always
Steps to Reproduce:
1. Installation started from boot.iso on a USB drive.
2. Proceed to the Network spoke, select the wifi device and click "Select network".
3. Select one of the networks protected by a password, click "Connect", but do not enter any password and click "Cancel".
4. Click on the "Select Network" button again (do it quickly).
Actual results:
The list of available wifi networks is empty.
Expected results:
The list of available networks is populated.
Additional info:
Workaround is to wait a while and click the "Select network" later (in about 10 seconds). Perhaps there is a refresh of the available networks happening at this time?
The same problem with empty list of wifi networks happens right after enabling the wifi device. There is no info if there are no networks available or if scanning is in progress.
I noticed that this is also a problem in installed system environment GUI: top panel -> Select Network GUI dialog. When I was testing the patches running Anaconda on installed system (F32) the behaviour in this aspect seemed the same for the system dialog and for Anaconda dialog so I think the root cause is on NetworkManager scanning the networks / APs ?
Comment 5Beniamino Galvani
2021-01-20 15:52:13 UTC
NM doesn't scan while it's connecting to a Wi-Fi network, so after the activation is canceled, you have to wait for a new scan to get the updated results. However I expect that the APs that were detected before would stay in the list for a certain time (at least a minute).
> There is no info if there are no networks available or if scanning is in progress.
This seems more like a GUI problem.
Comment 7RHEL Program Management
2022-07-12 07:27:28 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.