Summary:
Unable to install Soundflower 1.6.6b on Mac OS X 10.6.8. Running installer
package from GUI produces an error message complaining that an unknown error
occurred and exits. Soundflower does not install. Running from command line
produces same results. Installing software updates, restarting, etc, does not
resolve the issue. Checking system console logs reveals that installer failed
due to the package being untrusted.
Steps to Reproduce:
Attempt to run installation package, either via GUI by double clicking package
(or control clicking it and opening it with installer) or via command line
using the installer command as root.
Running from command line using following command:
sudo installer -verbose -pkg Soundflower.pkg -target /
Expected Results:
Expected soundflower to be installed correctly as I had no trouble installing
it on my other Mac with identical hardware specifications running the same OS
version the previous day.
Actual Results:
Installer fails and complains about unknown error and asks that I contact the
software vendor for assistance. Console logs reveal that installer failed due
to package being untrusted.
Running installer from command line produces following output:
installer: Package name is Soundflower
installer: Installing at base path /
installer: Preparing for installation….....
installer: Preparing the disk….....
installer: Preparing Soundflower….....
installer: The install failed (The Installer encountered an error that caused
the installation to fail. Contact the software manufacturer for assistance.)
Related console log:
3/5/14 5:22:40 PM Installer[333] Failed install preflight: Error
Domain=PKInstallErrorDomain Code=102 UserInfo=0x11868e010 "The package
“Soundflower.pkg” is untrusted." Underlying Error=(Error
Domain=NSOSStatusErrorDomain Code=-2147409654 UserInfo=0x11866e8a0 "The
operation couldn’t be completed. CSSMERR_TP_CERT_EXPIRED")
Regression:
Software installation was successful on an identical Mac (Apple iMac, model
identifier iMac7,1) running the same OS version the previous day.
Notes:
According to the project bug tracker, this issue was apparently encountered in
previous versions and was supposedly fixed. Despite this claim, however, the
problem appears to have returned.
Also not sure why it worked on my other machine the other day but not this one.
Perhaps the certificate expired overnight - do not know.
Original issue reported on code.google.com by dgulley...@gmail.com on 6 Mar 2014 at 1:57
Original issue reported on code.google.com by
dgulley...@gmail.comon 6 Mar 2014 at 1:57