Hi to all!
I've an Asus n752vx laptop with an external monitor connected using an hdmi cable.
The laptop screen is set as the primary one and the external one is at the right side of the laptop.
When I lock the session with Ctrl+Alt+L, ksreenlock appears on both screens and when I click to insert the password, the password field is activated only on that screen and typing the password a dot is added for each character only on that screen.
That behaviour seems correct.
However when I close the lid, the screen is automatically locked which is still OK and the laptop one is turned off by the firmware.
When I open the lid kscreenlock appears only on the external monitor, the laptop monitor is turned off and I see only the mouse pointer on it and whaen I insert the password nothing changes on the external monitor and if I blindly insert the correct password, I can login.
Is it possible to have ksceenshot work as it does when I lock the screen with Ctrl+Alt+L ?

Exact Plasma version and distribution?

Mamarok wrote:Exact Plasma version and distribution?

I'm using an up to date arch linux distro with plasma version 5.20.3-1

Hm, I tried to reproduce this here, but my Plasma version is older and I connect through Display Port:
The lock screen appears on the external monitor when I close the lid, but I haven't it set to go off when closing the lid. When re-opening the lid, the lock screen is again visible in both screens, the entry filed appears when I move the mouse to it.

You should file a bug, or at least ask in the distribution forum if this is a known bug.

Mamarok wrote:Hm, I tried to reproduce this here, but my Plasma version is older and I connect through Display Port:
The lock screen appears on the external monitor when I close the lid, but I haven't it set to go off when closing the lid. When re-opening the lid, the lock screen is again visible in both screens, the entry filed appears when I move the mouse to it.

You should file a bug, or at least ask in the distribution forum if this is a known bug.

It seems that it is already been reported on the forum:
https://bbs.archlinux.org/viewtopic.php?id=251323
but it seems to be not solved and it is not clear if any bug has been opened either in arch or in kde.
So I'll open a bug in the kde because it does not seem a problem related to the packaging. Is it correct?

yes, I would say so: https://bugs.kde.org/enter_bug.cgi?prod ... nt=general