fix persistent logout issue with sddm

[nuknes]

What would you like to be added?

issue is that the sddm tty handover fails when asked nicely resulting in a black screen with blinking cursor

loginctl terminate-session $XDG_SESSION_ID

loginctl terminate-user $(whoami)

loginctl terminate-user ""

uwsm stop

and (for some users) even hyprctl dispatch exit doesn't work

only the sledgehammer pkill -KILL -u $(whoami) works because it forces the session to terminate from the outside

but there's now

https://github.com/hyprwm/hyprshutdown

a new graceful execution orchestrator for the Hyprland exit process, might finally ensure a clean logout with sddm

interesting forkoff() function in case any remaining stubborn processes still not gracefully shutting down politely we can add a "--post-cmd" flag so the detached hyprshutdown process still brings out the hammer and executes the final bash -c 'pkill -KILL -u $(whoami)'

hyprshutdown isn't available in the AUR yet but you can try it by installing manually and assuming that you have a working hyprland installation with all dependencies (hyprlang, hyprutils, etc.)

now in the AUR, so just

yay -S hyprshutdown-git

or manual install if you prefer

sudo pacman -S --needed git base-devel
git clone https://github.com/hyprwm/hyprshutdown.git
cd hyprshutdown
cmake --no-warn-deprecated ..
make
sudo cp hyprshutdown /usr/local/bin/

then edit ~/.config/caelestia/shell.json

"logout": ["hyprshutdown", "--post-cmd", "bash -c 'pkill -KILL -u $(whoami)'"],

How will it help?

should fix the persistent logout issue with sddm where you logout to a black screen with blinking cursor

this two stage approach, a graceful app termination followed by a guaranteed, hard session kill from a detached process is the most reliable way to force a clean tty handover

if you've tried it and it solves your logout issue please comment

hopefully it works for everyone and when hyprshutdown is finalized and available I'll open a PR to add a dependency and update the example config.json

#936

#816

#711

#303

#250

[soramanew]

hyprshutdown just uses hyprctl dispatch exit in the backend

[nuknes]

hyprshutdown just uses hyprctl dispatch exit in the backend

yea it runs the IPC equivalent to that to shut down the compositor

but for those that find that even hyprctl dispatch exit doesn't work at least this first attempts app cleanups gracefully (IPC/SIGTERM) then only detaches forkoff() + --post-cmd to a final brute force pkill

my rationale behind using hyprshutdown this way as the example in config.json is that it should work for almost everyone "out of the box" especially sddm users and we'd see less of the black screen logout bug issues?

[dark3txr]

I think "loginctl kill-session" or "loginctl kill-user" and "pkill -TERM" work ok with sddm

[Markus328]

The loginctl terminate command worked with me until I started to use uwsm (required for convenience to me). Now only using hyprctl dispatch exit works properly

[nuknes]

The loginctl terminate command worked with me until I started to use uwsm (required for convenience to me). Now only using hyprctl dispatch exit works properly

mirrors my own experience, had to use hyprctl dispatch exit after switching to uwsm managed hyprland, then a few days ago (interestingly after my reply to #936) updated one of my laptops and it black screened even with that command

only thing different with that old laptop being an nvidia optimus hybrid. haven't dug into it

[nuknes]

I think "loginctl kill-session" or "loginctl kill-user" and "pkill -TERM" work ok with sddm

loginctl kill-session and pkill -TERM are both SIGTERM like loginctl terminate-user and hyprctl dispatch exit and they all rely on a graceful shutdown chain that is somehow broken in certain setups so failing to cleanly complete the tty handover

haven't tried loginctl kill-user might work but it's still part of the signaling chain involving logind failing that's why pkill -KILL -u $(whoami) bypassing logind is the only thing that works for some users

[yuisa-ortega]

this has been annoying me for a bit, but it worked for me thank youuu

[Kyder]

Loginctl seems to still have theese issues. So using hyprshutdowns works way better.

Thanks for it, it just works. I was little bit confused what is config.json but i figured out it is shell.json

and i made session section to look like this.

  "session": {
    "enabled": true,
    "dragThreshold": 30,
    "vimKeybinds": false,
    "commands": {
      "logout": [
        "hyprshutdown",
        "--post-cmd",
        "bash -c 'pkill -KILL -u $(whoami)'"
      ],

Also modified in similiar way Launcher section but that probably does nothing.

[nuknes]

Loginctl seems to still have theese issues. So using hyprshutdowns works way better.

Thanks for it, it just works.

I was little bit confused what is config.json but i figured out it is shell.json

@Kyder
oops. brain fart haha glad you caught it.