wayland desktop environment using webtech
Find a file
Stephen Hellings 4fe557c536 fix: register Wayland display/socket fds with calloop to fix DRM rendering stall
The DRM event loop only woke for registered calloop sources (VBlank,
libinput, session). When the VBlank rendering cycle broke (transient
page-flip failure, timing edge), nothing woke the loop to restart it —
only input events (mouse movement) would un-stall rendering.

Three changes:

1. Register the Wayland display poll_fd as a calloop source so client
   surface commits immediately wake the event loop and trigger
   render_frame via the main callback.

2. Register the listening socket fd so new Wayland client connections
   also wake the loop promptly.

3. Add a periodic timer (fires every frame_time ≈ 16ms) as a safety net
   to restart stalled VBlank cycles even with no input or client
   activity.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-03-09 19:24:33 -04:00
electron Cry 2026-03-09 18:07:07 -04:00
packaging/wayland-sessions Initial commit 2026-03-08 23:04:02 -04:00
src fix: register Wayland display/socket fds with calloop to fix DRM rendering stall 2026-03-09 19:24:33 -04:00
.gitignore Initial commit 2026-03-08 23:04:02 -04:00
Cargo.lock Attempt 5... 2026-03-09 15:54:29 -04:00
Cargo.toml Attempt 5... 2026-03-09 15:54:29 -04:00
config.example.toml Attempt 3 to fix launching permission denied 2026-03-09 11:21:08 -04:00
LICENSE Create LICENSE 2026-03-08 23:12:27 -04:00
PKGBUILD Do not use npm for pkg 2026-03-08 23:39:36 -04:00
README.md Initial commit 2026-03-08 23:04:02 -04:00
whatever.txt Attempt 5... 2026-03-09 15:54:29 -04:00

wo compositor

don't bother (woe)