Testing sddm 0.11.0 on Mageia 5 pre-RC, I see that there is an issue with the keyboard layout. "en_US" is preselected and is the only available option, I can't use the "fr" keyboard layout even though my system locale is French. Reproducible: Steps to Reproduce:
CC: (none) => doktor5000Assignee: bugsquad => mageia
This would be this upstream bug: https://github.com/sddm/sddm/issues/202
I have the same behaviour as some reported on the upstream bug report by the way: the flag is initially "us", but as soon as I start typing my password, it switches to "fr".
Hmmm I think we had similar patch for this, will recheck as it was fixed. Patch was added here: http://svnweb.mageia.org/packages?view=revision&revision=797925 and was merged upstream in 0.11: http://svnweb.mageia.org/packages?view=revision&revision=800515 Seems that was a different issue. For me, also only en_US is preselected, and once I select my username and begin typing, it automatically switches to de_DE including the correct flag. Although I don't have some german special characters, I'll check again for the keyboard layout. Do you have either /etc/locale.conf /etc/vconsole.conf or something in /etc/X11/xorg.conf.d/ ? What does localectl show? As our tools don't run localectl, it will probably show nothing, which might be the cause of the bug as mentioned in https://github.com/sddm/sddm/issues/202 Will need to check how Colin fixed similar issues for GNOME et al.
(In reply to Florian Hubold from comment #3) > Do you have either > /etc/locale.conf > /etc/vconsole.conf > or something in /etc/X11/xorg.conf.d/ ? I don't have any of those. > What does localectl show? $ localectl System Locale: n/a VC Keymap: n/a X11 Layout: n/a > As our tools don't run localectl, it will probably show nothing, which might > be the cause of the bug as mentioned in > https://github.com/sddm/sddm/issues/202 > Will need to check how Colin fixed similar issues for GNOME et al. That might be yet another "old cauldron" issue, Colin did implement some stuff with localectl AFAIU, so maybe sddm works fine on new installs of Mageia 5 beta 3. I'll check that in a VM.
I can confirm that the bug also affects a Mageia 5 beta 3 VM.
Whiteboard: (none) => 5beta3
In my Mageia 5 beta 3 VM I do have all the files you mentioned, and the configuration look good: $ cat /etc/locale.conf LANGUAGE=de_DE.UTF-8:de LANG=de_DE.UTF-8 $ cat /etc/vconsole.conf KEYMAP=de-latin1 FONT=lat0-16 $ cat /etc/X11/xorg.conf.d/00-keyboard.conf # Read and parsed by systemd-localed. It's probably wise not to edit this file # manually too freely. Section "InputClass" Identifier "system-keyboard" MatchIsKeyboard "on" Option "XkbLayout" "de" Option "XkbModel" "pc105" Option "XkbOptions" "compose:rwin" EndSection $ localectl System Locale: LANG=de_DE.UTF-8 LANGUAGE=de_DE.UTF-8:de VC Keymap: de-latin1 X11 Layout: de X11 Model: pc105 X11 Options: compose:rwin So I guess all those files and localectl output are related to Colin's fixes for the GNOME l10n issues. Still, all that stuff does not fix the sddm flaw of showing "us" keyboard layout and grabbing the correct one when you start typing.
Lowering the severity as it actually works fine when you start typing (I did not check if the first character was inputted according to the US layout or the system one though).
Severity: major => normal
(In reply to Rémi Verschelde from comment #6) > Still, all that stuff does not fix the sddm flaw of showing "us" keyboard > layout and grabbing the correct one when you start typing. This is confirmed by 3 people in the upstream report, best comment there. We can't do much about this. Added a short note to Errata: https://wiki.mageia.org/en/Mageia_5_Errata#sddm
(In reply to Florian Hubold from comment #8) > This is confirmed by 3 people in the upstream report, best comment there. > We can't do much about this. Yep, let's see how upstream handles it. It's good to have our own bug report open for Mageia users that might want to report the same issue anyway. > Added a short note to Errata: > https://wiki.mageia.org/en/Mageia_5_Errata#sddm Thanks! :)
I got it working by editing this file /usr/share/sddm/scripts/Xsetup Added: setxkbmap XX XX are your keyboard layout code can list availables with: localectl list-keymaps
CC: (none) => ozkyster
You do realize that we cannot hardcode the keyboard layout in the script that is supposed to set this according to systemwide defaults?
Priority: Normal => LowStatus: NEW => ASSIGNEDAssignee: mageia => doktor5000Whiteboard: 5beta3 => 5beta3, IN_ERRATASeverity: normal => minor
Yes i realize it,that was just my own test that suggested thing temp fix it.
Keywords: (none) => UPSTREAM
Whiteboard: 5beta3, IN_ERRATA => 5beta3, IN_ERRATA 5rc
Whiteboard: 5beta3, IN_ERRATA 5rc => 5beta3 ERRATA 5rc
Whiteboard: 5beta3 ERRATA 5rc => 5beta3 FOR_ERRATA 5rc
Whiteboard: 5beta3 FOR_ERRATA 5rc => 5beta3 IN_ERRATA 5rc
Whiteboard: 5beta3 IN_ERRATA 5rc => IN_ERRATA, MGA5TOO
Still no progress upstream, so I pinged them in the bug report: https://github.com/sddm/sddm/issues/202
It was suggested earlier that this might be an XCB bug, so reported that: https://bugs.freedesktop.org/show_bug.cgi?id=93701
Still no activity upstream, not much more info on the XCB bug report, and upstream moved it from the 0.14 milestone to 0.15, so we're not seeing a fix anytime soon. Could we hack a workaround for Mageia 6?
(In reply to Rémi Verschelde from comment #15) > Could we hack a workaround for Mageia 6? Feel free to hack on this.
Is this bug still valid?
CC: (none) => marja11
This is still valid yes. IIRC Papoteur had started working on an edited version of our theme to simply remove the misleading flag icon.
Yes, See here: https://bugs.mageia.org/show_bug.cgi?id=16493#c12
CC: (none) => yves.brungard_mageia
Guys, do you confirm this is closed? I pushed a while ago Papoteur's patch, in my case I don't see any flag any more.
CC: (none) => eatdirt
(In reply to Chris Denice from comment #20) > Guys, do you confirm this is closed? I pushed a while ago Papoteur's patch, > in my case I don't see any flag any more. Thanks, Yves and Chris. I don't remember having seen a flag since many weeks ago... closing. Please reopen if you still see the flag.
Resolution: (none) => FIXEDStatus: ASSIGNED => RESOLVED