15 Jul
2021
15 Jul
'21
4 p.m.
Am Donnerstag, 15. Juli 2021 schrieb Michael via tde-users:
No, I really got that wrong, at least in writing. Thanks for the
clarification.
$ dcop kdesktop KScreensaverIface lock
doesn't start the screensaver on my system but just does what the
command says, it locks the screen/session, just like it would if you
lock the session from TDE menu. I guess you have configured your system
to automatically start the screensaver when you lock the session…
$ dcop kdesktop KScreensaverIface save
directly starts the screensaver and that's what I was looking for in the
first place to try out screensavers in a running session.
On Thursday 15 July 2021 02:11:48 am Stefan Krusche
via tde-users
wrote:
Am Mittwoch,
14. Juli 2021 schrieb Michael via tde-users:
Hi Stefan,
Possibly just a language difference, but just wanted to clarify.
xset won't start the screensaver, the 'lock' above the xset does
that. xset dpms force standby
That will also 'sleep' the monitor without turning it off.
Yeah, thanks. I've been using xset all the time but not thought of
it being able to start the screensaver as well… :-) The 3 second sleep is to extract yourself from the
computer so
moving the mouse (or whatever) doesn't re-awaken the monitor after
'standby' puts the monitor in, well, standby (which I called sleep
earlier).
All of the above is really useful if you have a laptop in a hotel
room (or computer in a bedroom).
Best!,
Michael
Thanks and best to you, too!
Cheers,
Stefan