When Steam is running, it stalls shutdown of my system by a minute

Ask Fedora
, ,
1

I have this problem since upgrading to F44 but I am not entirely sure why it would be related to F44. Maybe I got the new containerized Steam runtime in the same timeframe?

Anyway my problem is that if I have Steam running and want to shut down my system, it stalls the shutdown process by about a minute compared to when I shut down with Steam not running.

I ran journalctl -b-1 -e after a reboot and I am getting these log entries:

May 14 11:02:37 fedora systemd[2082]: beszel-agent.service: Killing process 12482 (catatonit) with signal SIGKILL.
May 14 11:02:38 fedora systemd[2082]: Stopped plasma-kwin_wayland.service - KDE Wayland Compositor.
May 14 11:02:38 fedora systemd[2082]: plasma-kwin_wayland.service: Consumed 19.637s CPU time over 8min 18.776s wall clock time, 133.8M memory peak.
May 14 11:02:38 fedora systemd[2082]: Requested transaction contradicts existing jobs: Transaction for podman-pause-9f3a7732.scope/start is destructive (systemd-exit.service has 'start' job queued, but 'stop' is included in transaction).
May 14 11:02:38 fedora systemd[2082]: Requested transaction contradicts existing jobs: Transaction for podman-pause-c19e569c.scope/start is destructive (exit.target has 'start' job queued, but 'stop' is included in transaction).
May 14 11:02:38 fedora systemd[2082]: Requested transaction contradicts existing jobs: Transaction for podman-pause-40259159.scope/start is destructive (systemd-exit.service has 'start' job queued, but 'stop' is included in transaction).
May 14 11:02:38 fedora systemd[2082]: Requested transaction contradicts existing jobs: Transaction for podman-pause-ae158908.scope/start is destructive (systemd-exit.service has 'start' job queued, but 'stop' is included in transaction).
May 14 11:02:38 fedora systemd[2082]: Requested transaction contradicts existing jobs: Transaction for podman-pause-8963843f.scope/start is destructive (systemd-exit.service has 'start' job queued, but 'stop' is included in transaction).
May 14 11:02:38 fedora systemd[2082]: Requested transaction contradicts existing jobs: Transaction for podman-pause-8080c6d8.scope/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 14 11:02:38 fedora systemd[2082]: Requested transaction contradicts existing jobs: Transaction for podman-pause-2712cba0.scope/start is destructive (systemd-exit.service has 'start' job queued, but 'stop' is included in transaction).
May 14 11:02:38 fedora systemd[2082]: Requested transaction contradicts existing jobs: Transaction for podman-pause-a3255a15.scope/start is destructive (exit.target has 'start' job queued, but 'stop' is included in transaction).
May 14 11:02:38 fedora systemd[2082]: Requested transaction contradicts existing jobs: Transaction for podman-pause-4e00bf7d.scope/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 14 11:02:38 fedora systemd[2082]: Requested transaction contradicts existing jobs: Transaction for podman-pause-3e16e65d.scope/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
May 14 11:02:38 fedora beszel-agent[12544]: time="2026-05-14T11:02:38+02:00" level=warning msg="Failed to add pause process to systemd sandbox cgroup: Transaction for podman-pause-3e16e65d.scope/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction)."
May 14 11:02:38 fedora systemd[2082]: beszel-agent.service: Killing process 12566 (catatonit) with signal SIGKILL.
May 14 11:02:38 fedora systemd[2082]: Stopped beszel-agent.service - Beszel Agent Container.
May 14 11:02:38 fedora systemd[2082]: beszel-agent.service: Consumed 872ms CPU time over 10min 38.403s wall clock time, 70.8M memory peak.
May 14 11:02:38 fedora systemd[2082]: Stopped podman-user-wait-network-online.service - Wait for system level network-online.target as user..
May 14 11:03:22 fedora systemd[2082]: app-steam@6442055df4144b15be1759e02a788d4a.service: State 'stop-sigterm' timed out. Aborting.
May 14 11:03:22 fedora systemd[2082]: app-steam@6442055df4144b15be1759e02a788d4a.service: Killing process 4889 (steam) with signal SIGABRT.
May 14 11:03:23 fedora audit[4889]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=4889 comm="steam" exe="/home/corvidad/.local/share/Steam/ubuntu12_32/steam" sig=6 res=1
May 14 11:03:23 fedora crash_20260514110322_37.dmp[12587]: Uploading dump (out-of-process)
                                                           /tmp/dumps/crash_20260514110322_37.dmp
May 14 11:03:23 fedora systemd-coredump[12588]: Process 4889 (steam) of user 1000 terminated abnormally with signal 6/ABRT, processing...
May 14 11:03:23 fedora crash_20260514110322_37.dmp[12587]: Finished uploading minidump (out-of-process): success = no
May 14 11:03:23 fedora crash_20260514110322_37.dmp[12587]: error: Peer certificate cannot be authenticated with given CA certificates
May 14 11:03:23 fedora crash_20260514110322_37.dmp[12587]: file ''/tmp/dumps/crash_20260514110322_37.dmp'', upload no: ''Peer certificate cannot be authenticated with given CA certificates''
May 14 11:03:23 fedora systemd[2082]: app-steam@6442055df4144b15be1759e02a788d4a.service: Failed with result 'timeout'.
May 14 11:03:23 fedora systemd[2082]: Stopped app-steam@6442055df4144b15be1759e02a788d4a.service - Steam.
May 14 11:03:23 fedora systemd[2082]: app-steam@6442055df4144b15be1759e02a788d4a.service: Consumed 1min 7.076s CPU time over 8min 23.925s wall clock time, 6.3G memory peak.
May 14 11:03:23 fedora systemd[2082]: Stopped target basic.target - Basic System.
May 14 11:03:23 fedora systemd[2082]: Stopped target paths.target - Paths.
May 14 11:03:23 fedora systemd[2082]: Stopped drkonqi-sentry-postman.path - Submitting pending crash events (file monitor).
May 14 11:03:23 fedora systemd[2082]: Stopped target sockets.target - Sockets.
May 14 11:03:23 fedora systemd[2082]: Stopped target timers.target - Timers.
May 14 11:03:23 fedora systemd[2082]: Stopped drkonqi-coredump-cleanup.timer - Cleanup lingering KCrash metadata.
May 14 11:03:23 fedora systemd[2082]: Stopped grub-boot-success.timer - Mark boot as successful after the user session has run 2 minutes.

So that difference between 11:02:38 and 11:03:22 roughly would match the prolonged time it takes for the system to shutdown. Sometimes it’s a bit longer, but that happens when the system is running for a long time with Steam also running for most of said runtime.

Sadly because of that CA Cert error I can’t see what’s in that mini dump file.

Does anyone know a way to resolve that?

2

I use the steam rpm from rpmfusion and I am not seeing a delay on shutdown.
I don’t think steam delays shutdown deliberately, say to do a cloud save.
Are you using the rpm or flatpak?

3

If you use the quit menu for steam does it also take a minute to stop?

4

I am on the RPM version.

When I start my system from a cold boot, run steam I have the delay.

When I do the same without starting steam, instant shut down.

Visually it does not seem like it, when I select quit in steam it takes roughly 5 seconds for the main window and the notification icon to disappear.

5

I figured it out. I totally forgot that I tested Millenium for Steam about two weeks ago and just forgot to remove the base install files again, I had only removed all themes I tested.

As soon as I removed them, my system shut down the same way as before. So I assume some process there is hindering steam to shutdown normally when triggered through a shut down.