Jeremie Courreges-Anglas <j...@wxcvbn.org> writes: Hello, > On Tue, Aug 15 2017, Stuart Henderson <s...@spacehopper.org> wrote: >> On 2017-08-15, Jeremie Courreges-Anglas <j...@wxcvbn.org> wrote: >>> On Tue, Aug 15 2017, tomr <t...@equalit.ie> wrote: >>> >>>> I've figured out an effective workaround I think, which is to SIGUSR1 my >>>> running xidle(1) process, which works. >>> >>> That's probably less hackish and better on multi-user machines. >> >> fwiw, I sometimes had problems with characters from my password going to >> xterms when I used xidle. I don't know if it was something odd about my >> setup, but something to watch out for if anyone's changing config as a >> result of this thread.
I'm stepping in just to mention that I've observed the same behaviour, though I thought it was because of the locking program that I used (slock), not xidle. Since then, I've switched to i3lock and stopped using xidle (I'm locking manualy) and haven't observed this behaviour. I'll give xidle a new try and report here if the problem occurs again. Best. > Duh, thanks for the heads-up. This is a bit scary. > >> I like the hackish way :) > > ;)
