45 second timeout at shutdown

Yes. Manually or via a drop-in..

The ‘drop-in’ (bit more resistant to package updates):
sudo mkdir -p /etc/systemd/user.conf.d
sudo sh -c ‘printf “[Manager]\nDefaultTimeoutStopSec=10s\n” > /etc/systemd/user.conf.d/timeout.conf’
sudo systemctl daemon-reexec

I’m offered 2 versions of Bottles - the Fedora repo version and a Flatpak version. I’m running the Flatpak version. I don’t know how to see whether it’s the user or system version. I remember there being three in some earlier install of Fedora. I’m running the version I’m running because the other version doesn’t work on my system. I have to try my way every time I reinstall Fedora.

I created the user.con manually in /etc/systemd with those contents under [Manager] . The timeout is still 45s. I’ve rebooted 3 times with these settings.

Check for typo “I created the user.con manually”, ‘con’ should be .conf

Check what you have: ls -l /etc/systemd/user.con*

If so, rename: sudo mv /etc/systemd/user.con /etc/systemd/user.conf

Verify: cat /etc/systemd/user.conf

Output should be:
[Manager]
DefaultTimeoutStopSec=10s

Reload and Reboot:
sudo systemctl daemon-reexec

Confirm:
systemctl --user show -p DefaultTimeoutStopSec

Should report DefaultTimeoutStopSec=10s (shown as 10000000 microseconds). If it still says 45s after the rename and a reboot we have to dig further…

No, that did it. The filename had been wrong. The timeout is now 10 seconds. Way more acceptable. I take it it will also catch other such events where a service hangs.

Thanks for staying around getting somewhere with this.

And then I haven’t even mentioned the real trouble hanging at reboots this F44 has.

flatpak list  #last column tells you system or user.
# to install a different one use "flatpak install --user/--system PackageName"

OK so I have the system version of the Bottles software. And others are not available in Discover.

“flatpak install --user usebottles.bottles” finds nothing (corresponding with Discover) and

“flatpak install --system usebottles.bottles” finds the existing installation.

It starts to disturb my way to support here, the fact that we do have two editions (KDE & Gnome) which are not acting the same way. I hope that the FPL @jspaleta gets aware of this and helps looking into it.

The F44 Workstation shows the two Flatpak version (system/user) and also the RPM version.

If Discover is not able to display the same as the Software app, we definitively need some cli scripts which we can use to compare and start to fix this inequality.

@unraid you might also have to look into flatpak --help and check the syntax as I not tested my commands. My workflow is the gnome way, and since few weeks I post screenshots to prove that there are not the same outputs in Discover and Gnome Software.

@ngompa can we get some cli tooling/helper scripts to be able to help independent on which DE/edition we are working?!

Well, thanks for all your assistance it’s greatly appreciated. I did get a viable solution out of the thread by shortening the time Fedora waits to 10s.