-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mouse wheel lockup #4
Comments
I notice it too and I have a hard time troubleshooting this random lockup, |
Edit: tested running 'xinput test-xi2 --root' ..and after some provoking scrolling both: EVENT type 16 (RawButtonRelease) EVENT type 15 (RawButtonPress) stop responding until keypress |
Last comment on this issue; ..and it only triggers for me on a display resolution above 1920x1080 with same config files and so on (tested on two separate pc 4K vs HD). Edit: only difference between these systems are on EDIT: it's started to act up on the other pc as well, so monitor size or the input drivers are not the issue. |
i also experiences this but not with Firefox, only with vivaldi, and it appears to have gotten worse since my last system update which did not include pekwm 0.18, but i do run 0.18 compiled from git since 2020-11-24 and i cannot recreate the error on MATE. i think it might be related to Chromium's BrowserView since i can replicate the issue in Slack as well.. |
@pekdon while testing out branch zombie-14, any recommend tool I should use to trace this issue as well? |
To be honest I'm not sure. xev might provide relevant information but it will be for a specific Window and will also produce so much output it will be hard to figure out what is relevant. Consistent reproduction steps would help but that is easier said than done. Haven't experienced it myself in a long while. |
~ $ xev -root Focus and raise window (mouse leftclick)
Scrollwheel up
Scrollwheel down
but while it locks up so does xev output and a
brakes lockup |
@biopsin it would be real interesting to see what happens if you clear out all but the bare minimum of key and mouse bindings, especially the ones on button 4/5 and see if you still can reproduce the issue! I think I will be adding some trace logging on grab/ungrab operations as well to further be able to understand the issue. |
@pekdon; Your right I do have set mouse button bindings on 4/5 in Client |
Testing latest master with --log-file issue.log --log-level trace ; but it's unfortunatly not catched here either.. |
i did a rebuild of master, and tried trace -logging as well, and i can't see anything either in the trace-log when the error occurs, but i can provoke the error in a few secconds if i scroll quickly up and down with my trackpad in Slack and Vivaldi, but also some times in RDP sessions (where it appears as if the shift-key is stuck, until i "release" the mouse pointer with a single press on the win-key) i think it might be in Electron apps most notably... |
I have also discovered that the bug can also be triggered when just rapidly clicking ui elements (the window decorations for instance) it seems , so its not specifically the mouse wheel. |
Seems as if I'll have to try harder to reproduce this locally, thanks for all the information so long. Won't have time to look into until earliest next week. |
I had the same issue with initial v0.1.18, but after I compiled the last revision (v0.2.0) the problem doesn't showed up anymore using the same configs... maybe someone can confirm |
What is latest? (Githash) |
Well I run @ [003cab5] and I still have lockups just less frequantly, however I have notice lockups as ovlx mentioned too, something that has not been so obvious as I use theme without decorations. |
Oh, what are you building on? Verified OK on Ubuntu, NetBSD 9.1, FreeBSD 12 and OpenBSD 6.8 master should always compile fine, so that's an issue. Let me do a quick commit... |
voidlinux build container |
cleanup - temperary build fail.. |
pull and try again (should add that to my buildbot setup as well) |
nope; same error.. all options left to default
|
[4f08bc9] build fine again ,tnx! |
Do you have any mouse client window mouse bindings for button 4 or 5? Still have set GDK_CORE_DEVICE_EVENTS to 1? If so, try setting to 0 and remove those bindings and see if it still happens. |
i cannot re-produce any lockups either.. |
@biopsin no, i can't get it to lock up no matter what i do to abuse it, i previously could get it to lockup in less than 5 seconds without exception in Slack, now i've scrolled back 3 months in a #general channel with lots of chatter, and tried the archwiki page, all it did was to make my machine hot, but no lock-ups |
@pigge2 thank you for testing. |
thing is it happening in any client window, tested now scrolling back in simple terminal and it ain't even using gtk. |
So for you @biopsin it got worse by the latest change, and this being on void linux I guess? (Probably time to get void up and running on my Pi then) |
Yes, I build it from git yesterday (d7616d3) (with all deps installed, cmake, make, make install ... in Void Linux on a Toshiba laptop, I had some troubles running make with an error "XDestroyImage not declared" but I fixed it installing some devel libs and xwininfo ) Let me explain more, maybe helps (today I just had it happen again with or without compton / picom no matter to me):
|
No, as mentioned earlier its less frequently, but still happens. |
It kind of feels like these actions are being triggered:
I will add some tracing of actions executed in the Action Handler to see if that sheds more light on the issue. |
EDIT : @pekdon I'm wrong! removing all bindings on 4&5 fixes this woho |
Do you include the system configuration (as they have them) or you have all own bindings @biopsin? |
Se commen above |
[ Issue resolved for me ]
this on Client is the culprint, and
works fine now |
@ovlx tried current git master with an updated mouse config to see if fixes the issues for you? |
@pekdon |
Thanks for testing @ovlx, at least I know where to look now. |
Had to eventually remove those last ButtonPress 4/5 as well, had sporadically but very very seldom lockups. Edit: Damnit, it lockedup on clicking issue link #.89.. |
In case it helps, I'm seeing this too on FreeBSD 13.0: pekwm-0.1.17_5,1 |
@stuart-mclaren is this a default install with no custom configuration? |
I can confirm this bug across multiple configurations:
Both systems are notebooks, so scrolling is triggered by a touchpad. Otherwise they're fairly different. The issue is easily reproducible by scrolling in a browser (chromium or firefox). If the bug is triggered, all content on screen stops reacting to mouse events. The cursor can be moved, but no click seems to get through. As soon as any button on the keyboard is pressed, the mouse starts acting normal again, and some of the "queued" actions are executed, sometimes resulting in unwanted effects. It seems to be directly related to the frequency of the scroll-events (if the touchpad is set to scroll faster, the issue turns up sooner and more often), and perplexingly also seems to depend on the complexity of the current screen content. This might explain why it is most noticeable in browsers, but can also happen in terminal windows (e.g. xterm), although much more infrequent. |
After some more frantic scrolltestes on different long sites past days, Im happy to announce this bug is no longer happening for me building against master, so the last refactor of events have a positive effect. Great work! |
Unfortunately I'm still able to produce lockups using gvim clicking franticly between the two windows as explained by gammy. Also, the current master have had some issues for me on Debian 11 amd64 but seems OK on NetBSD 9.2. Mind trying out the button-events branch and see how that behaves for you @biopsin ? |
@pekdon but it does not trigger on the wheel so I salute it 👍🏻 |
🤔 maybe I'm wrong but for me it looks like after a few clicks when the window manager seems frozen, it is behaving very similar when like a key press is required in a key chain sequence |
@pekdon & button-events branch : there is something happening for me with the mouse -> Mod4 + [button] where nothing get triggered. Its bit weird as it did work yesterday when testing hmm. I have to switch to debug mode and try again.. |
After the latest commit with the extra flush removed I have been unable to get pekwm to lock up. |
I still experience one odd issue; sometimes when selecting on any applications top menubar the dropdownmenu wont expand or its hidden behind the main window, either way a Pekwm restart resolves it. |
Closing this issue, haven't had the lockups myself. If you're able to reproduce the menubar issue @biopsin, do open a new ticket with notes on how to reproduce it! |
FYI: having the same issue. For me it happens when scrolling fast (using the scrollwheel or touchpad gestures, dragging the scrollbar does no harm). It is easy to reproduce when using chrome. To unblock the WM again I either need to hit the escape button a few times, or switch back and forth between two TTYs using "ctrl + alt + any F key". I am using the debian stable stock version of pekwm. |
what output from I guess its solved in master so you will have to build it for the time being. |
pekwm: version 0.1.18 O.k. will try. |
The debian repo version of pekwm is nearly two years outdated, and you should update to the latest release. |
I have encountered an issue where, if you scroll really up and down using the mouse wheel, all mouse inputs will lockup randomly, no left or right click, pressing space(and otherkeys) on the keyboard interrupts the lock and it continue as normal
running 18.04.3 with lxqt and kernels 5.0/5.2/5.3
disabling any keybinds to the mousewheel had no effect.
setting GDK_CORE_DEVICE_EVENTS=1 had no effect.
mouse is set to 500hz, will update on whether dropping the polling rate to 125hz changes anything.
edit: noeffect
latest git version was compilled using -O2
The text was updated successfully, but these errors were encountered: