You are not logged in.
Pages: 1
Hello all,
sometimes the Q4OS system requires many seconds to completely shutdown due to some user@1000.service!
Is this normal?
Giannis
Offline
No it's not normal. How many seconds ?
Offline
No it's not normal. How many seconds ?
90 seconds
Offline
This problem occurs in my desktop running X11. This is not present in my Tuxedo Pulse that runs wayland
Offline
AI says, and it's consistent with what we assume:
Systemd is trying to stop the user session for UID 1000 (usually the first normal user) and something in that user session is hanging during logout/shutdown.
What’s usually causing it, most common culprits:
- A stuck user process (browser, Electron app, VS Code, Java, Python, etc.)
- A systemd user service that doesn’t exit cleanly
- FUSE mounts (sshfs, rclone, gvfs)
- Lingering user services still running after logout
- Flatpak / Snap apps misbehaving
Systemd waits (default ~90s), then complains.
Quick ways to diagnose
See what’s still running for that user
$ loginctl user-status 1000
This usually points straight at the offender.
Check failed user services
$ systemctl --user list-units --failed
Or logs:
$ journalctl --user -xe
Offline
here is the output for loginctl:
and here for systemctl
Offline
Pages: 1