Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

That's not mapping a PID to the window though - it's just destroying a window ID and seeing what happens to error out - which might not happen if the app was written to handle the window being destroyed outside it's control, or it's running on a different machine where you won't see any error output/a process dying.


https://gitlab.freedesktop.org/xorg/app/xkill/-/blob/master/...

It literally is using XKillClient - https://linux.die.net/man/3/xkillclient

You can kill the connection of another client if you know its id. That's one of the reasons why we love X11 so much.

Another way, as josefx mentioned, is to kill the PID from _NET_WM_PID window property. This is often used by window managers when they offer to kill an unresponsive application.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: