"Soundflower.pkg" cannot be opened. You should eject the disk image.

[GoogleCodeExporter]

So, I ran in to the "Soundflower is not installed" problem and ran the 
uninstall script.  So far so good.  Then I tried to run the installer again, 
and got the message:

"Soundflower.pkg" cannot be opened.  You should eject the disk image.

Googling suggests that this is something to do with Gatekeeper on Mountain 
Lion.  But I'm only on 10.7.4, and there's no Gatekeeper setting in the System 
Preferences..  More googling says that Gatekeeper is already present in 10.7.4, 
but hidden - you need to use spctl to configure it.  I tried 'sudo spctl 
--disable' and it said "invalid API object reference".  I tried 'sudo spctl 
--master-disable' and got no error, but it seems to make no difference - it 
still refuses to run the Soundflower installer.

Restarts at various points in the process have made no difference either.

Any suggestions?

Original issue reported on code.google.com by whittm...@gmail.com on 3 Aug 2012 at 9:05

[GoogleCodeExporter]

I see the same, and might be able to provide some additional info for debugging:

I have downloaded Soundflower 1.6.5. I'm using an early 2008 MacBook Pro with 
OS 10.8. Gatekeeper is turned of, so that I'm able to install and use software 
from any vendor, be they registered with Apple or not.

I open the disk image and double click the installer package. This leads to the 
same message as mentioned above:

"Soundflower.pkg" cannot be opened.  You should eject the disk image.

Hitting the "?" button eventually takes me to a web page stating that:

The app's authorisation has been revoked. Although this app was signed by an 
authorised dealer, the certificate for the app has been revokes.There might be 
a problem with it. The app cannot be opened. You should check with the App 
Store to see if there is an updated version of this app, or check with the 
software developer.

Original comment by tr...@trondlossius.no on 5 Aug 2012 at 12:06

[GoogleCodeExporter]

Same here!

Original comment by andrea.m...@gmail.com on 6 Aug 2012 at 12:54

[GoogleCodeExporter]

Running spctl directly against the installer also tells me that the certificate 
has been revoked.  spctl also confirms that assessment is disabled globally on 
my machine, so the fact that it's refusing to run that installer looks to me 
like a bug.  Maybe not all that surprising since Gatekeeper isn't actually 
officially present in Lion, but still a right royal pain in the fundament.

What's also puzzling is that the installer ran fine the first time, but isn't 
allowed to run after that.  Again that smacks of a bug to me, rather than a 
problem with the installer.

Original comment by whittm...@gmail.com on 7 Aug 2012 at 9:03

[GoogleCodeExporter]

OK, I seem to have found a fix for this.  The problem seems to be that the 
installer gets "quarantined" because of an unrecognised certificate.  This is 
marked against the file by an extended attribute.  You need to clear the 
attribute to allow the installer to run again.  The command for this is:

xattr -c <pathname of the installer>

The installer will run after this.  It throws up a certificate error but you 
can tell the system to trust it.  For some reason, the install ran completely 
clean after this and SoundFlower was there in the System Preferences - none of 
the "SoundFlower is not installed" malarky.  The only things I am aware of 
having done differently this time are:
1) Gatekeeper was disabled (as documented in my original posting)
2) I copied the installer off the disc image on to my desktop and ran it from 
there
3) I had restarted the machine just before running the installer
I don't know whether any of those things made a difference, I mention them so 
that other folks who still have problems can try them.

Original comment by whittm...@gmail.com on 7 Aug 2012 at 10:19

[GoogleCodeExporter]

Further information: I've realised that I *had* to copy the installer off the 
disc image in order to clear the "quarantined" attribute, since the disc image 
is read-only.  That suggests that the attribute is set on the installer as it 
is downloaded within the disc image, which probably needs fixing.

Also: I've successfully installed SoundFlower on a second machine using the 
same trick, so I'm confident that it works (no restart was required).

Original comment by whittm...@gmail.com on 7 Aug 2012 at 10:28

[GoogleCodeExporter]

This is fixed in the 1.6.6b version.

Original comment by tr...@trondlossius.no on 8 Aug 2012 at 7:26

[GoogleCodeExporter]

Tried 1.6.6b and it's fixed the problem.  Many thanks!

Original comment by whittm...@gmail.com on 11 Aug 2012 at 9:32

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I was trying to install a different application which has the same problem.

"xattr -c <pathname of the installer>"

Copying the file to desktop and running that command fixed the issue.
Thanks  whittm...@gmail.com.

Original comment by kniha...@gmail.com on 26 Feb 2013 at 3:13

[GoogleCodeExporter]

You help me!
Thanks!!!

Original comment by z.kodza...@gmail.com on 13 Apr 2013 at 7:08

[GoogleCodeExporter]

sorry guys, it' s not working for me. any help please?

Original comment by riccardo...@gmail.com on 4 May 2013 at 2:56

[GoogleCodeExporter]

I don't know how to do the following (not a great computer user..):
"
"xattr -c <pathname of the installer>"

Copying the file to desktop and running that command fixed the issue."

Original comment by riccardo...@gmail.com on 4 May 2013 at 2:58

[GoogleCodeExporter]

many sites are only still offering 1.6.5
get 1.6.6b here:

http://code.google.com/p/soundflower/

Original comment by hansende...@gmail.com on 13 Jul 2013 at 3:35

[GoogleCodeExporter]

Whit!!! Awesome, thanks so much! My macbook pro with OSX 10.7.5 wouldn't let me 
install adobe master suite from the actual disk for the same reason! I was able 
to copy the files from the disc to my mac desktop, then run that command in 
terminal and POOF, fixed! 

A little trick for those of you less familiar with Terminal, just type the 
beginning of the line above   "xattr -c " then literally drag the install file 
that you cannot open from your desktop and drop it into the terminal window, 
this will ensure the exact and full filepath is used.  If nothing seems to 
happen after pressing enter and it just opens a new blank terminal line, you 
have successfully completed this step and the install file should open right 
from your desktop.  Thanks again! Saved me a nightmare! 

Original comment by ronlivig...@gmail.com on 29 Oct 2014 at 2:21