Even if X server is to blame for the hack looping xscreensaver is to
blame for not unlocking the screen. If I can kill the hack
xscreensaver can too. And the reason the hacks are separate is
exactly that xscreensaver need not rely on their correct operation
for xscreensaver itself to operate correctly.
You can think that all you want, but your X server is not operating
correctly, and without fixing the X server, there is no way for
xscreensaver to function as designed.
Not surprisingly, xscreensaver *does* need to rely on the correct
operation of the *window system itself* to operate correctly.
Report a bug against X.
Claiming it's a bug in xscreensaver isn't going to get your problem
solved.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
