https://tanguy.ortolo.eu/blog/article36/return-code en a blog about Debian and self-hosting Fri, 09 Dec 2011 07:38:00 +0000 PluXml https://tanguy.ortolo.eu/blog/article36/return-code/#c1323416295-1 https://tanguy.ortolo.eu/blog/article36/return-code/#c1323416295-1 @Zack: Yes, that is right; as I said this is probably a bug either way since something is going wrong, either the return code or the screen locking, and in that case, the error message should at least be understandable. I only took it as an example of how that can be annoying. Fri, 09 Dec 2011 07:38:00 +0000 Tanguy https://tanguy.ortolo.eu/blog/article36/return-code/#c1323385549-1 https://tanguy.ortolo.eu/blog/article36/return-code/#c1323385549-1 I want to suggest the possiblity that, when this happens, the screen only <i>appears</i> to be locked; perhaps there is something the program that controls window 4212 could still do, that it shouldn't be able to do while the screen is locked. This is totally hypothetical on my part, and comes mostly from my expectation that jwz is the sort of person who would get the exit code behavior of his programs right. Thu, 08 Dec 2011 23:05:00 +0000 Zack https://tanguy.ortolo.eu/blog/article36/return-code/#c1323381512-1 https://tanguy.ortolo.eu/blog/article36/return-code/#c1323381512-1 PS: Yes, that xscreensaver-command error (I cannot tell the exact message now since I have only seen it at my office and I did not note it yet) is probably a bug and I should probably report it when I have collected enough information about it. Thu, 08 Dec 2011 21:58:00 +0000 Tanguy