config: add option to enable/disable xwayland

[Trimutex]

Describe your PR, what does it fix/add?

Allows enabling and disabling XWayland during runtime. #3371 appears to be stale and not being worked on.

Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)

1. Disables "DISPLAY" env variable to prevent X11 launches. Due to this, a pop up will occur notifying of this. Is this to be left alone or is there a better way of informing the user that XWayland is not enabled?
2. While it closes the windows, applications like Steam are still running in the background with a tray icon. Is it possible to close these or just ignore them?

Is it ready for merging, or does it need work?

Current state of commit works, but see above for things I would like to address first. Closes #7607

[vaxerski]

will this work at runtime? e.g. if someone enables it while running hl

[vaxerski]

if yes it'd be nice to also do xwaylanf restore while we at it (restart if crash)

[Trimutex]

will this work at runtime? e.g. if someone enables it while running hl

Yeah, the option is meant to work while Hyprland is running and I want to keep it that way

if yes it'd be nice to also do xwaylanf restore while we at it (restart if crash)

calling g_pXWayland->reset(), or resetting is members (pServer, pWM) crashes it when disabling due to lingering apps, probably due to the same issue as 2 above

[Trimutex]

Unless there is some way to simply test if it crashed that I'm unaware of? That would just be oversight from my part if there's a good way for that

[vaxerski]

I think if the wm is yeeten off then it crashed or died

[Trimutex]

Update note: This PR currently only prevents creation of new XWayland windows by unsetting the env variable. I'll continue to dig deeper on actually shutting down XWayland and applications with it off.

[Trimutex]

Few bugs but currently handles turning off/on multiple times just fine

Current Bugs

• Steam stays alive after closing its windows and can only exit if XWayland is re-enabled (not sure if fixable)
• Possibly taking another window with it when disabling (seems to be if previous window was X11?)

[Trimutex]

@vaxerski Should be all good now for merge.

Leaving steam issue alone as I don't think its an XWayland problem, just would require keeping track of PIDs and killing them. That might be leaking into territory better made for another PR.

Additional mention as you asked about it that XWayland should fully restore on re-enable. I can't test that for sure though as I don't have a reliable way of crashing it in such a way that it can't restart.

[Trimutex]

Managed to crash XWayland and can confirm this restores successfully!

[vaxerski]

sankyu!