"session-5.scope: Stopping timed out. Killing." during shutdown

Everytime I’m trying to shutdown my system I’m always blocked by watchdog for 1:30 minutes.
Those are the last lines of journalctl -eb -1 -p warning:

pipewire[11318]: mod.x11-bell: X11 I/O error handler called on display :0
pipewire[11318]: mod.x11-bell: X11 display (:0) has encountered a fatal I/O error
cupsd[1621]: Notifier for subscription 2510 (dbus://) went away, retrying!
cupsd[1621]: Notifier for subscription 2512 (dbus://) went away, retrying!
org.freedesktop.secrets[11803]: discover_other_daemon: 1
kdeconnectd[11710]: 2025-06-15T23:38:10 default: The Wayland connection broke. Did the Wayland compositor die?
systemd[11135]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
systemd[11135]: app-org.kde.kdeconnect.daemon@autostart.service: Failed with result 'exit-code'.
systemd[11135]: flameshot.service: Failed with result 'exit-code'.
systemd[1]: session-5.scope: Stopping timed out. Killing.
systemd[1]: session-5.scope: Failed with result 'timeout'.
systemd[11135]: ssh-agent.service: Failed with result 'exit-code'.
wireplumber[11325]: pw.core: 0x287b75a0: leaked proxy 0x2899ba20 id:3
wireplumber[11325]: pw.core: 0x287b75a0: leaked proxy 0x28a3c190 id:4
kernel: watchdog: watchdog0: watchdog did not stop!

I was trying to investigate more about those two lines:

systemd[1]: session-5.scope: Stopping timed out. Killing.
systemd[1]: session-5.scope: Failed with result 'timeout'.

and skimmed through this issue: "session-1.scope: Failed with result 'timeout'." · Issue #23501 · systemd/systemd · GitHub.
However I couldn’t find anything useful.

May I ask if anyone has an idea how to fix this?

Ok, after changing priority from warning to info, I’m seeing the following lines:

systemd[1]: session-5.scope: Stopping timed out. Killing.
systemd[1]: session-5.scope: Killing process 11304 (cosmic-settings) with signal SIGKILL.
systemd[1]: session-5.scope: Killing process 11310 (cosmic-settings) with signal SIGKILL.
systemd[1]: session-5.scope: Failed with result 'timeout'.

so it seems to be an issue from cosmic-settings.