Description of problem: On the login screen, if I select "Restart.." or "Power Off..." nothing happens. Version-Release number of selected component (if applicable): gdm-41~alpha-2.fc35.x86_64 gnome-shell-41~beta-1.fc35.x86_64 How reproducible: Always Steps to Reproduce: 1. Start the computer 2. At the login screen select top right actions menu 3. Select "Power Off/Log Out" -> "Restart..." Actual results: Nothing happens. Expected results: The computer shoult reboot or power off. Additional info: This line appears in the logs as soon as I click on one of those actions (Restart/PowerOff): Aug 24 10:02:29 tosh gnome-shell[4049]: Ignored exception from dbus method: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Proposed as a Blocker for 35-beta by Fedora user alciregi using the blocker tracking app because: Shutting down, rebooting, logging in and logging out must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops.
*** Bug 2001398 has been marked as a duplicate of this bug. ***
Updating component and upstream link from the dupe. Taking votes from the dupe at https://pagure.io/fedora-qa/blocker-review/issue/435 , +3, so marking accepted.
Upstream closed gnomeshell#4599 and referenced gdm#725, changing component to reflect.
Yeah, just checked that it still occurs in the last workstation build: Fedora-Workstation-Live-x86_64-35-20210906.n.0.iso
oh, has anyone checked if it's still the case with SELinux in permissive mode (boot with enforcing=0 or run `setenforce Permissive`)?
I just did, and yes, it still happens. So doesn't look like this is SELinux-related. Can reproduce the bug with SELinux in both enforcing and permissive mode.
Ben Cotton asked me to take a look at this. I'm doing a gnome-shell build now that I think should fix the problem. Unfortunately, I'm a little time crunched today with a RHEL blocker, so I'd appreciate if someone else could test and confirm that it works.
(In reply to Ray Strode [halfline] from comment #8) > Ben Cotton asked me to take a look at this. I'm doing a gnome-shell build > now that I think should fix the problem. This one? https://koji.fedoraproject.org/koji/buildinfo?buildID=1831567
❯ rpm -qa gnome-shell gnome-shell-41~rc.1-2.fc35.x86_64 I verified the fix, after installing the koji task, I am able to restart and shutdown from the login screen
Fix works for me, too. Slightly slower to respond than I'd expect, but that may just be my VM. In any case, I'd say the blocking behavior is resolved.
(In reply to Ben Cotton from comment #11) > Fix works for me, too. Slightly slower to respond than I'd expect, but that > may just be my VM. In any case, I'd say the blocking behavior is resolved. Works for me. I spotted a little delay too, and I'm on bare metal.
FEDORA-2021-d0b0be7c4e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d0b0be7c4e
with the fix https://bodhi.fedoraproject.org/updates/FEDORA-2021-d0b0be7c4e (gnome-shell-41~rc.1-2.fc35) now I can succesfully shutdown or reboot form the login screen.
tested on a UEFI VM (kvm virt-manager)
FEDORA-2021-d0b0be7c4e has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d0b0be7c4e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d0b0be7c4e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I can confirm that this update fixes the issue for me and you can initiate the poweroff or reboot process from the login screen.
Hi, we forgot to push this to rawhide. It will be back for F36 if we aren't careful!
So, update is now UNPUSHED...
yes, for reasons I explained in it. I'm working on sorting that out.
FEDORA-2021-d0b0be7c4e has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.