Version:            (using KDE KDE 3.5.6)
Installed from:    Debian testing/unstable Packages

This has been reported in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389585

Whenever I lock the screen via KDE-Menu -> Lock Session the X screen
saver timout will be set to the strange value of 310 seconds:

$ xset q | grep -A2 Saver
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  600
[... locking and unlocking the screen now ...]
$ xset q | grep -A2 Saver
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  310    cycle:  600

I think I was once able to reproduce this by calling kdesktop_lock in
konsole, but now I get sane results using either parameters. Also,
when logging out of KDE (and saving the session) to the command line
and running startx again the timeout will be reset to 0, the desired
value.
Unfortunately I have no idea what might be causing this behavior. In
kcontrol I have deactivated all screen saver stuff, but somehow the
timeout gets activated whenever I lock the screen, which is no big
deal, yet slightly annoying.


--- 2nd mail ---

Summary

Expected behavior: Locking the screen via the kde menu does just that,
it won't change any settings.
Experienced behavior: Changes in settings occur, but they are not
reflected in any visible setting within kde but only visible via xset,
nor do they seem to be persistant.
Severity: Minor. This can easily be helped manually after each
occurence, but it's still annoying.

Recently I realized that locking the screen doesn't just blank but
calls the selected screen saver instead (which normally is Blank Screen
in my case), even if it is _not_ set to start automatically, so I
fiddled with them a bit.

Going to kcontrol -> Appearence & Themes -> Screen Saver, selecting
Blank Screen (or any other saver, fwiw), activating Start automatically
and clicking Apply will set the screen saver timeout. Just as can be
expected from it. Well, it adds 10 seconds for some reason.
If I set this timeout to, say, 10 minutes, but _deactivate_ Start
automatically, and then follow the procedure as outlined in my original
bugreport, the timeout will still be set to 610 secs, so this seems to
be where the timeout value comes from.

Apparently locking the screen via the kde menu does the same as
activating a screen saver (including setting its timeout), but doesn't
reset the timeout to its original value when unlocking. This might be
intended, but to me it came completely unexpected, especially as I
didn't notice this behavior ealier on.
Anyway, if this is intended, something is broken: Even when kde screen
savers are explicitely deactivated, locking the screen will activate
their timeout, but won't say so when checking the screen saver settings
via kcontrol.