The symptom: the mouse becomes somewhat unresponsive. The cursor still moves. If you have a window focused, it still receives keystrokes and can launch other things. But the window manager (fvwm3) doesn't seem to be aware of what the mouse is doing; it won't pop up menus or do the "focus follows mouse" behaviour it normally does.
You can sometimes restore responsiveness by killing one of the Fvwm modules (FvwmButtons, FvwmIconMan), or getting the window that has focus to close. These tend to be sort of chicken-egg since the issue appears a few seconds after login so you don't necessarily have an xterm launched and receiving focus.
You can also get control back reliably by switching out of the current VT and back (Control-Alt-F1/Control-Alt-F7)
It mostly happens shortly after the first login on a fresh boot. (Log out and back in and it doesn't trigger). I think there have been a few times it happened in other scenarios.
It seems to happen on both Devuan Excalibur and Void (current). The impacted machine is a home-built desktop with a Radeon 6900XT and two monitors (one 1440p/120Hz, one 4k xrandr'd-down to 1440p/60Hz) and two trackballs.
I don't think it happens on my other machine (a Thinkpad L13 Gen3 running Devuan Excalibur, with just the one 1200p touchscreen, Trackpoint and touchpad) but its config is different in a few ways (not loading some items I don't use there), so there's not an obvious single differentiator.
I think I also saw some similar weirdness in Fluxbox; the menu would come up but wouldn't acknowledge clicks on items. In that case, I was able to navigate the menu with keystrokes to restart the window manager and regain control.
HakFoo in techsupport @lemmy.world
X11 mouse "partial dropout".
The symptom: the mouse becomes somewhat unresponsive. The cursor still moves. If you have a window focused, it still receives keystrokes and can launch other things. But the window manager (fvwm3) doesn't seem to be aware of what the mouse is doing; it won't pop up menus or do the "focus follows mouse" behaviour it normally does.
You can sometimes restore responsiveness by killing one of the Fvwm modules (FvwmButtons, FvwmIconMan), or getting the window that has focus to close. These tend to be sort of chicken-egg since the issue appears a few seconds after login so you don't necessarily have an xterm launched and receiving focus.
You can also get control back reliably by switching out of the current VT and back (Control-Alt-F1/Control-Alt-F7)
It mostly happens shortly after the first login on a fresh boot. (Log out and back in and it doesn't trigger). I think there have been a few times it happened in other scenarios.
It seems to happen on both Devuan Excalibur and Void (current). The impacted machine is a home-built desktop with a Radeon 6900XT and two monitors (one 1440p/120Hz, one 4k xrandr'd-down to 1440p/60Hz) and two trackballs.
I don't think it happens on my other machine (a Thinkpad L13 Gen3 running Devuan Excalibur, with just the one 1200p touchscreen, Trackpoint and touchpad) but its config is different in a few ways (not loading some items I don't use there), so there's not an obvious single differentiator.
I think I also saw some similar weirdness in Fluxbox; the menu would come up but wouldn't acknowledge clicks on items. In that case, I was able to navigate the menu with keystrokes to restart the window manager and regain control.
I don't see anything obvious in dmesg, either.