On 22 January 2012 18:25, Roman Z. <rom...@lavabit.com> wrote: >> On 21 January 2012 01:13, Bjartur Thorlacius <svartma...@gmail.com> wrote: >> > Ţann fös 20.jan 2012 23:42, skrifađi Rob: >> >> >> >> On Fri, Jan 20, 2012 at 07:01:22PM +0000, Bjartur Thorlacius wrote: >> >> Surely it just destroys the window, you can't get a PID for any X >> >> window, >> >> since it could be a networked one >> >> >> > >> > As I expected. The PID is usually stored in a window property, as is the >> > hostname, of every or most windows. But this is a flat out bug in slock. >> > Slock should survive window destruction, right? >> >> Did anyone reproduce this issue with slock? > > Yes, slock is affected too. > >> I pushed a change that adds a dummy error handler instead. Please >> could anyone test hg tip if it is still affected? >> (Though the correct handling will be recreating the particular slock >> window as well). > > No change. Maybe this gives you a hint though: this is printed when > slock is killed with ctrl+alt+multiply, with both the old version and > the patched version: > >> XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" >> after 28 requests (28 known processed) with 0 events remaining.
Ok, so the error handler trick doesn't work as it exceeds some x server threshold and then raises an XIO fatal error. I will investigate this issue further, but will need a more current X server first ;) Cheers, Anselm
