https://bugs.kde.org/show_bug.cgi?id=515119
--- Comment #1 from Kacper Paczos <[email protected]> --- There is a second half to this that is worth keeping in view while the content side is being solved: even setting aside what ends up in the recording, right now nothing tells the person that the recording is still running once the screen is locked. You note that in the report - the SNI is hidden - and that is exactly the gap. The lock screen shows no camera, microphone or screen capture indication of any kind, so for the whole time the machine sits locked there is no way to tell that a capture is in progress, whatever the stream happens to contain. Whoever walks up to the machine, including the owner, learns about it only after unlocking. For reference, the user-facing report of the same thing is bug 496819, and the merge request that came out of it (kwin!9246, "Don't record lockscreen contents") has been sitting as a draft since May. I have filed the intent side separately as bug 525039: locking while a screencast is running should either ask (explicit lock) or pause the stream (idle lock), with RemoteDesktop sessions exempt precisely because of the flexibility you mention here. Keeping it apart so this report stays about the content of the stream. There is also bug 525038 about the indicators being easy to miss in general, of which "invisible on the lock screen" is the extreme case. -- You are receiving this mail because: You are watching all bug changes.
