Bug 1372300 - GDM does not use the keyboard layout which is selected
Summary: GDM does not use the keyboard layout which is selected
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedBlocker
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-01 11:21 UTC by Kamil Páral
Modified: 2017-12-12 10:21 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:21:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
bug demonstration video (354.24 KB, application/octet-stream)
2016-09-01 11:21 UTC, Kamil Páral
no flags Details
journal snippet during log out -> failed log in -> successful log in (3.96 KB, text/plain)
2016-09-01 11:22 UTC, Kamil Páral
no flags Details
rpm -qa output (49.73 KB, text/plain)
2016-09-01 11:22 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2016-09-01 11:21:04 UTC
Description of problem:
This has been first reported here:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/NS4KX6XQ2ULBUFY72OSQAL7BLALOJ4TP/

I tried to reproduce and found the same or a very similar bug. If I have two keyboard layouts configured in GDM, russian and english, even though english is selected, it is not being used (but probably russian). After I use the selector to switch to russian and back to english, then finally english layout is used and I can log in with my ascii password.

Version-Release number of selected component (if applicable):
gdm-3.21.4-1.fc25.x86_64
gdm-3.21.90-2.fc25.x86_64
gnome-shell-3.21.4-1.fc25.x86_64
gnome-shell-3.21.90.1-1.fc25.x86_64

How reproducible:
I haven't tried multiple installs, but on the installed system, I can reproduce it every time I log out. When I reboot, gdm shows russian layout by default, so in that case I have to switch to english and it works. But when I log out, it shows english layout by default, and there the problem occurs until I double-switch the layout.

Steps to Reproduce:
1. install F25. Choose Russian language in anaconda, keep all defaults. In user creation spoke, switch to english layout, and create the user with ascii password.
2. boot to the installed system, go to system settings, change language (the first item) from russian to english. Confirm log out.
3. notice that gdm shows english layout as selected. try to log in. it will fail.
4. switch the keyboard layout to russian and back to english. try to log in. it will work.

Actual results:
gdm shows english layout as selected while in reality it uses russian one

Expected results:
show exactly the one that is being used

Comment 1 Kamil Páral 2016-09-01 11:21:39 UTC
Created attachment 1196745 [details]
bug demonstration video

See the video to understand the needed workaround to log in.

Comment 2 Kamil Páral 2016-09-01 11:22:22 UTC
Created attachment 1196751 [details]
journal snippet during log out -> failed log in -> successful log in

Comment 3 Kamil Páral 2016-09-01 11:22:41 UTC
Created attachment 1196752 [details]
rpm -qa output

Comment 4 Kamil Páral 2016-09-01 11:25:48 UTC
I'd say this is a violation of:
"If a particular keyboard layout has been configured for the system, that keyboard layout must be used: 
 When logging in via the default login manager for a release-blocking desktop"
https://fedoraproject.org/wiki/Fedora_25_Final_Release_Criteria#Keyboard_layout_configuration

In this case, it seems the layout *is* actually being used, but a different layout is displayed as active, and therefore the users are confused why their password are being rejected.

Comment 5 Alexander Kolesnikov 2016-09-01 12:19:44 UTC
"4. switch the keyboard layout to russian and back to english. try to log in. it will work." - this workaround doesn't work for me, unfortunately.

Comment 6 Ray Strode [halfline] 2016-09-01 13:31:30 UTC
Rui, does this bug resonate for you?

Comment 7 Geoffrey Marr 2016-09-13 02:27:06 UTC
Discussed during the 2016-09-12 blocker review meeting: [1]

The decision to delay the classification of this as a bug was made as it's not entirely clear if this is a problem after a default Russian install or only after tweaking the keyboard layout order post-install. There are several people currently testing this bug.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-09-12/f25-blocker-review.2016-09-12-16.01.txt

Comment 8 Kamil Páral 2016-09-13 10:54:41 UTC
I wasn't able to reproduce this without any changes to the installed system. If I install Fedora with Russian language and en+ru keymap, but en keymap as the default one, this bug does not occur - en keymap is selected as default in gdm and it is also used.

This seems to be somehow related to the locale change performed in gnome-control-center.

Comment 9 Christian Stadelmann 2016-09-19 11:11:54 UTC
(In reply to Kamil Páral from comment #8)
> I wasn't able to reproduce this without any changes to the installed system.
> If I install Fedora with Russian language and en+ru keymap, but en keymap as
> the default one, this bug does not occur - en keymap is selected as default
> in gdm and it is also used.
> 
> This seems to be somehow related to the locale change performed in
> gnome-control-center.

Probably. After updating a F24 instance it now has switched to using the English layout although it used to have another (German) layout and I can't remember to have changed this.

Comment 10 Petr Schindler 2016-09-19 18:04:06 UTC
Discussed at 2016-09-19 blocker review meeting: [1]. 

We decided to delay the decision: We currently cannot find an appropriate criteria to block on, however this bug makes multilingual use of F25 unusable. We will delay the classification of this as a blocker until the criteria can be amended, we receive new info on this bug, or the bug is fixed.

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2016-09-19/

Comment 11 Geoffrey Marr 2016-09-26 23:40:52 UTC
Discussed during the 2016-09-26 blocker review meeting: [1]

The decision to classify this bug as a RejectedBlocker was made as the bug does not violate any Blocker-Criteria because it is triggered by post-install changes to the locale configuration, which the criteria do not cover.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-09-26/f25-blocker-review.2016-09-26-16.04.txt

Comment 12 Fedora End Of Life 2017-11-16 18:44:22 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 13 Christian Stadelmann 2017-11-16 22:54:58 UTC
I ran into this bug to, but by updating to Fedora 27 it vanished.

Comment 14 Fedora End Of Life 2017-12-12 10:21:19 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.