You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Multiple wl_seat globals: hyprtoolkit binds the last seat, so hyprland-dialog ignores the real mouse #146
CWaylandPlatform's registry handler (src/core/platforms/WaylandPlatform.cpp, the wl_seat branch) rebinds m_waylandState.seat for everywl_seat global and releases the previous one. When the compositor advertises more than one seat, hyprtoolkit apps end up on whichever seat came last.
With a Hyprland plugin that adds two extra seats (for background automation input), hyprland-dialog — and so Hyprland's "Application Not Responding" dialog — attaches pointer and keyboard to the last extra seat. Real mouse clicks on the compositor's own seat never reach it; Terminate/Wait do nothing.
Suggested fix (tested on Hyprland 0.56.2 / hyprland-guiutils 0.2.2 via LD_LIBRARY_PATH; the dialog then binds wl_seat#4.name("Hyprland")):
- if (NAME == "wl_seat") {+ if (NAME == "wl_seat" && !m_waylandState.seat) {+ // Bind only the first seat. Rebinding on every wl_seat global would leave us on+ // whichever seat the compositor advertised last, which may not carry the user's input.
Single-seat sessions are unaffected. (A PR was auto-closed as I'm not vouched: #145.)
Opened #159 with @andyhennie's fix (their commit, authorship kept). Confirmed the mechanism in WaylandPlatform.cpp:61 (the bind overwrites m_waylandState.seat on every wl_seat global) and that single-seat is unaffected; multi-seat is their reproduced case.
Activity
UncleJ4ck commentedon Nov 9, 2026
Opened #159 with @andyhennie's fix (their commit, authorship kept). Confirmed the mechanism in
WaylandPlatform.cpp:61(the bind overwritesm_waylandState.seaton everywl_seatglobal) and that single-seat is unaffected; multi-seat is their reproduced case.