Hi Guys,
I've been using xlock for years and never had any issue with its
crashing. May be it is due to the fact that when I want my screen
locked, I do not care to watch running goblins on the screen, therefore
I use
XLock.mode: blank
in my .Xresources. May be just making blank mode to be default (unless
explicitly asked to 'shoot in the foot' with some fancy one)? or may be
even
mv /usr/bin/xlock{,.bin}
echo >>/usr/bin/xlock<<EOF
#!/bin/bash
while true; do
xlock.bin $* && break
echo 'xlock abnormal exit, lets lock again'
done
EOF
chmod +x /usr/bin/xlock
would at least reduce the severity of this elderly bug and allow
xlockmore to get into Debian release?
Otherwise, please provide reproducible scenario (which screen saver
crashes it etc) so it would be possible to actually fix up the bug
properly.
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
