Distro: KDE Neon Developer Edition Git-Unstable from 19th August 2017. Plasma: 5.10.9 KDE Frameworks: 5.39.0 Related bugs: 312427 and 316084 Number of users on the system: 1 At the user login (after starting the system) and at the lockscreen (if these two use cases are handled differen internally), the password field of the user is not focused and therefore, needs to be focussed manually (by clicking into the field). This circumstance is unfortunate, because it minimizes flow of user interaction.
works fine here. Which look'n'feel package are you using?
(In reply to Martin Flöser from comment #1) > works fine here. Which look'n'feel package are you using? Thank you for the quick reply! Turns out, the problem was my dual screen setup. The screenlock screen is shown on both screens, but the de facto main monitor was turned off. I have therefore written in the correct input field on the "wrong" monitor, but could not see it, because it was turned off. So, my fault. One question arises though: Why is the screenlock shown on both screens in general? For instance on Windows 10, the second (not the main) screen ist tilted black.
(In reply to Christian Ohrfandl from comment #2) > Why is the screenlock shown on both > screens in general? For instance on Windows 10, the second (not the main) > screen ist tilted black. I think you can answer that question yourself: to handle situations just as yours. If for whatever reason the main monitor is not visible it should still be possible to unlock.
(In reply to Martin Flöser from comment #3) > I think you can answer that question yourself: to handle situations just as > yours. If for whatever reason the main monitor is not visible it should > still be possible to unlock. Well, of course I thought about that ;-) But as I just found out, there is an explicit option to choose the main monitor/view, which would therefore support the opinion of only showing the screenlock on the main screen. Of course, this is no major "flaw" but rather a design choice. It's just my two cents... So I can set the bug to closed, if you want to... BTW (I do not know if you are the correct person for this question): I could not find KDE Neon in the platform list while reporting the bug. Considering that KDE Neon is the official distro for KDE development, it would be nice to find it in the platform list. Additionally, version 5.10.9 was not choosable aswell... In general, reporting a bug is not that easy due to the fact that "Product" shows a considerably large amount of applications; I guess not every user is able to distinguish between this bunch of applications and even if so, the sheer amount of them may make you report the bug at all. Maybe an improvement using an alternate approach for instance by classifying the products into categories (categories may be choosen by the amount of bugs for the corresponding products and/or cluster analysis).