I just tripped on this bug when launching 'xscreensaver-command -lock' from
xmobar's label action. Locking via shell-script with 'sleep 0.1' before
xscreensaver-command works around this problem.

Reply via email to