Custom keyboard layout not appearing in System Settings — Sequoia 15.6.1 / Ukulele 3.6.1

9 views
Skip to first unread message

Hüse Roland

unread,
Jun 2, 2026, 10:33:35 AM (3 days ago) Jun 2
to Ukelele Users
I'm writing to report a bug with Ukulele 3.6.1 on macOS Sequoia 15.6.1.

I have a custom keyboard layout (Rovas-HUN) that I originally created in Ukulele in 2023. After reinstalling it on my Mac, it does not appear in System Settings → Keyboard → Input Sources → Others. Only 'Unicode Hex Input' appears under Others.

I have tried the following:
- Installing via Ukulele 3.6.1 (File → Install for Current User)
- Manually copying the .keylayout file and .bundle to both /Library/Keyboard Layouts/ and ~/Library/Keyboard Layouts/
- Fixing ownership and permissions via Terminal (chown root:wheel, chmod 644)
- Clearing input source caches (com.apple.HIToolbox.plist, cfprefsd)
- Multiple restarts and logouts

None of these methods made the layout appear. The bundle and keylayout file are correctly placed and owned, but macOS does not register them as available input sources.

I am attaching my .keylayout file for reference. Please let me know if this is a known issue with Sequoia 15.6.1 and if there is a workaround or fix coming.

Thank you,
Roland

John Brownie

unread,
Jun 2, 2026, 10:40:36 AM (3 days ago) Jun 2
to ukelel...@googlegroups.com
Hi Roland,

Sorry that you’re having trouble! The custom keyboard layout didn’t come through with your message. I don’t know if that’s related to the security settings where I have to approve the first post from each author to prevent spam, but you can try again.

One trouble-shooting trick is to force the keyboard layout file to be saved as ASCII only, encoding all non-ASCII characters with their XML hex encoding. This is done in the Settings window. Activate the option “XML has code points”, and save the file again. This sometimes works because certain Unicode sequences apparently cause Apple’s keyboard compiler to fail, and doing it in strict ASCII gets around that.

Hope that helps, but let us know either way!

John

--
You received this message because you are subscribed to the Google Groups "Ukelele Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukelele-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ukelele-users/5aebe728-6ef7-4d08-aea8-7de4b0a6893cn%40googlegroups.com.

John Brownie

unread,
Jun 2, 2026, 1:15:43 PM (2 days ago) Jun 2
to ukelel...@googlegroups.com
Just to let you know that I solved this off-line. Somehow there were some references to a state with an empty string as the name, which is illegal, so it didn’t compile. Hand-editing the XML file fixed it, but I’m none the wiser about how it got that way in the first place!

John
Reply all
Reply to author
Forward
0 new messages