Whenever shutting down, logging out, or restarting, there’s a significant 7 or so second delay before any of the three actually happen. My apps close around 4 seconds after clicking one of the three buttons in my application launcher, and then 2-3 seconds later, my desktop executes that. How do I fix this to make it immediately do the respective when selecting one of them in the application launcher? I’m on KDE Plasma running Fedora 44.
open a terminal and run journalctl --no-hostname --no-pager -f within it. It’ll track the end of the system journal.
Do stuff to replicate the issue.
Post whatever gets spewed into the journal when the issue occurs here, as pre-formatted text
like so
This is what it came up with:
May 29 13:35:44 systemd[2080]: Started dbus-:1.2-org.kde.Shutdown@2.service.
May 29 13:35:47 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
May 29 13:35:47 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 29 13:35:47 audit: BPF prog-id=207 op=UNLOAD
May 29 13:35:48 xwaylandvideobridge[29866]: QObject::disconnect: Unexpected nullptr parameter
May 29 13:35:48 flatpak[30406]: console.log: "[Floorp OS] Browser shutdown detected, stopping processes..."
May 29 13:35:48 systemd[2080]: app-org.kde.xwaylandvideobridge@autostart.service: Consumed 241ms CPU time over 28.473s wall clock time, 72.4M memory peak.
May 29 13:35:49 systemd[2080]: app-flatpak-one.ablaze.floorp-3284771777.scope: Consumed 11.175s CPU time over 26.687s wall clock time, 1G memory peak.
May 29 13:35:50 kdeconnectd[29863]: Missing CAP_NET_ADMIN permission. Cannot determine whether a found address is of random or public type.
After the final line, it would ask to shut down the console to fully log out.
That’s from a shutdown command, and it looks pretty normal. You issued the shutdown command and within 4 seconds, after floorp finally closed thanks to being a flatpak app, everything was in a position to permit the full shutdown to complete.
Looks normal to be honest.
With Floorp closed, it still takes 4 or so seconds to shut down my computer (by shut down, I’m referring to it showing the plymouth screen, whilst shutting down, and for logging out, immediately logging out when I click the respective option). Is there any way to make it so it does it immediately?
Not that I’m aware of - all processes have to be signalled to end cleanly (and given time to do so), buffers flushed, logs written, caches written to disk and filesystems sync’d, hardware powered off, and so on.
Quickest way you can shut everything down is to cut the power - it’ll definitely shut down immediately then, but doing so has its downsides.
Hmm, alright. Is there possibly a way to give it the illusion of shutting down? Like for example, it shows some kind of loading screen when clicking on the option to shut down, restart, or log out, while executing what it needs to in the desktop before it actually does the respective.
You COULD tell the kernel to vanish immediately, with a shutdown now command. That should be faster, but any software you have running with open buffers will not get a chance to deal with them.
I don’t know what open buffers means, may you clarify?
You’ve got a process running which editing a file. When the kernel vanishes in a puff of logic, you may well lose data from edit session - it won’t get a chance to write the latest changes to disk… they’re gone.
Of course you might not care, so long as you can shutdown in under a second. Quite why that’s important is beyond me.
A quick shutdown like that is just personally preferable to me. Thanks for the help and information though.
shutdown now for an immediate shutdown.
shutdown -r now for an immediate reboot.
Have at it! 
Open buffers can also include changes to configuration setting and histories, depending on the application. There can be quite long delays writing to a slow device such as a USB key.
There are certain services running that may take a certain amount of time to shutdown cleanly as well. A 4 second delay in shutdown seems quite reasonable to me and is lightning fast compared to some systems.