Registered Member
|
Hi!
How can I launch manually Kscreensaver? Going to system settings and launching from there always works, but I'm wondering if there's a more direct way (eg. launching from konsole). I used to activate kscreensaver from konsole (also useful for making a desktop launcher or a keyboard shortcut), but the command I used, no longer works. TIA! |
Manager
|
|
Registered Member
|
Nope!
This presents me the lock screen (and I have to enter my pwd), but don't activates the screensaver. |
Manager
|
|
Registered Member
|
Well, I tested both options, more thoroughly and it's just a random effect if they succeed or not.
They may launch kscreensaver (asking or not for pwd at resume), or they just present the lock screen, or just returning to the next konsole line (without actually doing something). Also giving "xdg-screensaver status", returns "disabled"! |
Administrator
|
Which screen locking option do you have specified in System Settings?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Start automatically after 30min.
Screen locker type: Screen saver. |
Administrator
|
Okay. At what point is your screen set to automatically lock?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Immediately (after pressing Enter).
|
Administrator
|
Try disabling that behaviour in the settings, and then trying again with the qdbus command given above. I suspect that setting the screensaver as active is triggering an immediate locking of the screen.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Nope! No visible difference.
|
Administrator
|
I'm afraid i'm not sure why this is happening - it seems SetActive is now seen as "lock desktop immediately". I would suggest filing a bug report at bugs.kde.org.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
1) I created a new user account (in order to be sure, for filing a bug report), but at the new account I can properly launch Kscreensaver from Konsole (both ways, with qdbus and xdg).
I think something has to be done, with the various config files, scattered arround. Maybe a simpler, more laconic approach, without so many config files, that confuses the applications. 2) Even at the new user account, Kscreensaver locks the screen afterwards. I doubt though, if it's meaningful to create yet another bug report. KDE tracker has already many reports, that Kscreensaver locks the screen. Most of them. marked as solved or duplicated. |
Administrator
|
For #1, is any output made when you try to launch KScreenSaver from the terminal under your usual user account?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Registered users: Bing [Bot], blue_bullet, Google [Bot], rockscient, Yahoo [Bot]