Bug 1084670 - screen lock: password input focus on multimonitor setup
screen lock: password input focus on multimonitor setup
Status: NEW
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma)
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: E-Mail List
E-mail List
Depends on:
  Show dependency treegraph
Reported: 2018-03-09 11:56 UTC by Peter Sütterlin
Modified: 2018-03-09 11:58 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Peter Sütterlin 2018-03-09 11:56:51 UTC
I am using my laptop (Lenovo T460p) for work both at home and at the office.  At the office I have a docking station with a second monitor, set up as an area next to the main screen (i.e., not in copy mode).  Normal procedure is to only suspend the laptop (close lid), and resume, which starts the lock screen.

If I resume, or lock the screen, in the dual monitor config, lock screen and unlock prompts are displayed on both screens.  But only one of the password fields can get the input focus.  That is, I can click the password field e.g. on the laptop screen, and enter my password.  It shows up as bullets, but only on that screen.  The input field on the other monitor stays empty.

I can move the mouse cursor to the second screen, but clicking the input field there does *not* move the focus there.  I am not able to input anything.  I can however click on any of the entries (like switch user, login).  But if I click 'login' it uses the (empty) password from that screen and of course fails to unlock the session.

The first time I have noticed this was in TW 20180227, likely because the input focus was on the second screen there, as I could not enter my password on the laptop screen.  At that time, I did not look at the second screen at all, sorry.
I only had a closer look after finding some older (redhat-related) postings regarding input focus.  But the issue seems new, I've been using this laptop for more than 1 1/2 years in sucht dual-config without seeing this once.

In case it's relevant: The laptop has an optimus setup, but I use the CPU-included one (i7 - HD530, using intel driver)
Comment 1 Peter Sütterlin 2018-03-09 11:58:04 UTC
Argh - sorry.  I of course forgot the important thing:
This is running plasma5/kwin_x11.