Not working in mojave?

[glaesser]

Installs just fine on 10.14.3, but just doesn't do anything (yes have copied/configured settings file, and even tried higher and lower ms values + verified my keycode). I have exactly the same issue with the repeating "n" key on a 2017 macbook pro, and it's driving me insane.

[johanbaath]

@glaesser I just verified that it works fine in Mac OS X Mojave. Did you follow the instructions exactly as described? Did you forget to move the settings.sample.json to settings.json?

[glaesser]

Unfortunately I did not, just double checked again and both files exist (as I write this, n is repeating multiple times). How can I help debug this further?

[johanbaath]

You can run /usr/local/bin/keyblock with sudo in your terminal, what output does it give you?

[glaesser]

Certainly:

M:keyblock m$ sudo /usr/local/bin/keyblock Password: Event tap created. Intercepting events...

[johanbaath]

While that is running, try pressing n multiple times fast. Set the delay in your settings.json to like 250 and you should notice that it blocks keystrokes. Does it do that? If that works, you should shut down the process and run: sudo launchctl start com.johanbaath.keyblock. Then make sure it's running looking in your Activity Monitor or using ps.

Let me know!

[johanbaath]

Also, you should download: https://manytricks.com/keycodes/ and make sure you are using the correct keyCode! Very important.

[glaesser]

1. Whatever I try, nothing with "key" or "com.joh..." shows up in activity monitor? What is the process called that should be showing?

2. I had already verified the keycode using that utility, it's "45" for the "n" key, exactly like in your case.

[johanbaath]

It seems Mojave has tighter security regarding launching global daemons with root access. I have no easy workaround as of now, but I suggest you run it manually in a terminal with sudo. That should work. Does it?

[glaesser]

It seems Mojave has tighter security regarding launching global daemons with root access. I have no easy workaround as of now, but I suggest you run it manually in a terminal with sudo. That should work. Does it?

You mean simply run sudo /usr/local/bin/keyblock in terminal instead of the launch daemon?

[johanbaath]

Yes, and keep it running.

[glaesser]

Thanks, I will do that and see how it goes :)

[glaesser]

Just reporting back here - this has been working great, no more issues, sanity restored. Thank you very much! If you ever get the daemon working in Mojave, that'd be a bonus :)