When SDDM initializes, the focus is never on the correct field. At the first use of a freshly-installed system, the User field is not filled in, and the focus should be on that field, but it is not. Moreover, the Password field is filled in with a non-blank value containing god-knows-what (it displays only as bullet glyphs). After a successful login, the last-logged-in user is filled in in the User field, and the Password field is blank. In this case, the focus should be on the Password field, but it is not. In both cases, it isn't clear where the focus actually is, but typing doesn't enter data in any modifiable field on the screen. Reproducible: Steps to Reproduce:
Assignee: bugsquad => doktor5000
That is with which theme, and what sddm version? Can reproduce that on a single-user system, the only user is filled in in User field, but password field will be empty, no glyph filled in. Focus is on no field at all, and tab will not cycle through input areas. There may be an issue with multi-monitor setup: https://github.com/sddm/sddm/issues/514 but to me this issue sounds like https://github.com/sddm/sddm/issues/501 I'll try to play a little with the workaround for the theme mentioned in which seems to enable the focus. See https://github.com/sddm/sddm/issues/501#issuecomment-147101026 and https://github.com/sddm/sddm/issues/501#issuecomment-153084546 Thanks for the report.
Status: NEW => ASSIGNEDURL: (none) => https://github.com/sddm/sddm/issues/501CC: (none) => doktor5000Hardware: x86_64 => AllSummary: focus not on correct field initially => sddm - keyboard/input focus not on correct field initially
FWIW, the originally expected behaviour regarding focus seems described here: https://github.com/sddm/sddm/issues/197 but seems this is somehow working differently since the move to Qt5, but have to mess around with the themes more.
After a short test, the workaround to enable autofocus works fine. I've just submitted sddm-0.12.0-4.mga6, please test once it hits your mirror.
sddm-0.12.0-3.mga6.x86_64.rpm and whatever the default theme is. I agree, both links (the bug and the expected behavior) are spot on, thanks.
This appears to be fixed now.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED