chawang000 / soundflower

Automatically exported from code.google.com/p/soundflower
GNU General Public License v2.0
0 stars 0 forks source link

Soundflower installs with weird permissions under non-admin #42

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Installing Soundflower under non-admin user by authorising installation with an 
Admin account 
results the Soundflower folder in the Applications folder to have weird 
permissions and unable for 
the non-admin to access. See attached screenshot.

What version of the product are you using? On what operating system?
Soundflower 1.5.1, OS X 10.6.1

Please provide any additional information below.
See attached image.

Original issue reported on code.google.com by pjburnh...@gmail.com on 10 Oct 2009 at 4:07

Attachments:

GoogleCodeExporter commented 8 years ago
Installed as admin and still have weird permissions.
Installed with 1.2 already installed. Don't know if that might have affected 
somehow.

Original comment by patrik.a...@gmail.com on 14 Oct 2009 at 6:26

GoogleCodeExporter commented 8 years ago
Got the same issue on OS X 10.6.2, Soundflower 1.5.1:

drwx------   7 501     wheel   238 Nov 13 12:13 Soundflower

manul:Soundflower vitaly$ ls -l
total 64
-rwxr-xr-x  1 501  admin  18009 Aug  1 01:18 License.txt
-rw-r--r--  1 501  501     3502 Sep  1 21:03 ReadMe.rtf
-rw-r--r--  1 501  admin   3929 Sep  2 18:47 Soundflowerbed README.rtf
drwxrwxr-x  3 501  admin    102 Sep  2 18:44 Soundflowerbed.app
-rw-r--r--  1 501  501     1186 Sep  1 21:03 Uninstall Soundflower.scpt

After changing permissions to vitaly:admin, Soundflower works ok

Original comment by vita...@gmail.com on 14 Nov 2009 at 2:12

GoogleCodeExporter commented 8 years ago
Similarly, I used Finder to change permissions for 
/Applications/Soundflower
from no access 
to read only 
for everyone. 

Original comment by grahampe...@gmail.com on 17 Nov 2009 at 11:47

GoogleCodeExporter commented 8 years ago
This folder is created by Apple's installer program, and there are no settings 
in 
PackageMaker to control it.

Original comment by 74obje...@gmail.com on 8 Mar 2010 at 3:32

GoogleCodeExporter commented 8 years ago
Installed 1.5.2 without any problems.

Original comment by vita...@gmail.com on 12 Mar 2010 at 10:45

GoogleCodeExporter commented 8 years ago
I am having the same issue.  This occurs with both 1.5.1 and the newer 1.5.2 
beta.  I am running Mac OS X 
10.6.3.  It installs with no permissions.  My account is an administrator 
account and it was installed under this 
account.

Original comment by joe.rizz...@gmail.com on 11 May 2010 at 5:43