3 ms·
The offending commit[1] loads fine for me, but I'd rather not call out some poor OSS contributor by name here. My question is: what is the actual function/line
by lepht 15y ago
The offending commit[1] loads fine for me, but I'd rather not call out some poor OSS contributor by name here.
My question is: what is the actual function/line that causes the screen lock to die? My C knowledge is close to non-existent, but the ungrab all function looks a bit suspicious. Some commentary by someone who understands what's going on here would be appreciated.
[1]: http://cgit.freedesktop.org/xorg/xserver/commit/?id=7d2543a3cb3089241982ce4f8984fd723d5312a1 http://cgit.freedesktop.org/xorg/xserver/commit/?id=7d2543a3...
- yew 15y agoX11 screen lockers (usually) work by filling the screen and grabbing all keyboard and mouse input. The UngrabAllDevices function interferes with this functionality, and optionally kills the "offending" process. Said functionality is entirely intentional, although presumably the author didn't consider the implications outside of a debugging context.