hyprland doesn't clean up its Wayland sockets after exit

[appsforartists]

Hyprland Version

0.32.3

Bug or Regression?

Bug

Description

Hyprland sets WAYLAND_DISPLAY when it starts up, but doesn't release it when quit. This prevents other sessions (like gamescope) from starting correctly.

On my system, exiting Hyprland leaves me in a loop of this printing to the console:

DEBUG Using pkexec loader
DEBUG Found wayland session

until I hold the power button down long enough for the firmware to kill the OS.

How to reproduce

1. systemctl --user show-environment before starting Hyprland. Observe that WAYLAND_DISPLAY is unset.
2. Start a Hyprland session.
3. hyprctl dispatch exit
4. systemctl --user show-environment Observe that WAYLAND_DISPLAY is still set to wayland-1.
5. Observe that /run/user/1000/wayland-1 still exists (when it should have been cleaned up during exit).

Crash reports, logs, images, videos

No response

[vaxerski]

maybe hyprland crashed? is there a crash report?

[appsforartists]

This happens consistently for me when I try to exit Hyprland, so I don't think it's a crash.

Where would I find a crash report?

[vaxerski]

$XDG_CACHE_HOME/hyprland or ~/.hyprland

[appsforartists]

No such file or directory for both.

[vaxerski]

dam

[thomascft]

I'm having the same issue.

[wvffle]

I can confirm the issue. When hyprctl dispatch exit is run, systemctl --user show-environment still shows WAYLAND_DISPLAY=wayland-1 and there is no crash log.

[thomascft]

Sounds like the issue may be with wlroots itself. Someone reported the same issue with sway here: Jovian-Experiments/Jovian-NixOS#267

[appsforartists]

cc @emersion

[emersion]

wlroots is not involved in the systemd environment stuff.

[vaxerski]

yeah sorry simon idk why they pinged you

[izmyname]

I can confirm the issue. When hyprctl dispatch exit is run, systemctl --user show-environment still shows WAYLAND_DISPLAY=wayland-1 and there is no crash log.

Aquamarine doesn't clean up WAYLAND_DISPLAY, either