gdm after suspend loginscreen has wrong keyboard layout

Bug #1727980 reported by Sven on 2017-10-27
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Undecided
Unassigned

Bug Description

system information:
===================
Ubuntu 17.10, wayland, gdm3 : 3.26.1-3ubuntu3, on lenovo yoga 14

ch layout configured both: system wide and in desktop configuration:
gsettings get org.gnome.desktop.input-sources sources :
[('xkb', 'ch')]

and
cat /etc/default/keyboard :
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="thinkpadz60"
XKBLAYOUT="ch"
XKBVARIANT="de_nodeadkeys"
XKBOPTIONS="lv3:ralt_switch"
BACKSPACE="guess"

expected:
=========
- ch-layout on initial login screen (after boot)
- ch-layout on lock login screen (after locking the screen)
- ch-layout on desktop
- ch-layout on login screen after suspend

what happens:
=============
OK: ch-layout on initial login screen (after boot)
OK: ch-layout on lock login screen (after locking the screen)
OK: ch-layout on desktop
NOT OK: us-layout on login screen after suspend

Only the login after suspend is affected.

additional information:
Setting XKBLAYOUT="ch,us" gives the indicator on login screen to switch the layout, but not on the login screen which is presented after suspend.

Sven (mcsv) on 2017-10-27
tags: added: gnome-17.10 sus
tags: added: suspend-resume
removed: sus
Gunnar Hjalmarsson (gunnarhj) wrote :

I just tested with two layouts in /etc/default/keyboard, and I have a working keyboard indicator also on the login screen after suspend.

Gunnar Hjalmarsson (gunnarhj) wrote :

Also, I see now that you have a variant in /etc/default/keyboard (ch+de_nodeadkeys) but not in the desktop configuration. That's really two different layouts. Can it possibly be that what you think is the us layout is actually ch+de_nodeadkeys?

No, I can login, when I use the corresponding keys in the us-layout (I
learned it by heart)

Gunnar Hjalmarsson <email address hidden> schrieb am Fr., 27. Okt.
2017 um 11:11 Uhr:

> Also, I see now that you have a variant in /etc/default/keyboard
> (ch+de_nodeadkeys) but not in the desktop configuration. That's really
> two different layouts. Can it possibly be that what you think is the us
> layout is actually ch+de_nodeadkeys?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1727980
>
> Title:
> gdm after suspend loginscreen has wrong keyboard layout
>
> Status in gdm3 package in Ubuntu:
> New
>
> Bug description:
> system information:
> ===================
> Ubuntu 17.10, wayland, gdm3 : 3.26.1-3ubuntu3, on lenovo yoga 14
>
> ch layout configured both: system wide and in desktop configuration:
> gsettings get org.gnome.desktop.input-sources sources :
> [('xkb', 'ch')]
>
> and
> cat /etc/default/keyboard :
> # KEYBOARD CONFIGURATION FILE
> # Consult the keyboard(5) manual page.
> XKBMODEL="thinkpadz60"
> XKBLAYOUT="ch"
> XKBVARIANT="de_nodeadkeys"
> XKBOPTIONS="lv3:ralt_switch"
> BACKSPACE="guess"
>
> expected:
> =========
> - ch-layout on initial login screen (after boot)
> - ch-layout on lock login screen (after locking the screen)
> - ch-layout on desktop
> - ch-layout on login screen after suspend
>
> what happens:
> =============
> OK: ch-layout on initial login screen (after boot)
> OK: ch-layout on lock login screen (after locking the screen)
> OK: ch-layout on desktop
> NOT OK: us-layout on login screen after suspend
>
> Only the login after suspend is affected.
>
>
> additional information:
> Setting XKBLAYOUT="ch,us" gives the indicator on login screen to switch
> the layout, but not on the login screen which is presented after suspend.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1727980/+subscriptions
>

Sven (mcsv) wrote :

It looks as if I solved it by reconfiguring input settings from within gnome ("Eingabemethoden" / im-config). But I really don't know what happened nor why initial login, gnome, gnome-terminal and login after suspend use different keyboard settings / configurations.

So maybe it's not a bug, but the request for a possibility to configure keyboard layout for everything in one place.

Sven (mcsv) wrote :

Nope... now, an hour later, the config seems to be totally broken... now all my login screens have us layout... I am checking and keep this updated

Gunnar Hjalmarsson (gunnarhj) wrote :

On 2017-10-27 14:36, Sven wrote:
> So maybe it's not a bug, but the request for a possibility to
> configure keyboard layout for everything in one place.

Actually there is such a place:

Settings -> Region & Language

From there you can add and remove "input sources" for your user.

If you click the "Login Screen" button at the top right of the window, you can do the same thing system wide (i.e. changing input sources in that mode will make changes to /etc/default/keyboard).

> Nope... now, an hour later, the config seems to be totally broken...
> now all my login screens have us layout...

That's not good. To determine if this really is a bug, we'd need a reproducible step-by-step case.

I'd advise you to make use of the GUI mentioned above. Change things back and forth a couple of times, to make sure that everything is in sync, and then reboot.

Please let us know if that makes a difference.

Changed in gdm3 (Ubuntu):
status: New → Incomplete
Sven (mcsv) wrote :

Thanks for this hint - I'll keep it in mind.

Actually I cannot reproduce this anymore - seems to have been a local problem.
Here is what I did to solve it: I reset the whole gnome config (dconf reset -f /org/gnome/), changed the layout to "de" and then back to "ch-de". Now it works as expected.

I think we can close this case. Sorry for stealing your time!

Gunnar Hjalmarsson (gunnarhj) wrote :

Ok, no problem. Thanks for letting us know that you sorted it out.

Changed in gdm3 (Ubuntu):
status: Incomplete → Invalid
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1652618, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers