We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

I have a crash using a custom keyboard layout

  • 4 antwoorde
  • 2 hierdie probleem
  • 1 view
  • Laaste antwoord deur Matt

more options

Typing a command+key shortcut with at least some custom keyboard layouts crashes Thunderbird. I'm involved with the development of custom keyboard layouts, so would like to know what is going on. It seems, from the backtrace, that the event isn't coming through correctly with all information, but it's all hidden in internals.

Does anyone know where I can look (more specifically than "in the source") to see what's happening?

Typing a command+key shortcut with at least some custom keyboard layouts crashes Thunderbird. I'm involved with the development of custom keyboard layouts, so would like to know what is going on. It seems, from the backtrace, that the event isn't coming through correctly with all information, but it's all hidden in internals. Does anyone know where I can look (more specifically than "in the source") to see what's happening?
Aangehegde skermkiekies

Gekose oplossing

The problem appears to be that the keyboard layout in its XML form has state names that are all numeric. Changing the state names fixes the problem. I have opened a bug with Apple about it.

Lees dié antwoord in konteks 👍 0

All Replies (4)

more options
more options

OK, further investigation shows it's not just Thunderbird, but also Firefox. In Firefox, exactly the same error occurs. It also happens in Safari, the same error code but different backtrace, so it looks like it is a Mac problem rather than a Mozilla one.

more options

Gekose oplossing

The problem appears to be that the keyboard layout in its XML form has state names that are all numeric. Changing the state names fixes the problem. I have opened a bug with Apple about it.

more options

Thanks for the feedback. I have marked the thread solved, more to allow search engines to index it than because if actually contains a real resolution. Issues like these so often do not appear in search results because they are not "Solved" and I feel all information is relevant to these sorts of issues.