X stops receiving mouse clicks
marius at gedmin.as
Wed May 13 08:25:05 PDT 2009
On Wed, May 13, 2009 at 10:11:42AM +1000, Peter Hutterer wrote:
> On Tue, May 12, 2009 at 04:35:51PM +0300, Marius Gedminas wrote:
> > On Tue, May 12, 2009 at 05:57:00PM +1000, Peter Hutterer wrote:
> > > no, actually. this is how input devices work. the physical devices are
> > > abstracted away through the virtual core pointer. all events go through this
> > > core pointer device, and if an application grabs it then events are no
> > > longer sent to anyone else. same with the keyboard.
> > > hence if you have a rogue grab, all devices seem to stop working.
> > Are there any debugging facilities for finding out which X client has
> > the grab?
> > I once spent an hour killing all processes one by one until I found the
> > one responsible (gnome-settings-daemon):
> > http://mg.pov.lt/blog/xorg-snafu.html
> if you have a second machine you can ssh+gdb in and look at
> CLIENT_BITS(inputInfo.pointer->deviceGrab.grab->resource). this should give
> you the client mask for the grab, and with xwininfo -root -children -all you
> can then match that up with a running client (that's from memory, no
Thank you, this is more or less what I wanted to know in case the bug
strikes again (probably unlikely).
Premature optimization is the root of all evil.
-- D.E. Knuth
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: Digital signature
More information about the xorg