LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10600000 ), so we cannot talk to it. amework: coreservicesd process died attempting to reconnect but future use may result in erroneous behavior.Īnd that after that there were problems talking to coreservicesd: 14:17:45. Looking into the logs a bit more I found the earliest libdispatch crash, and before that found that coreservicesd had died: 14:17:43. I should note that I've rebooted several times and verified the disk permissions and the disk. I'm beginning to wonder if there's a permissions problem, or corruption of an important library. The common text in the diagnostic messages is: Exception Type: EXC_BAD_INSTRUCTION (SIGILL)Įxception Codes: 0x0000000000000001, 0x0000000000000000Ĭrashed Thread: 1 Dispatch queue: -managerīUG IN CLIENT OF LIBDISPATCH: Do not close random Unix descriptors Of these, only the last is non-Apple software!

I had a look in the Console app at the diagnostic messages and I noticed a pattern, that a number of apps were reporting 'BUG IN CLIENT OF LIBDISPATCH'. I followed the steps at which don't seem to work for me, although I can connect if I use the command line with sudo : sudo vpnclient connect MyProfile I've also been having problems (at first seemingly unrelated) with the horrible Cisco VPN client, which started giving me this error: Error 51: Unable to communicate with the VPN subsystem I've attempted the fix at /kb/HT1747 but it failed. It fails with a crash dialog reporting 'AppleMobileDeviceHelper quit unexpectedly' and an error dialog 'iTunes was unable to load dataclass information from SyncServices. Most noticably, iTunes no longer syncs with my iPhone. In the last day I have started having a lot of brokenness on my Mac (MacBook Air running Mac OS X 10.6.2 with all software updates).

Bug in libdispatch client high sierra