Q: After Upgrading to 10.9.2 Isight is not working

I delete all apps mentioned above,Airdisplay, Airparrot, iDisplay, and didn't work.

Before a clean install (i really need one), but is a pain to me reinstall everything.... I thought I should try one more thing.

Than I remove VMWARE and PARALLELS. (only the app, not the virtual machine - keep the machine until appear a solution...)

Solved! Everything back to normal. iSight back to FaceTime and Skype.

Is a try to people who already try everything.

I have Parllels working.  I had to uninstall AirDisplay and reboot.  THEN I had to start the camera with any 3rd party software (I used TeamViewer Preferences / Video) when the camera led turned on and I saw image I was able to use FaceTime, Photo Booth, and any other webcam application.

Seems to affect software like AirDisplay, Air Play and any that creates a "display" wonder if Apple warned developers of this?  Or if they even care?  I just bought AirDisplay to use both my mac displays as 2nd and 3rd for my Windows 8 machine, now I'm back down to 1 on PC and 2 on Mac...  Do we have to accept this or what?  Bleh...

Humbs wrote:

 

I delete all apps mentioned above,Airdisplay, Airparrot, iDisplay, and didn't work.

 

Before a clean install (i really need one), but is a pain to me reinstall everything.... I thought I should try one more thing.

 

Than I remove VMWARE and PARALLELS. (only the app, not the virtual machine - keep the machine until appear a solution...)

 

Solved! Everything back to normal. iSight back to FaceTime and Skype.

 

Is a try to people who already try everything.

I'm almost 100% certain that VMware and Parallels have nothing to do with it -- I use Parallels and it's working just fine. I do have a theory: uninstalling VMware and Parallels caused the Extensions folders to be "touched", telling OS X to re-scan them, causing it to notice that the incompatible kexts are now gone. This seems to be a necessary step. Others have done it using the "touch" terminal command. Opening the folder in the Finder does the same thing.

edgararroyo wrote:

 

I have Parllels working.  I had to uninstall AirDisplay and reboot.  THEN I had to start the camera with any 3rd party software (I used TeamViewer Preferences / Video) when the camera led turned on and I saw image I was able to use FaceTime, Photo Booth, and any other webcam application.

 

Seems to affect software like AirDisplay, Air Play and any that creates a "display" wonder if Apple warned developers of this?  Or if they even care?  I just bought AirDisplay to use both my mac displays as 2nd and 3rd for my Windows 8 machine, now I'm back down to 1 on PC and 2 on Mac...  Do we have to accept this or what? 

I've since discovered that the "seed note" on the developer preview of 10.9.2 asked developers to give particular attention to graphics drivers.

Spudboy2012 wrote:

 

Has anyone tried AirParrot 1.5.4? Does it continue to have same issues? Thanks for any info.

Yes. All the evidence so far is that the bug is in 10.9.2 itself, not in AirParrot.

Vinnie1vinnie wrote:

 

Hey I'm new to the mac and can't seem to find the "Extension" folder in library. A little guidence please

Did you make sure you're looking in the correct Library folder? There are several ones:

• /System/Library/
• /Library/
• ~/Library/

( ~ = your home folder)

It looks to me like those apps may be using a deprecated or unofficial method to get a display so it may not be a bug in OS-X, just that those apps hadn't updated to the new interface. Of course, I wouldn't expect anything to crash as a result of that so Apple has some work to do regardless. But, those apps may still not work after Apple's done it's fix.

27.02.14 02:27:00,272 VDCAssistant[4350]: CGSDisplayID: App trying to enumerate [0 to CGSGetNumberOfDisplays()] instead of using CGSGetDisplayList().  Compensating...

27.02.14 02:27:00,272 VDCAssistant[4350]: Client is attempting to access a display by index (1) instead of display ID.

Yeah, but it puzzles me that Apple didn't advise these developers about the Display change?  Big developers should have a notice or warning that someting is changing no?   I develop for iOS in Xcode and I get the warnings every time there is an iOS framework update, why can't they do the same with OS X?  I have a Mac Pro with a GeForce GTX 470 1280MB.  The machine booted fine with graphics and sound through the HDMI, I don't think it was my GFX card this time, I downloaded the latest drivers and I believe CUDA is integrated in 10.9?

edgararroyo wrote:

 

Yeah, but it puzzles me that Apple didn't advise these developers about the Display change?  Big developers should have a notice or warning that someting is changing no?   I develop for iOS in Xcode and I get the warnings every time there is an iOS framework update, why can't they do the same with OS X?

Xcode does do that for OS X apps and has done so since before iOS existed. That, and the fact that the seed notes for the 10.9.2 developer preview expressly note to look at graphics drivers, makes me think that Apple changed something under the hood and inadvertently broke something.

I received this information from AirParrot support:

"You can install AirParrot and mirror to your AppleTV. The driver that may be affected is the extended display driver. This is not installed unless you select "Extend Desktop" in AirParrot and install the driver.

Normal mirroring will continue to work as there is no driver installed for mirroring."

I haven't tested this yet myself, however. They claim the only AirParrot kexts that are causing the trouble are:

/System/Library/Extensions/APExtFramebuffer.kext

/Library/Extensions/APExtFramebuffer.kext

My guess, which is only a guess, is that 10.9.2 was going along its development cycle happy as a clam INTERNALLY using a new tweak in the new API, but because of the SSL debacle, got shoved out rather abruptly to "fix" that issue before anyone internally at Apple understood the ramifications to legacy software.

I have a rather ancient early-2008 MBP and it's choking on the crash for almost anything that may even vaguely reference another screen including Apple's current version of "Motion."  I've removed all of the obvious offenders, but fully expect this behaviour to continue until the next patch; maybe in a couple of weeks to coincide with an iTunes/iOS patch as well.

Not sure what you mean.

Anyway I installed 1.5.4 and it killed all my cams just like before. Used the remove tool. Restarted my computer. Cams were still not working. Searched for the kext files. They were not installed. Restarted again. Launched Skype. All cams were back.

I'll be leaving AirParrot alone until I know for sure that all issues have been resolved.

My experience would suggest they are wrong.

Here a Dutch contribution and a solved problem. All of you: Thank you su much for your brilliant work!

mid 2007 MacBookPro 3.1, after update 10.9.2 no Sight camera, no FaceTime, etc.

The advised full Combo-19.9.2 reinstall didn't work

This is what I finally needed to do:

Removed apps:

- AirParrot

- AirVideoServer HD

- Beamer 1 and Beamer 2

- iVi

Extra manually removed files:

- file:///Library/Extensions/AirParrotDriver.kext/

- file:///Library/Extensions/APExtFramebuffer.kext/

Terminal:

sudo touch /System/Library/Extensions

-> Restart MBP

-> start Skype

pffff. happy me )

well nothing worked.

new symptom appeared!

when i launched Photoshop, crash reports starts again.

i suppose any apps which call up the graphic driver it gets triggered or something.

Apple gotta give out a fix soon unless I gotta keep restarting MBP several times a day!