Bug 1808564
Summary: | Wi-fi networks not displayed in F32 SoaS (works in F31 SoaS) spin | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alex Perez <aperez> |
Component: | sugar | Assignee: | Simon Schampijer <simon> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | acardace, aperez, awilliam, bgalvani, dcbw, fgiudici, gmarr, gnome-sig, ibiam, john.j5live, lkundrak, mclasen, pbrobinson, rhughes, rstrode, sandmann, sebastian, simon, smparrish, tomeu |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | AcceptedFreezeException | ||
Fixed In Version: | sugar-0.116-5.fc32 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-10 01:56:18 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1705304 |
Description
Alex Perez
2020-02-28 20:11:18 UTC
sugar-base doesn't exist any more. Peter can you change the component and assign this to me, thanks. This needs further investigation, it looks like a NM issue, not sure whether it's a regression or whether it's a deprecation that wasn't advertised to the sugar community. Do you see wifi networks in the output of 'nmcli device wifi'? Executing 'nmcli device wifi' lists all wi-fi networks as expected, and shows that it's connected to "Ad-hoc network 1" by default, which is not desired/expected behavior. These same networks don't show up on the Network Neighborhood Sugar page (F1), and therefore I suspect this is a NetworkManager API issue. Interestingly, the connected ad-hoc network 1 does not show as connected in the Sugar UI, either, and it should. FEDORA-2020-59fe8b4ca5 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-59fe8b4ca5 sugar-0.116-5.fc32, sugar-toolkit-gtk3-0.116-7.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-59fe8b4ca5 With FEDORA-2020-59fe8b4ca5 applied (now in the nightlies), this problem appears to be resolved, and wi-fi networks are detected, and usable. Proposed as a Freeze Exception for 32-beta by Fedora user pbrobinson using the blocker tracking app because: Fixes displaying WiFi networks on the Sugar desktop/SoaS. Being able to connect to wifi using the GUI is useful :) +1 FE for me. Discussed during the 2020-03-09 blocker review meeting: [0] The decision to classify this bug as an "AcceptedFreezeException" was made as it is a noticeable issue that cannot be fixed with an update. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-03-09/f32-blocker-review.2020-03-09-16.01.txt sugar-0.116-5.fc32, sugar-toolkit-gtk3-0.116-7.fc32 has been pushed to the Fedora 32 stable repository. If problems still persist, please make note of it in this bug report. |