After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 634719 - GDM incorrectly handles keyboard layouts with variants
GDM incorrectly handles keyboard layouts with variants
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
2.32.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks: 622305
 
 
Reported: 2010-11-12 21:39 UTC by Andrew Zabolotny
Modified: 2018-05-24 10:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andrew Zabolotny 2010-11-12 21:39:15 UTC
I use a custom keyboard layout, which is set up by X11 as:

Option      "XkbLayout" "zap(us_ro),zap(ru)"

Now with latest gnome when entering a password on GDM screen it will allow me to choose either one (although only the second "works", utf-8 characters are not allowed in passwords?). But in ~/.dmrc I'm left with:

Layout=zap

This is wrong, because the variant is missing, and the "zap" layout with no variant is empty. This, in turn, has the effect of adding the "zap" layout unconditionally to my keyboard layout set up (e.g. in System->Parameters->Keyboard->Layouts I will see *three* layouts: "zap(us_ro)", "zap(ru)" and "zap", and ISO_Next_Group will cycle between three groups rather than two, one of which is unusable.

This problem will arise with any layouts using variants - e.g. for example users which will want the "ru(typewriter)" layout will get in the end two layouts - ru and ru(typewriter) due to the annoying habbit of the gnome-settings-daemon's keyboard plugin to append GDM's layout to user settings at every login.
Comment 1 GNOME Infrastructure Team 2018-05-24 10:31:24 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/44.