lkn
/
windowmaker-wl
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

xwayland: eager mode (start at init, not on first X11 client) — eliminates 3-5s lag

This commit is contained in:
Ollie 2026-05-28 22:43:39 +02:00
parent a721f1333a
commit 0642bcb92c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/backend/wayland/wl_backend.c
View File

@ -3111,7 +3111,7 @@ wl_display_open(const char *name)
* renders through XWayland, making the WM visible on-screen.
* The ready signal fires once Xwayland's socket accepts connections. */
wl_state.xwayland = wlr_xwayland_create(wl_state.display,
wl_state.compositor, true);
wl_state.compositor, false);
if (wl_state.xwayland) {
/* Wire server destroy signal to detect early failure (e.g. stale
* display lock → Xwayland exits before ready fires). */
@ -3205,7 +3205,7 @@ wl_display_open(const char *name)
* No need to wait for it at startup. Mark as ready so the rest of
* init proceeds without blocking. */
if (wl_state.xwayland) {
wwarning("wl_backend: XWayland configured (lazy mode) — starts on first X11 client");
wwarning("wl_backend: XWayland configured (eager mode) — ready at startup");
wl_state.xwayland_ready = true;
if (wl_state.x_display) {
wwarning("wl_backend: XWayland bridge ready — Display*=%p, full WM UI enabled",