[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 --- Comment #6 from ukeic...@proton.me --- (In reply to fanzhuyifan from comment #3) > (In reply to fanzhuyifan from comment #2) > > Is the user using the default breeze theme? > > The user reports using the oxygen theme (so not a 3rd party theme). I

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 ukeic...@proton.me changed: What|Removed |Added CC||ukeic...@proton.me --- Comment #5 from

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|---

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 --- Comment #3 from fanzhuyi...@gmail.com --- (In reply to fanzhuyifan from comment #2) > Is the user using the default breeze theme? The user reports using the oxygen theme (so not a 3rd party theme). -- You are receiving this mail because: You are

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 --- Comment #2 from fanzhuyi...@gmail.com --- FWIW I can't reproduce on arch linux, wayland, git build. After resuming from suspend to ram, the lockscreen is fully functional and gets all key presses. Is there a downstream bug report for this? I didn't

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 --- Comment #1 from unblended_icing...@simplelogin.com --- CCing some people who might have an insight on this bug. -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 unblended_icing...@simplelogin.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 unblended_icing...@simplelogin.com changed: What|Removed |Added CC||unblended_icing552@simplelo

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 unblended_icing...@simplelogin.com changed: What|Removed |Added CC||n...@kde.org -- You are

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 unblended_icing...@simplelogin.com changed: What|Removed |Added CC||k...@davidedmundson.co.uk

[kwin] [Bug 484122] [Security Vulnerability] Keyboard input may not be blocked by lock screen

https://bugs.kde.org/show_bug.cgi?id=484122 unblended_icing...@simplelogin.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b