Ukulele issues

177 views
Skip to first unread message

Jonas

unread,
Jul 4, 2022, 5:16:45 AM7/4/22
to Ukelele Users
Hello everyone,

I wanted to remap a few keys and tried ukulele. But it does not really work well. After making the layout and installing it, then logging out and in, I can find the layout in "Others".

Unfortunately, it didn't go very well, now I have two of them in the layouts called with the same name (one is an older version I did a mistake in). When uninstalling it through ukulele the app "quit unexpectedly" and it still stays in the layout preferences. It is greyed out now.

But even when I make it work the custom keys are not translated into text (even if the keyboard viewer actually shows the symbol that I want to write - it just doesn't appear).

I feel all the install / uninstalling might have messed it up a bit. How can I start from scratch and remove all layouts from the system?

Jonas

unread,
Jul 4, 2022, 5:17:31 AM7/4/22
to Ukelele Users
Forgot to mention, I got Mac 12.4 (M2) and Ukulele 3.5.6

Jonas

unread,
Jul 4, 2022, 6:02:12 AM7/4/22
to Ukelele Users
I had an issue with the "zombie keyboards" as somebody mentioned in another thread. I was able to get rid of them by uninstalling them through the organizer and then restarting in safe mode to clear cache.

However, the issue persists that they symbols are simply not written into text despite the "Keyboard Viewer" of MacOS clearly showing the correct symbol. I also tried to make a keyboard as collection, but this does also not help.

As a general issue, the organizer frequently crashes

Gé van Gasteren

unread,
Jul 4, 2022, 6:13:20 AM7/4/22
to ukelel...@googlegroups.com
Hi Jonas,

Thanks for the good news about Safe Boot.
The advantage of putting keyboard layouts into a Collection is that you assign them a language and then they don’t show up in Others anymore, but under their proper language.

If your custom layout doesn’t work properly & the Organiser crashes frequently, maybe the layout is somehow broken.
Can you upload/attach it here, so I can try out how it behaves on my system?
Maybe you can also give some idea of what you have changed, so I know what to look for :-)

--
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 on the web visit https://groups.google.com/d/msgid/ukelele-users/19730f78-0808-4735-92d7-a0ee51bb09afn%40googlegroups.com.

Sorin Paliga

unread,
Jul 4, 2022, 6:28:56 AM7/4/22
to ukelel...@googlegroups.com
Such crashes sometimes indicate a problem with the system, many users do not have the patience to read the manual and make “illegal acts”, in most cases not mentioning details about what and how they had done it. 
A keyboard layout works and interferes with the system, so an illegal code or various other situations may indeed lead to crashes.

Tom Gewecke

unread,
Jul 4, 2022, 6:37:23 AM7/4/22
to ukelel...@googlegroups.com


> On Jul 4, 2022, at 6:02 AM, Jonas <gehrlei...@gmail.com> wrote:
>
>
> However, the issue persists that they symbols are simply not written into text

Could you give examples of the symbols and the apps where this is happening?

Jonas

unread,
Jul 4, 2022, 6:41:16 AM7/4/22
to Ukelele Users
Hi Tom!
Yes, I just figured out that for whatever reason MacOS does not allow the command key to actually lead to a symbol output. I mapped command + 8 to [ but then of course it didn't work. After I found out, I swapped the modifiers in the MacOS settings and now it works!
The constant crashing of the organizer seems to be unrelated to this.
So, for me everything works now, thanks a lot for this tool!
Should I leave this thread ? I feel it does not contribute much, but maybe somebody else realizes that command cannot be mapped to key output?

Jonas

unread,
Jul 4, 2022, 6:41:40 AM7/4/22
to Ukelele Users
Thanks for the reply. It seems the crash is unrelated and it still works even if the organizer crashes

Tom Gewecke

unread,
Jul 4, 2022, 6:44:32 AM7/4/22
to ukelel...@googlegroups.com


> On Jul 4, 2022, at 6:41 AM, Jonas <gehrlei...@gmail.com> wrote:
>
>
> Yes, I just figured out that for whatever reason MacOS does not allow the command key to actually lead to a symbol output.

Right, Mac’s normally only use option and option shift for special characters, not command or control.

Sorin Paliga

unread,
Jul 4, 2022, 6:47:21 AM7/4/22
to ukelel...@googlegroups.com

On 4 Jul 2022, at 13:41, Jonas <gehrlei...@gmail.com> wrote:

ut maybe somebody else realizes that command cannot be mapped to key output?

This is specified in the manual, but most people do not read it, they prefer to ask before reading. And there are many other details in that manual. 
As a rule of thumb: the Command (and Ctrl) key(s) is/are for system commands, Option/Alt key for keylayouts.

John Brownie

unread,
Jul 4, 2022, 6:49:03 AM7/4/22
to ukelel...@googlegroups.com
I'd love to hear someone describe what leads up to a crash in the
organiser, since I've never been able to get a crash to happen in my
testing! A crash log would also be nice, but it's increasingly hard to
find where they are...

John (developer of Ukelele)
--
John Brownie
Mussau-Emira language, New Ireland Province, Papua New Guinea
Turku, Finland

Gé van Gasteren

unread,
Jul 4, 2022, 6:50:33 AM7/4/22
to ukelel...@googlegroups.com
On Mon, Jul 4, 2022 at 12:41 PM Jonas <gehrlei...@gmail.com> wrote:
Thanks for the reply. It seems the crash is unrelated and it still works even if the organizer crashes

In another thread, John wrote that crash reports could be helpful. So if you like, you can upload one.
Here’s John’s text:
Yes, it would help me to hear that the Organiser crashes. In particular, any crash logs would be really helpful in seeing what is going wrong. Where they are found varies depending on the version of macOS you are running, but looking in ~/Library is a good starting point. With Monterey, it looks like DiagnosticReports is the key folder, but /var/log is probably more useful. Otherwise, looking in the Console app should find them. I think that they might get pruned, perhaps at reboot, so finding the log shortly after the crash is the best bet. A description of the steps leading to the crash is best.

Jonas

unread,
Jul 4, 2022, 9:26:33 AM7/4/22
to Ukelele Users
yes, I feel bad about not reading the manual before. I guess that will never change - manuals are an outdated concept xD I will check for the crash report. Btw. one thing that really works well is the safe mode reboot. Whenever there is some dead layout stuck in the keyboard settings that you cannot get rid of by uninstalling it, you can do a safe reboot and its cleared.

Gé van Gasteren

unread,
Jul 4, 2022, 9:30:37 AM7/4/22
to ukelel...@googlegroups.com
On Mon, Jul 4, 2022 at 3:26 PM Jonas <gehrlei...@gmail.com> wrote:
Whenever there is some dead layout stuck in the keyboard settings that you cannot get rid of by uninstalling it, you can do a safe reboot and its cleared.

I’m not sure it matters, but I *always* install with the Organiser and I *never* have such "dead layouts"…

Sorin Paliga

unread,
Jul 4, 2022, 9:34:53 AM7/4/22
to ukelel...@googlegroups.com


On 4 Jul 2022, at 16:26, Jonas <gehrlei...@gmail.com> wrote:

manuals are an outdated concept

Well, definitely yes, pray God answering questions in a forum may not be outdated too one good day. 

Jonas

unread,
Jul 4, 2022, 9:45:20 AM7/4/22
to Ukelele Users
soon enough some AI can give the answers that are embedded in a manual :)
Reply all
Reply to author
Forward
0 new messages