Very Odd Error High Sierra - Need Help - Anyone up for the challenge?
Talk about learning fast especially Terminal which Id never touched before in my life.
I've Just updated my daughters Mid 2010 iMac from El Capitan to High Sierra.
It originated a very odd Mac Bluetooth Keyboard Error which Im trying to track down. 9 keys on the Keyboard do not now register, but this only happens for one of the 5 User profiles on the machine and then only after the initial login password screen as 2 of the failed characters were in the password.
The 9 keys are m . 8 9 u i o k l (but suspect that not relevant)
I first thought it was hardware but the keyboard works fine for all other profiles even a new profile set up specifically to test. Also works ok on another mac. Keyboard input was fine pre update.
I have reset all bluetooth, PRAM and SMC resets on the Mac with no joy.
Virtual Keyboard entry is unaffected (using it to bypass problems within the affected profile)
Im now trying to see differences between the new user login set up under El Capistan prior to High Sierra Upgrade and the Problem Users (both have admin level).
Ive listed launchctl (launchctl list) and compared the outputs at name level ie if process name matches on both logins. Only a few differences but to my limited knowledge these seem explainable. ( ie first two items below I have no idea what the process is on either login and assume that the preceding number is simply the different user .)
38d37
< com.apple.cvmsCompAgent3425AMD_i386
39a39
> com.apple.cvmsCompAgent3425AMD_i386
49a50
> com.apple.xpc.launchd.oneshot.0x10000001.Safari
96d96
< com.apple.Siri.agent
108a109
> com.apple.Terminal.3992
135a137
> com.apple.siri.context.service
141d142
< com.apple.Notes.1080
184d184
< com.apple.imdpersistence.IMDPersistenceAgent
185a186
> com.apple.imdpersistence.IMDPersistenceAgent
187c188
< com.apple.Notes.datastore
---
> com.apple.KeyboardViewer.3932
285d285
< com.apple.Terminal.1104
292a293
> com.google.keystone.user.agent
320a322
> com.apple.Safari.History
Login Start up entries for both are empty so nothing different there.
The only difference I can see so far is Google Auto update on the affected profile. so will delete Google and test again.
In the meantime I wondered if anyone on this forums has ever seen or heard of such an odd error and could offer any pearls of wisdoms / possible surgical solutions before I go in with the big hammer and wipe profiles or possibly complete machine and start again.
Cheers
David