kext drivers found in /System/Library/Extensions or /Library/Extensions. The suggested work-around was to uninstall AirParrot, especially any of its. For this reason, I had AirParrot installed on my Mac Pro but not my other Macs. It’s especially useful for older Macs that are not compatible with AirPlay mirroring. The cause turned out to be AirParrot-a program that mirrors a Mac’s display to Apple TV via AirPlay. It reported that AirPlay mirroring no longer worked for some users after updating to OS X 10.9.2. One Apple Support Communities thread especially grabbed my attention.
While waiting for Apple’s return call, I did some further digging into problems with OS X 10.9.2. He promised Apple would get back to me in a few days, after analyzing the results. The support person next had me download an app called Capture Data which collects and sends data from your computer to Apple. They had me perform one additional diagnostic test: remove third-party kext files from the /System/Library/Extensions folder. I never bothered to try this.ĪirParrot, AirPlay mirroring, and the missing camera solutionĪdmitting defeat, I called Apple Technical Support. At this point, I searched the web and found a report that claimed deleting .plist from /System/Library/LaunchDaemons would stop the crashing but (as I expected) not restore the camera. Surprisingly, neither the killall command in Terminal nor a Force Quit from Activity Monitor could terminate the process. This meant that killing the process might stop the crashes but would not bring back the camera. I figured that, while this VDCAssistant file was likely involved in the missing camera mystery, it was not the root cause. It revealed that a process called VDCAssistant was crashing at a rate of about ten times a second! I located this OS X file buried in /System/Library/Frameworks/amework/Versions/A/Resources/VDC.plugin/Contents/Resources.Ĭonsole’s system.log shows a steady stream of VDCAssistant crashes. If anything, checking the logs only succeeded in raising my anxiety. Perhaps OS X’s Console logs could identify the culprit file? Nope. As a start in this search, I temporarily disabled the contents of various startup-related folders in the /Library folder: Extensions, LaunchDaemons, LaunchAgents, Preferences and StartupItems. Unfortunately, a Safe Boot offers no way to determine precisely what those files might be. Rather, the evidence suggested that the culprit was a file (or files) either in the Mac Pro’s /Library or /System/Library folders.
Still, this pretty much ruled out a hardware failure as the cause of the problem. After restarting normally, the camera vanished again.
It was only a temporary respite, however. One thing did succeed in bringing the Cinema Display’s camera back to life: a Safe Boot.
0 kommentar(er)
