-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Norman not showing as an input option on macOS’s login screen? #15
Comments
I don't have any ideas on what the problem is here, but I can confirm I also see this with both Norman and Workman layouts. I could have sworn it used to be there, but maybe not? |
Yes, it used to be there. The Users & Groups preference checkbox was the big key to showing it after it was activated by any user. None of the keyboard layouts from the Norman challenge are showing for me anymore in the login menu. I imagine this is a "security" fix for running userland files for a login prompt. Maybe Apple is concerned about a keyboard bundle somehow logging passwords? I'm not excited about the possibility of having to sign the bundle with a $99/yr developer account. |
If it comes to that, I’d be happy to chip in toward that cost if you were to set up a GoFundMe or something. (It’d be the least that I could do to thank you for all your hard work in creating this.) |
I don't yet know if that's the fix or not. |
Try as I might, I can’t seem to get Norman to show up as an option on macOS’s login screen. I’ve followed the steps from the readme as best as I can:
When I go to log in, there’s an Input menu, but I don’t see “Norman” in the main list of input sources or under the list of “Other Input Sources”:
Would you happen to have any ideas there?
(Just for completeness: I’m seeing this on my MacBook Pro, which is running El Capitan 10.11.6, and I’m also seeing this on my Mac mini, which is running High Sierra 10.13.4.)
P.S. Norman works fine once I log in (and in fact, I’m wrote this with Norman). It only seems to be on the login screen where I’m running into this.
The text was updated successfully, but these errors were encountered: