multi monitor follow_mouse=2 focus issues #8861
Comments
|
issue seems to be caused by mishandling of multiple exclusive layers |
|
as an extensive user of follow mouse 2 also, I can confirm the issues which snowman is experiencing. Having two foot terms open on one monitor, and opening slurp and dragging from the focused window to the other one, causes focus to return back to the original window (focused border colour is displayed) but the window doesn't act like it, it receives no keyboard input. There have also been times (that I don't have exact repro steps for sadly) where my focused workspace can be on one monitor with the focused window on the other. afaik, this should not happen, it shouldn't be possible for the active workspace to be different to the one the active window is on (or at least it isn't intuitive for this to be the case) |
|
I'm facing this issue with a single monitor. I suspect it's because I'm running Xfce panel 4.20, whose Wayland support is new and experimental. The panel opens as a top layer with other plugins that have their own layers (such as the Whisker menu, which runs as an overlay layer). |
Already reported ? *
Regression?
No
System Info and Version
e75e2cd
Description
Focused window gets into a state where it can't receive keyboard input without changing focus to another window and back to it (same state as #6929)
Could be related to another issue where same state happens after unlocking
How to reproduce
Put 1 window in each monitor (I used foot)
Open slurp and start and end selection on the window that is not focused (other monitor)
Focus will be back to the original window but keyboard will not work
Crash reports, logs, images, videos
Example Config
input { follow_mouse = 2 } $mainMod = ALT bind = $mainMod, Q, exec, foot bind = $mainMod, C, killactive, bind = $mainMod, left, movefocus, l bind = $mainMod, right, movefocus, r bind = $mainMod, up, movefocus, u bind = $mainMod, down, movefocus, d bind = $mainMod SHIFT, left, movewindow, l bind = $mainMod SHIFT, right, movewindow, r bind = $mainMod SHIFT, up, movewindow, u bind = $mainMod SHIFT, down, movewindow, d bind = $mainMod, 1, workspace, 1 bind = $mainMod, 2, workspace, 2 bind = $mainMod, 3, workspace, 3 bind = $mainMod, 4, workspace, 4 bind = $mainMod, 5, workspace, 5 bind = $mainMod, 6, workspace, 6 bind = $mainMod, 7, workspace, 7 bind = $mainMod, 8, workspace, 8 bind = $mainMod, 9, workspace, 9 bind = $mainMod, 0, workspace, 10 bind = $mainMod SHIFT, 1, movetoworkspace, 1 bind = $mainMod SHIFT, 2, movetoworkspace, 2 bind = $mainMod SHIFT, 3, movetoworkspace, 3 bind = $mainMod SHIFT, 4, movetoworkspace, 4 bind = $mainMod SHIFT, 5, movetoworkspace, 5 bind = $mainMod SHIFT, 6, movetoworkspace, 6 bind = $mainMod SHIFT, 7, movetoworkspace, 7 bind = $mainMod SHIFT, 8, movetoworkspace, 8 bind = $mainMod SHIFT, 9, movetoworkspace, 9 bind = $mainMod SHIFT, 0, movetoworkspace, 10 bindm = $mainMod, mouse:272, movewindow bindm = $mainMod, mouse:273, resizewindow debug { enable_stdout_logs = true }The text was updated successfully, but these errors were encountered: