it won't tell you *why* the grab is stuck though, but debugging that is fickle, the cause can be virtually anything, either the client not sending an ungrab request or the server ungrabbing the wrong device. That dump should get you a step closer to verifying the grab and who has it. Should be possible on anything reasonably new (3 years or so.) The next step would be to trigger the grab debugging in X and look at the logs: setxkbmap -option "grab:debug" and when it's stuck, hit ctrl+alt+F11 and look at the xorg.log, that lists all current grabs, including passive ones. Here's one from several years ago, you should be able to modify it if needed: You can write a very simple test program that tries to grab the mouse, if that fails that would confirm the grab at least. Yeah, sounds like a stuck grab, but those are notoriously hard to debug. You might in particular try the grab log suggestion. I asked one of the X.Org developers for ideas and this is part of the answer. My guess is that some change in VirtualBox might have triggered it. Sorry for the slow answer, I was on holiday.
0 kommentar(er)
