While I am able to lock my screen with ctrl-alt-l, the automatic locking after idle time seems to be broken.



No locking is happening at all. I found out after I left my workspace without locking my screen, waking up my monitors, and finding out my desktop was unlocked.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial

konsole --version
Qt: 5.5.1
KDE Frameworks: 5.18.0
Konsole: 15.12.3

Seems to work at here with:

Qt 5.7.0
KDE Frameworks 5.24.0
KDE Plasma 5.7.3
KDE Applications 16.04.3
Arch Linux

Something to try

1) Examine if the problem is local: viewtopic.php?f=14&t=38828

2) Do the logs have error messages ?

At here:
- Turning the Screen locking on: 'Lock screen automatically after 1 min'
- Waiting a moment - the screen is locking at here.
- Unlocking
- Looking the systemd journal:

Code: Select all

journalctl -n 100 > locking.txt

locking.txt has at here:

...
Aug 03 10:41:01 archfox ksmserver[759]: lock called
Aug 03 10:41:01 archfox ksmserver[759]: Lock window Id: 23068685
...

More journactl tips: https://www.digitalocean.com/community/ ... stemd-logs

I have the same issue: KDE will not lock the screen automatically no matter the time in the setting.

I moved it from 1 min to 2 min and sent a log message before hitting apply, waited 5 min to be very sure, here's journalctl -f

Feb 11 15:45:55 paddy.optusnet.com.au zebee[4865]: change 2 2min
Feb 11 15:50:15 paddy.optusnet.com.au systemd[1]: Starting system activity accounting tool...
Feb 11 15:50:15 paddy.optusnet.com.au audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 11 15:50:15 paddy.optusnet.com.au audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 11 15:50:15 paddy.optusnet.com.au systemd[1]: Started system activity accounting tool.
Feb 11 15:50:50 paddy.optusnet.com.au plasmashell[1853]: QXcbConnection: XCB error: 2 (BadValue), sequence: 9629, resource id: 92274693, major code: 141 (Unknown), minor code: 3

and here is -n just in case
Feb 11 15:45:55 paddy.optusnet.com.au zebee[4865]: change 2 2min
Feb 11 15:50:15 paddy.optusnet.com.au systemd[1]: Starting system activity accounting tool...
Feb 11 15:50:15 paddy.optusnet.com.au audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=42
Feb 11 15:50:15 paddy.optusnet.com.au audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=429
Feb 11 15:50:15 paddy.optusnet.com.au systemd[1]: Started system activity accounting tool.
Feb 11 15:50:50 paddy.optusnet.com.au plasmashell[1853]: QXcbConnection: XCB error: 2 (BadValue)

Fedora 24 Plasma 5.8.5 I think.



As you can see... ain't nothing happening screenwise after hitting apply.

Some time ago I set xscreensaver as the screensaver. but I backed out of that a while back. I suppose there is something I missed but if so I can't find it.

I'd like to get in on this thread as well. This is a fresh Mageia installation on a desktop. I blew away my home partition and just reinstalled and configured everything with minimal restoration from backups.

Linux spike 4.9.50-desktop-1.mga6 #1 SMP Wed Sep 13 23:14:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

plasma-desktop-5.8.4-1.mga6.x86_64

This works just fine:

Code: Select all

set dpms force off

I set the locking screen to activate in 1 minute. Wait one minute plus 10 seconds and nothing happens.
I check the logs:

Code: Select all

journalctl -n 100 > locking.txt

I scour that text file for "lock" and get nothing:

Code: Select all

[madams@spike ~]$ grep lock locking.txt
[madams@spike ~]$


It isn't calling for the screen locking to happen.

Here's the substance of locking.txt: https://pastebin.com/YZjWG8U8

I should also mention that I'm trying to use the power management settings to power the screen off after an interval. This is what I would really like, but it's not working. I realize that this would constitute a different issue and I'll take it up there. Just wanted to get it out there.

I had a similar problem. Then I realized I have accidentally configured "Never turn off screen" and/or "Never shut down computer" under Power Management > Activity Settings > Define a special behavior. After I disabled this, screen locking started working again.