search

hyprwm / hyprland-wiki

The Hyprland Wiki Pages, automatically synced with the website.
BSD 3-Clause "New" or "Revised" License
251 stars 383 forks source link

Clarify exit command variants #868

Closed Vladimir-csp closed 1 week ago

Vladimir-csp commented 1 week ago

Resort to terminate-user only in case of problems with less blanket options.

Ghosthree3 commented 1 week ago

Typo, boud.

How does uwsm stop compare with loginctl terminate-session "$XDG_SESSION_ID"? Will it kill all active graphical session units (ie. if I issue it in tty2 it will kill the tty1 Hyprland instance as well)? The description on the project page is unclear as to the scope of its effect, but given that the followup option wildcard stops all wayland-wm@* services and says it is effectively the same as uwsm stop I'm assuming it does.

The reason I bring this up is because I think it is unintuitive to the user that issuing an exit command in Hyprland will in fact kill all existing Hyprland (or Wayland) sessions.

Vladimir-csp commented 1 week ago

Systemd-managed system assumes there is only one graphical session per user. UWSM operates in this paradigm, you will not be able to launch more than one wayland-wm@.service.

uwsm stop, systemctl --user stop wayland-wm@.service, systemctl --user start wayland-session-shutdown.target are qeuivalent.

loginctl terminate-session "$XDG_SESSION_ID" produces the same result if login session is bound to graphical session.

Ghosthree3 commented 1 week ago

That makes sense, thank you. I suppose additional instances will just have to be started the traditional way, without uwsm.