On Tue, Jun 14, 2016 at 6:23 PM, Brandon Allbery <allbery.b@gmail.com> wrote:

On Tue, Jun 14, 2016 at 6:19 PM, Brandon Allbery <allbery.b@gmail.com> wrote:
I just realized xeyes was a bad choice; Stoppable relies on _NET_WM_PID, and...

If you test this with a terminal, use one that doesn't use factory backends (like xterm or urxvt --- NOT urxvtc!) or suppress the backend factory; otherwise you get the pid of the factory and will be very unhappy when it suspends every terminal instance because they're all owned by the factory.

I should also mention that I pointed out these and other shortcomings of the information any implementation could rely on for this --- which isn't much --- to the author back when they were writing it. You seem to be hitting all the pain spots where it can't work sensibly. (Very recent xorg has a call that could make the xeyes case work, but would not help with the other cases I mentioned. It would also open an interesting potential issue with remote windows via ssh X11 forwarding, where it could suspend the ssh as the apparent owner of the window and cause the remote to time out and drop the connection.)

X11 *really* does not want this kind of thing to work.

brandon s allbery kf8nh sine nomine associates

allbery.b@gmail.com ballbery@sinenomine.net

unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net