Hello Kitty, Hello Crappy!
August 23, 2009 6:47 PM Subscribe
My iMac iSight camera is "in use by another application". Can you help me figure this out so I can use the camera again?
Hi,
In a moment of utter stupidity I tried downloading a driver from the Hello Kitty website in order to transfer some photos from my digital cam to the computer. Clearly this has affected something on my computer and I don't know how to undo what I've done.
I have an intel iMac, OS X 10.4.11 and when I try running Photo Booth, iChat or anything else the iSight camera is not recognised.
I would seriously appreciate any help here. I have reset the PRAM to no avail.
THANKS!
Hi,
In a moment of utter stupidity I tried downloading a driver from the Hello Kitty website in order to transfer some photos from my digital cam to the computer. Clearly this has affected something on my computer and I don't know how to undo what I've done.
I have an intel iMac, OS X 10.4.11 and when I try running Photo Booth, iChat or anything else the iSight camera is not recognised.
I would seriously appreciate any help here. I have reset the PRAM to no avail.
THANKS!
Have you tried going into Activity Monitor (in your Applications -> Utilities folder) to see what might be running covertly?
See if the new driver shows up on the bottom of the first page of your System Preferences (under "Other").
posted by starman at 7:21 PM on August 23, 2009
See if the new driver shows up on the bottom of the first page of your System Preferences (under "Other").
posted by starman at 7:21 PM on August 23, 2009
Response by poster: I have tried all of the things suggested above.
There might still be something running in the Activity Monitor that I haven't tried quitting because it's not clear what it's doing.
posted by fantasticninety at 7:30 PM on August 23, 2009
There might still be something running in the Activity Monitor that I haven't tried quitting because it's not clear what it's doing.
posted by fantasticninety at 7:30 PM on August 23, 2009
Have you tried rebooting?
posted by Cat Pie Hurts at 7:55 PM on August 23, 2009
posted by Cat Pie Hurts at 7:55 PM on August 23, 2009
Best answer: FYI, this seems to be the same problem.
It suggests the offending driver is in /System/Library/Image Capture/
posted by cj_ at 7:58 PM on August 23, 2009 [1 favorite]
It suggests the offending driver is in /System/Library/Image Capture/
posted by cj_ at 7:58 PM on August 23, 2009 [1 favorite]
Response by poster: CJ, thank you so much! That worked perfectly! Wow, I am extremely grateful.
posted by fantasticninety at 8:22 PM on August 23, 2009
posted by fantasticninety at 8:22 PM on August 23, 2009
No problem, always happy to help purge Hello Kitty..
FYI (for anyone in the future with a similar problem) you can find out what those .pkg installers are adding to your system from Terminal by running:
The directory it unpacks that to is defined in the XML file SomeInstaller.pkg/Contents/Info.plist.
That's assuming good faith on the part of the installer, of course, which can run bash/perl scripts that do who-knows-what. Generally not an issue though with legit software, though.
posted by cj_ at 9:05 PM on August 23, 2009 [1 favorite]
FYI (for anyone in the future with a similar problem) you can find out what those .pkg installers are adding to your system from Terminal by running:
lsbom SomeInstaller.pkg/Contents/Archive.bomThe directory it unpacks that to is defined in the XML file SomeInstaller.pkg/Contents/Info.plist.
That's assuming good faith on the part of the installer, of course, which can run bash/perl scripts that do who-knows-what. Generally not an issue though with legit software, though.
posted by cj_ at 9:05 PM on August 23, 2009 [1 favorite]
« Older How do I get up to speed with e/m coding? | When can a relief pitcher enter a baseball game?... Newer »
This thread is closed to new comments.
posted by Cat Pie Hurts at 7:12 PM on August 23, 2009