[Bug] Password field not getting focus

[ur5us]

Description

3, maybe even 4, out of 5 times when connected to a 2nd screen the password field is not getting focus. Here’s a little video: https://youtu.be/GYGDFNT-B6g It’s not possible to tab or click into the field and “submitting” the empty password in an attempt regain focus does not work. What’s worse is that by switching the 2nd screen’s input source to something else than the connected laptop I can get full access to the running session without entering the password at all (not shown in the video).

Budgie version

10.7.2

Operating System

Solus 4

Steps to reproduce the issue

1. Connect to 2nd screen (not sure whether relevant: 2nd screen is to the left of laptop main screen)
2. Lock session
3. Wait a few minutes (the monitor seems to go to some sleep state also, though it continues to provide power over USB-C and plugged USB devices are powered also)
4. “wake” the screen by moving mouse or keypress
5. Switch monitor’s input source to something other than the connected laptop (e.g. USB-C → unused Display Port) when password field cannot be focused
6. Use session without entering password

Not sure whether the specific hardware setup is relevant but just in case: the monitor is a LG 27UK850 connected via USB-C to a Lenovo Thinkpad T495. An external keyboard (ErgoDox Infinity) and mouse (Logitech MX Vertical) are connected to the monitor (as opposed to the laptop). The monitor powers the laptop. Upon “waking” the monitor seems to go through its own wake up states which results in its builtin USB hub to be disconnected from the laptop for a split second which is noticeable due to keyboard backlight going out but also via dmesg logs).

Actual result

Gain access to session without password entry.

Expected result

Password field always gets focus and it’s not possible to gain access to the session without providing a password.

Additional information

No response

[ur5us]

Now that this has been moved, it looks like another variation on #9 as far as I can tell. Maybe somebody more knowledgeable can extract some useful steps to reproduce the issue. But effectively this merged into and closed in favor of #9 I think.

[JoshStrobl]

Yea duplicate of #9 :)