LinuxQuestions.org - Xscreensaver & session-lock confusion, using XDM, KDE & Slackware.

The three situations, and their current functionality:

1 - Freshly booted machine sitting at login prompt; eventually the screen blanks and/or DPMS kicks in, but no screensaver ever happens here.
2 - I'm logged into my desktop and leave it idle; xscreensaver kicks in exactly as it should, eventually locks, and works perfectly as I have it configured. The unlock dialogue window is the fancy Xscreensaver one.
3 - Like 2, but instead of leaving it idle, I press 'Lock Session'. It indeed locks, but there's no screensaver, just a black screen, and then a different (plain) unlock dialogue window..

The goal: 1 and 3 above, should work like 2.

I've followed the instructions in the xscreensaver manpages, as well as on LQ here in several threads, for making the xscreensaver start on the initial login screen, but it doesn't work.
For # 3 above, I want to use Xscreensaver, NOT xlock, but cannot figure out what to change/edit to get it to work. Here's (some/all of) the various files I have lying around to get these working:

$HOME/.xscreensaver - my xscreensaver config file, which works perfectly.

/root/.xscreensaver - identical to the above file.

$HOME/.xinitrc AND /root/.xinitrc SYMLINKED to /etc/X11/xinit/xinitrc which contains the following:

Code:

#!/bin/sh

# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $



userresources=$HOME/.Xresources

usermodmap=$HOME/.Xmodmap

sysresources=/usr/X11R6/lib/X11/xinit/.Xresources

sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then

    xrdb -merge $sysresources

fi

if [ -f $sysmodmap ]; then

    xmodmap $sysmodmap

fi

if [ -f $userresources ]; then

    xrdb -merge $userresources

fi

if [ -f $usermodmap ]; then

    xmodmap $usermodmap

fi

# Start the window manager:

nvidia-settings -l

startkde

$HOME/.Xresources contains:

Code:

xscreensaver -no-splash &

/usr/bin/kdesktop_lock contains:

Code:

#!/bin/sh

# xscreensaver-command -lock

# xscreensaver-command -display :0.0 -lock

xscreensaver-command -lock || xlock $*

exit 0

/usr/lib/X11/xdm/Xsetup contains (among other stuff) the following lines at the top:

Code:

xhost +localhost

xscreensaver-command -exit

xscreensaver &

Per instructions elsewhere, I added to /usr/lib/X11/xdm/Xsession AND /usr/X11R6/lib/X11/xdm/Xsession the following lines:

Code:

# Section to run xscreensaver on system login screen:

xscreensaver-command -exit

xscreensaver &

# End xscreensaver info.

There are as you may know *numerous* other text files and scripts lying around, dealing with KDE, X and XDM, and I think I've played with all of them at some point over the past few months, but nothing seems to have any effect at all on situations 1 and 3 as I mentioned at the start of this post.
If someone can point me to a(nother) file(s) which need to be edited, or what to do with one of the ones mentioned here, I'd be pleased :)
Thanks!

PS - Also, I have taken to configuring my $HOME/.xscreensaver file by hand, for much better configurability. There's an option in it named 'memorylimit' which is not explained in the manpage. What's it for, and what units (b, kb, Mb) is it in? Currently it is set to 0 which presumably means unlimited, but if I were to actually set a value there, what would it be 'limiting' ? For example, would it restrict the size of the image-file my screensaver grabs?