kscreenlocker is 5.8.4. Not in bugzilla version list. Using more than one head (2 or 3) with a notebook. After screens are off, waking up the system, like with a key press, the displays turns on in very slow way. This is probably xorg, xrandr, prime issue. The primary display (LVDS1) turns on very fast, the others about 3s-5s each (serialized). The problem with this is that each screen has its one locker password widgets. And each time one screen comes on, it will steal the focus from the previous. So, If it is a 3-head, and the password is "foobaragain", I might get "foo" in the first head, "bar" in the second and "again" in the 3rd. This is very annoying, btw. I understand what is going on. Each screen have different resolution, DPI, etc. So each needs each on control set. The first one needs to steal the focus as it could be with any application. However, this is not true for the 2nd and 3rd controls. At least the controls should be able to sync the input and then wouldn't matter who really have the focus.
Git commit f8043de10b5dd94b9b931a92f3aa7167188786c9 by Fabian Vogt. Committed on 01/03/2017 at 17:48. Pushed by fvogt into branch 'Plasma/5.8'. Implement manual focus on click Summary: Currently only the first created screenlock window gets focus. On clicks, no focus events are sent, which makes it impossible to input passwords. This patch now makes it possible to focus to a different screenlock window (on a different monitor, for example) using a mouse button press. This should also fix newly created screenlock windows stealing the focus of already displayed ones as only the first window gains automatic focus. Related: bug 348789 Test Plan: Locked the screen, now I can use the password input on the secondary screen as well. Reviewers: #plasma, graesslin, broulik Reviewed By: #plasma, graesslin Subscribers: hein, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D4821 M +0 -1 greeter/greeterapp.cpp M +24 -2 x11locker.cpp M +2 -0 x11locker.h https://commits.kde.org/kscreenlocker/f8043de10b5dd94b9b931a92f3aa7167188786c9
*** Bug 378093 has been marked as a duplicate of this bug. ***