Description of problem: It happens on a Live session as well on an installed system. If there is a DHCP and you modify the network config, i.e. try to set up a static (manual) ipv4 address, or disable ipv6 or whatever, it works. If there is not a DHCP server on your network, so the connection doesn't have an IP and it is in connecting state, you are unable to modify the network, mainly set up a static ip address. The Apply button remains gray. Version-Release number of selected component (if applicable): gnome-control-center-40~beta-1.fc34.x86_64 How reproducible: If the connection doesn't have an IP assigned by the DHCP. Steps to Reproduce: On bare metal, if there is not a DHCP on your network. On a VM, with virt-manager, try to create a virtual network deselecting the DHCP. Then create a VM with the NIC on this network. Start a Live (like Fedora-Workstation-Live-x86_64-34-20210222.n.0.iso), you can't set up a manual ipv4, the Apply button remains gray. Expected results: You should be able to set up a static ipv4 if there is not a DHCP server on your network.
Proposed as a Blocker for 34-final by Fedora user alciregi using the blocker tracking app because: I propose this bug as final blocker due to this criteria. Default panel functionality All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use. However, it could be a beta blocker as well: if a user can't manually set up the network, it could be a bad experience.
+4 in https://pagure.io/fedora-qa/blocker-review/issue/254 , marking accepted.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/963 fixes bug 1936120 for me and I suppose it would fix this one too…
Also created PR for dist-git: https://src.fedoraproject.org/rpms/gnome-control-center/pull-request/8
FEDORA-2021-d4d69752d3 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-7c83318a60 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7c83318a60
FEDORA-2021-7c83318a60 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-7c83318a60` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-7c83318a60 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Reopening as it was the F35 fix that went to stable, not F34 one we are tracking here.
D'oh, we should really have pulled this in for the Beta candidate :( Proposing as a Beta FE in case we respin.
+3 in https://pagure.io/fedora-qa/blocker-review/issue/254 , marking accepted FE.
FEDORA-2021-b372f76251 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-b372f76251` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-b372f76251 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-b372f76251 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-d87acb1ecd has been pushed to the Fedora ELN stable repository. If problem still persists, please make note of it in this bug report.