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 738576 - Custom keyboard layouts fail to load
Custom keyboard layouts fail to load
Product: gnome-settings-daemon
Classification: Core
Component: keyboard
Other Linux
: Normal normal
: ---
Assigned To: Rui Matos
Depends on:
Reported: 2014-10-15 13:42 UTC by Robbie Smith
Modified: 2019-03-20 11:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

The patched files I used for my custom layout. (66.51 KB, application/x-gzip)
2014-10-15 13:42 UTC, Robbie Smith
Diff of my customisations (3.25 KB, patch)
2014-10-16 16:11 UTC, Robbie Smith
none Details | Review

Description Robbie Smith 2014-10-15 13:42:08 UTC
Created attachment 288584 [details]
The patched files I used for my custom layout.

I've been trying to emulate the custom keyboard layout I put together with XKB on GNOME, and it doesn't work, despite the layout working perfectly fine with setxkbmap and xkbcomp. The layout is a variation on the US one, with some extra third-level keys which I find useful. Adding the files in /usr/share/X11/xkb/symbols/ and amending the rules in /usr/share/X11/xkb/rules/{base,evdev}.{xml,lst} result in the layout showing up in the Input Sources settings, but the layout itself isn't applied. 

Calling `setxkbmap -layout <name> -variant <variant> -option <options>` in the terminal loads the layout, but if more than one Input Source is installed, switching to a different layout will result in you being unable to switch to your custom one. I'd like to be able to switch between my own layout and mozc (for Japanese input).

Setting the XKB strings manually in Dconf Editor has the same result as adding it via Input Sources.

The log viewer reports error messages warning that keyboard-plugin couldn't find XKB source '<name>'.

Interestingly enough, it isn't just my custom layout that results in this behaviour (so you can confirm it without making the customisations I did!). If you add APL (all variants) as an input source, for example, you'll get the same results, albeit for a OOTB layout. Another layout I found to have this bug/issue/feature is EurKEY.


System Details
OS/Distro: Arch Linux x86_64, Linux 3.16.4
GNOME version: 3.12.2
Comment 1 Robbie Smith 2014-10-15 13:42:49 UTC
This bug may or may not be related:
Comment 2 Rui Matos 2014-10-16 08:54:52 UTC
Can you submit a diff against the original files instead of a zip file?
Comment 3 Robbie Smith 2014-10-16 16:11:40 UTC
Created attachment 288700 [details] [review]
Diff of my customisations
Comment 4 Rui Matos 2014-10-16 16:55:57 UTC
(In reply to comment #3)
> Created an attachment (id=288700) [details] [review]
> Diff of my customisations

Shows up fine here on 3.14. Can you try that?
Comment 5 Robbie Smith 2014-10-17 05:38:27 UTC
I just upgraded to 3.14 on my testing desktop, and can confirm that all the keyboard layouts included by default that I tested (APL, EurKEY, Coeur d'Alene Salish, etc) show up. My modifications to the US layout don't though, even though it displays in the menu in Input Sources and the keyboard layout image gets rendered.
Comment 6 Rui Matos 2014-10-17 08:57:59 UTC
Are you saying that your layout shows up in the gnome-shell panel (top right) and doesn't show up in gnome-control-center?

If it shows up in the panel, are you able to switch to it and does it work?
Comment 7 GNOME Infrastructure Team 2019-03-20 11:18:42 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: