I tried the command and it worked. And I may have an idea of what's
wrong. I'm running plasma-netbook and by default krunner doesn't start
when plasma-netbook is running. If krunner is responsible for locking
the screen I may have to enable krunner to start along with my
plasma-netbook session. Does that make sense?
2012/3/15 Pablo Sanchez
[ Comments below, in-line ]
On 03/15/2012 11:56 AM, José Ricardo De León Solís wrote:
KDE doesn't lock my screen either way. I have enabled the auto lock option in the screen saver configuration and doesn't work. I also try to lock my screen on demand and doesn't work. I've yet to try the command though.
Hi,
Please open two terminal windows. In one, `tail -f ~/.xsession-errors' ... press <return> a few times to give you a visual break between the end of the file and potential new lines appearing.
In the second window, type:
qdbus org.kde.krunner /ScreenSaver Lock
Do any errors appear in `.xsession-errors'?
If so, paste them in a response back to the list and/or google the errors to try and find a solution. :)
Cheers, -- Pablo Sanchez - Blueoak Database Engineering, Inc Ph: 819.459.1926 Blog: http://pablo.blog.blueoakdb.com Fax: 760.860.5225 (US) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org