Re: Second user can't run app after install
Re: Second user can't run app after install
- Subject: Re: Second user can't run app after install
- From: Iceberg-Dev <email@hidden>
- Date: Wed, 8 Dec 2010 01:27:16 +0100
On Dec 8, 2010, at 1:08 AM, Mel Walker wrote:
I'm having an odd problem with packagemaker installs. An
application is installed to the Applications folder, but when the
second user on the machine tries to run it, they don't have
permission.
The app package has root:admin set for the entire hierarchy in the
pmdoc. The permissions seem right, too (read and execute for
everyone at all levels). I tried setting the owner:group and
permissions first, then creating the installer, but no dice. Both
of the users on the machine are Administrators, id's are 501 and 502.
The installer is being created from the command line on a buildbot,
if that matters. It's a simple installation — one app and one
preference pane. I've run out of good questions to ask for
debugging it, and I'm still pretty new at this "creating
installers" thing.
Any advice? Please?
1. You're not saying what the owner, group and permissions are in the
payload. Use Pacifist to check this.
2. You're not saying what the owner, group and permissions are for
the files on disk after installation.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden