Description of problem: Removing packages group kde-desktop-environment, removes from Gnome the means to connect graphically to Wi-Fi networks. Version-Release number of component: dnf.noarch 4.4.0-2.fc33 How reproducible: Initial situation: Fedora installed via Fedora Desktop then group kde-desktop-environment installed and logged into. From Gnome session: # dnf -y remove @kde-desktop-environment # dnf -qy autoremove # reboot $ gnome-control-center $ systemctl status wpa_supplicant $ nmcli radio wifi on Actual results: Wi-Fi selections are not longer available from gnome-control-center neither from Gnome interface.. $ systemctl status wpa_supplicant ● wpa_supplicant.service - WPA supplicant Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: disabled) Active: active (running) $ nmcli radio wifi enabled Expected result: Connection means to Wi-Fi network to be preserved. Required components not to be removed from Gnome.
Would it required one of these packages groups to be defined as marked? $ dnf -q --hidden group list installed | sed 1d | column Anaconda tools Hardware Support base-x LibreOffice Container Management Multimedia Core Common NetworkManager Submodules Firefox Web Browser Printing Support Fonts Virtualization GNOME Fedora Workstation product core Guest Desktop Agents x86 Baremetal Tools $ dnf --ids --hidden -q group list installed | tail -0 Command line error: argument --hidden: not allowed with argument --ids The option '--ids' seems the only one able to provide the required field for allowing a group to be marked!
I actually stumbled upon the same issue last week. For me, it turned out I had somehow managed to remove the iwl*-firmware package for my Intel wireless adapter. This happened after me removing the KDE group and other related packages, so I guess it really could have been the reason. I would definitely try installing the corresponding iwl*-firmware package and then rebooting.
I am really sorry, but this is known issue (See Bug 1554010 - No env. group installed after Fedora installation). After installation of Fedora workstation there is not marked Fedora workstation as installed. Then you install a second environment but dnf do not know that this is a second environment, therefore comps group that are shared between Gnome and KDE could be removed. The problem is not in installer (anaconda), but in spin-kickstart that provides incorrect data to installer.
I create PR - that should fix the issue - https://pagure.io/fedora-kickstarts/pull-request/729
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.