--- Please enter the report below this line. ---

Doesn't lock automatically by timeout, which presents a security issue. Seems
to work in a newly created test user setup, and randomly works sometimes in my
user, but I have no idea what makes in work. Probably some app "inhibits" the
automatic timeout, but I have no idea how to check it with all that
"brilliant" dbus crap.  Ubuntu has https://wiki.ubuntu.com/
DebuggingScreenLocking, but it's for Gnome, not KDE.


Debian Release: 10.0
  991 stable          security.debian.org
  991 stable          ftp.fi.debian.org
  990 buster-backports ftp.debian.org
   99 stable          www.deb-multimedia.org
  500 stable          dl.google.com
  500 stable          deb.torproject.org
--- Package information. ---
Depends                             (Version) | Installed
=============================================-+-====================
kpackagetool5                                 | 5.54.0-1
libc6                               (>= 2.28) |
libkf5configcore5                 (>= 5.24.0) |
libkf5configgui5                  (>= 4.97.0) |
libkf5coreaddons5                 (>= 4.97.0) |
libkf5crash5                      (>= 4.96.0) |
libkf5declarative5               (>= 5.50.0~) |
libkf5globalaccel-bin                         |
libkf5globalaccel5                 (>= 5.0.0) |
libkf5i18n5                       (>= 4.97.0) |
libkf5idletime5                   (>= 4.96.0) |
libkf5notifications5              (>= 4.96.0) |
libkf5package5                    (>= 5.42.0) |
libkf5quickaddons5               (>= 5.50.0~) |
libkf5waylandclient5             (>= 4:5.5.0) |
libkf5waylandserver5             (>= 4:5.6.2) |
libkf5windowsystem5               (>= 5.25.0) |
libpam0g                        (>= 0.99.7.1) |
libqt5core5a                  (>= 5.11.0~rc1) |
libqt5dbus5                      (>= 5.11.0~) |
libqt5gui5                       (>= 5.11.0~) |
libqt5network5                   (>= 5.11.0~) |
libqt5qml5                         (>= 5.0.2) |
libqt5quick5                       (>= 5.2.0) |
libqt5widgets5                   (>= 5.11.0~) |
libqt5x11extras5                   (>= 5.6.0) |
libseccomp2               (>= 0.0.0~20120605) |
libstdc++6                         (>= 4.4.0) |
libwayland-client0                (>= 1.9.91) |
libwayland-server0                  (>= 1.3~) |
libx11-6                                      |
libxcb-keysyms1                    (>= 0.4.0) |
libxcb1                                       |
libxi6                        (>= 2:1.2.99.4) |


Recommends                   (Version) | Installed
======================================-+-===========
kde-config-screenlocker                | 5.14.5-1


Package's Suggests field is empty.

Control: severity -1 normal
Control: tags -1 + unreproducible

I'm really sorry that kscreenlocker is not working right for you, sadly
I'm not being able to reproduce this issue, and as far as I can see it
works as expected. But, there are a couple of catches in this, for
example Xserver won't allow a screen lockeer to work whenever a context
menu window or a tooltip is being shown, this is a known problem in the
X11 world [1] [2] [3] that's only solved by migrating to wayland.

 From the side of the inhibitors, I'm not sure if there is an api you can
call to obtain the current inhibitors, but you can always try to lock
the screen by hand and see if the screen does in fact get locked or not.
Some known inhibitors are: google-chrome in certain situations, slide
programs in presentation mode, and most video players.

Hope this help you figuring out where is the problem you are seeing.

[1]: https://bugs.kde.org/show_bug.cgi?id=78871
[2]:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/49579
[3]:
http://blog.martin-graesslin.com/blog/2015/01/why-screen-lockers-on-x11-cannot-be-secure/

Happy hacking,