Hide Forgot
Description of problem: I have sddm configured as session manager on my laptop. When the system boots into the login screen, it will display US as selected (and only available) keyboard layout. However as soon as I type the first character of my password, the layout automatically changes to BE, which is the correct layout for my system and which is configured in several other places on the system. The password I type is correctly interpreted in the BE layout. I don't know if the first character would be interpreted in the US layout, because in my password that first character happens not to be layout dependent. Version-Release number of selected component (if applicable): sddm-0.14.0-1.fc25.x86_64 How reproducible: Always Steps to Reproduce: 1. Configure a system with sddm and a default keyboard layout different from US 2. Boot the system Actual results: As described above at startup the default layout shown is US once the first key is pressed, it switches to BE Expected results: the correct layout (BE in my case) should be selected and displayed before the first character is typed. Additional info: * I'm reporting this against Fedora 25, but it exists much longer than that. I'm sure it was there as well on at least Fedora 23 (which was the previous version installed on this particular laptop) * It's possible I had to configure my preferred keyboard layout the first time I booted with sddm. As only US is presented before typing any key, I had suppose I typed one character and then selected my correct layout from the list. * I checked the upstream sddm bug reports, and probably https://github.com/sddm/sddm/issues/202 is related. I have added this as external bug reference.
The github bug also points at an Xorg bug on freedesktop.org. For convenience I have added that one here as well. Note this is not a major bug, but very confusing for users of non-US keyboards.
sddm points to libxcb which points fingers at X server https://bugs.freedesktop.org/show_bug.cgi?id=93701#c4 I'm tempted to close->upstream , unless you have reasons to want to keep this open downstream (feel free to re-open then)
Probably not. My main motivation was to make the Fedora KDE team aware of this issue. Perhaps opening a bug report was not the best channel for that. I mainly figured as several components are involved it may require intervention on the integration level (that is the distribution level).