Bug#4551: xautolock and xtrlock conflict on screensaver
If xautolock tries to lock the display (with xlock) when xtrlock is
running, the screen flashes black and then returns to showing the X
display. After this, the screen saver does not kick in when it should.
The lack of a screen saver may lead to monitor burn over extended
periods if the user was expecting the screen saver to operate.
xautolock should check to see if the display is already locked before
attempting to run the locker program.
Dave Holland <email@example.com>
Trinity Hall, Cambridge, UK <firstname.lastname@example.org>