為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

I have a crash using a custom keyboard layout

  • 4 回覆
  • 2 有這個問題
  • 1 次檢視
  • 最近回覆由 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?
附加的畫面擷圖

被選擇的解決方法

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.

從原來的回覆中察看解決方案 👍 0

所有回覆 (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

選擇的解決方法

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.