Fedora 43 Workstation won't shut down if "apply pending updates" is selected

Ask Fedora
,
1

In a freshly installed instance of F43 Workstation, trying to power off when there are pending updates will, as expected, show the tick box to “apply pending updates” or whatever the exact phrasing is. Ticking the box and then pressing the button to power off leads to nothing happening, and simply drops me back to the desktop. Going back to the menu and pressing power off again now powers off immediately without showing the usual popup. No updates are applied, and instead the computer powers off completely instead of rebooting into the offline update environment. At next boot, updates are applied offline in the usual way, but now the computer powers off again instead of rebooting.

What I would expect to happen (and the way that it worked up to and including F42) is that ticking the box and powering off will not return to the desktop, but will reboot into the offline update environment right away, and the computer powers off after the updates have been applied.

I don’t know which component is responsible for all of this so I don’t know where to write a bug report or what logs to collect. If anyone can advise on that, that’d be great.

4 Likes
2

I’m experiencing the same issue. Fedora 43 Workstation: "Install pending updates" checkbox not working properly on Gnome's "Power Off..." dialog

1 Like
3

I have exactly the same issue. I reverted to 42 as there was no discussion about this issue, so I lost faith that it was being addressed.

4

This is definitely an issue. I haven’t seen it mentioned in Ask Fedora > Common Issues , so it’s worth filing it as a bug.

5

I’d be happy to if I knew the name of the component that is responsible. My guess is gnome-packagekit or gnome-software.

6

We don’t know yet. I’m guessing something regressed in either systemd or gnome-session. Breaking changes in GNOME Software or PackageKit is less likely.

2 Likes
7

A post was split to a new topic: Running and testing different desktop environments

8

I’m afraid you posted your request in the wrong topic.

9

Which topic should I post in? It’s not clear to me how all those topics are organized…

10

You can create a new topic in the “Ask Fedora” section for your question.

1 Like
12

@estaats or @mattipulkkinen: @shaundesignsgames reported that the issue has been fixed, are you still able to reproduce?

13

Sorry, It’s not fixed for me. It’s fixed if restarting with pending updates. But not fixed for a full shutdown.

14

I’m having the same problem.

15

Currently having the same issue here.

Found the service “gnome-session-manager@.service” throwing these errors.

Nov 08 09:51:38 fedora.fritz.box ir.imansalmani.IPlan.desktop[25685]: Fehler: app/ir.imansalmani.IPlan/x86_64/master ist nicht installiert
Nov 08 09:51:38 fedora.fritz.box gnome-session-service[25488]: Could not create transient scope for PID 25685: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No suc>
Nov 08 09:51:38 fedora.fritz.box gnome-session-service[25488]: Could not create transient scope for PID 25698: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No suc>
Nov 08 09:51:38 fedora.fritz.box gnome-session-service[25488]: Could not create transient scope for PID 25770: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No suc>
Nov 08 09:53:24 fedora.fritz.box gnome-session-service[25488]: GsmManager: Shell confirmed unexpected logout type

It works when pressing the shutdown button again.
Also it opens the shutdown window again if i open a file via gedit.
Normal shutdown if no offline updates where downloaded works perfect and doesn’t throw these error lines.

Issue only appered when upgrading from 42 to 43.
Same issue cannot be spotted on my KDE Workstation.

I did install no extra packages except wine after needing to uninstall and after the reboot to reinstall them.

16

Possible fixed with the new akmods package. See the bugzilla ticket DNF5 offline upgrade hangs indefinitely when akmods fails and holds systemd inhibitor lock

17

Same issue even after updating the akmods to newest version

Nov 08 23:56:28 fedora.fritz.box gnome-session-service[3698]: App gnome-keyring-secrets.desktop sets X-GNOME-Autostart-Phase, but gnome-session no longer manages session services
Nov 08 23:56:28 fedora.fritz.box gnome-session-service[3698]: App gnome-keyring-ssh.desktop sets X-GNOME-Autostart-Phase, but gnome-session no longer manages session services
Nov 08 23:56:28 fedora.fritz.box gnome-session-service[3698]: App spice-vdagent.desktop sets X-GNOME-Autostart-Phase, but gnome-session no longer manages session services
Nov 08 23:56:28 fedora.fritz.box systemd[3482]: Started gnome-session-manager@gnome.service - GNOME Session Manager (session: gnome).
Nov 08 23:56:30 fedora.fritz.box gnome-session-service[3698]: Entering running state
Nov 08 23:56:30 fedora.fritz.box vmware-user.desktop[4005]: vmware-user: could not open /proc/fs/vmblock/dev
Nov 08 23:56:30 fedora.fritz.box gnome-session-service[3698]: Could not create transient scope for PID 3946: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such >
Nov 08 23:56:30 fedora.fritz.box gnome-session-service[3698]: Could not create transient scope for PID 3982: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such >
Nov 08 23:56:30 fedora.fritz.box gnome-session-service[3698]: Could not create transient scope for PID 4002: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such >
Nov 08 23:59:16 fedora.fritz.box gnome-session-service[3698]: GsmManager: Shell confirmed unexpected logout type

Running 0.6.2-3.fc43.noarch

18

Um… I know many people have already said this… but… Same issue for me (alla packages are up to date).