Bug 1202046 - GDM selects bad default keyboard layout
Summary: GDM selects bad default keyboard layout
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 22
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-14 18:20 UTC by Couret Charles-Antoine
Modified: 2016-07-19 19:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 19:33:10 UTC
Type: Bug


Attachments (Terms of Use)

Description Couret Charles-Antoine 2015-03-14 18:20:21 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Couret Charles-Antoine 2015-03-14 18:26:40 UTC
Oops, I pushed bug by accident.

When I boot my computer, the GDM displays in right corner the keyboard layout. I have configured fr and fr2 in gnome-control-center for login screen. Even if I have fr and fr2 suggested by GDM, by default, it is "en" keyboard layout. But I have nothing about that.

Normally, en is not suggested and fr is the default keyboard layout.

And GDM forgot the last choice of keyboard layout if I reboot.
GDM version : 3.15.91.2

Comment 2 Fedora End Of Life 2016-07-19 19:33:10 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.