Open Bug 1209820 Opened 9 years ago Updated 8 years ago

SM updater does not set file permissions correctly on multi-user machine

Categories

(SeaMonkey :: General, defect)

SeaMonkey 2.38 Branch
x86_64
macOS
defect
Not set
normal

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: long, Unassigned)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:41.0) Gecko/20100101 Firefox/41.0 SeaMonkey/2.38
Build ID: 20150923200940

Steps to reproduce:

Was running Seamonkey 2.35.  Did Help -> Check for Updates.  Let it download and upgrade to 2.38.  Restarted SM when prompted.


Actual results:

Before the upgrade here are the results for files that are unreadable by other users on the system:

silver-bullet:SeaMonkey.app klong$ fgrep -ril qlehtqkjeth .
fgrep: ./Contents/Resources/precomplete: Permission denied
fgrep: ./Contents/Resources/removed-files: Permission denied
fgrep: ./Contents/Resources/searchplugins/duckduckgo.xml: Permission denied
silver-bullet:SeaMonkey.app klong$ 

After the upgrade here are the unreadable files:
silver-bullet:SeaMonkey.app klong$ fgrep -ril qlwhqkjhtqt .
fgrep: ./Contents/Resources/components/components.manifest: Permission denied
fgrep: ./Contents/Resources/dependentlibs.list: Permission denied
fgrep: ./Contents/Resources/precomplete: Permission denied
fgrep: ./Contents/Resources/removed-files: Permission denied
fgrep: ./Contents/Resources/searchplugins/duckduckgo.xml: Permission denied
silver-bullet:SeaMonkey.app klong$ 

When klong tries to run Seamonkey after the upgrade they get:
silver-bullet:MacOS klong$ ./seamonkey
Couldn't load XPCOM. 

If I then set the file permissions on ./Contents/Resources/dependentlibs.list to 0644 klong can run seamonkey again.


Expected results:

I shouldn't have to manually fix permissions to allow other users on the system to run SM.  The updater should ensure all permissions are set properly to allow everyone on the system to run the app.
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86_64
The seamonkey 2.46 updater still is setting crazy permissions.  I'm attaching two files showing the Seamonkey file permissions before and after I let the SM 2.46 run.
Attached file before.txt
Attached file after.txt
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: