* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)? No * Does the service listen on a network socket for connections originating on a separate physical or virtual machine? No * Is the service non-persistent (i.e. run once at startup and exit)? No * What is the exact name (or names) of the systemd unit files to be enabled? cosmic-greeter.service * Is this request for all Fedora deliverables or only for some Editions (list them)? Not sure, I would like to add it to 85-display-manager.preset from fedora-release https://src.fedoraproject.org/rpms/fedora-release I think that would make it enabled for all deliverables.
(In reply to Ryan Brue from comment #0) > * Is this request for all Fedora deliverables or only for some Editions > (list them)? > > Not sure, I would like to add it to 85-display-manager.preset from > fedora-release https://src.fedoraproject.org/rpms/fedora-release > > I think that would make it enabled for all deliverables. The question here is about the desired state. You want to treat it like any of the other display managers, so that's fine. I'll get this added.
I've merged this to Rawhide/F42 and it's building now. Is this something that should be included in Fedora 41 as well?
Hi, sorry for the delay: @sgallagh > Is this something that should be included in Fedora 41 as well? Yes, it should. COSMIC Packages are available in Fedora 41 now, as well as rawhide
I've made the PR for F41: https://src.fedoraproject.org/rpms/fedora-release/pull-request/346
Proposed as a Freeze Exception for 41-final by Fedora user sgallagh using the blocker tracking app because: The new Cosmic desktop will not be able to start its greeter after installation without this patch. It can't easily be rectified after installation, since the user will need to drop to the command-line to explicitly enable cosmic-greeter.service. Updating fedora-release package post-install will not change the disabled state of the greeter without an explicit request by the user, so I think this justifies a freeze exception.
+4 in https://pagure.io/fedora-qa/blocker-review/issue/1698 , marking accepted.
FEDORA-2024-56ea3e1da7 (fedora-release-41-25 and fedora-repos-41-1) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-56ea3e1da7
FEDORA-2024-56ea3e1da7 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-56ea3e1da7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-56ea3e1da7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-56ea3e1da7 (fedora-release-41-25 and fedora-repos-41-1) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.