Closed
Bug 95360
Opened 24 years ago
Closed 24 years ago
M0.9.3 file protection disables use for standard users
Categories
(SeaMonkey :: Installer, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: jakobus, Assigned: colin)
Details
After the upgrade from M0.9.2 under SYSTEM account Mozilla couldn't be started
from user accounts, I had to change the protection of the files:
SYS$COMMON:[MOZILLA.COMPONENTS]MOZILLA.XPT
SYS$COMMON:[MOZILLA.COMPONENTS]XPTI.DAT
SYS$COMMON:[MOZILLA.COMPONENTS]XPTITEMP.DAT
from W:RE to W:RWED now Mozilla can be used from user accounts.
Assignee | ||
Updated•24 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Comment 1•24 years ago
|
||
Theo, what happens if you change the protection BACK to W:RE on those three
files now. Can non-priv's users stil use Mozilla or does it revert back to
failing again?
Assignee | ||
Comment 2•24 years ago
|
||
I'm really not sure what's going on here. I can't reproduce this problem.
Here's what I tried:
- removed Mozilla
- installed M0.9.2
- ran Mozilla from non-priv'd account
- upgraded to M0.9.3
- ran Mozilla from non-priv'd account
Each time the non-priv'd user was able to run Mozilla.
Note that I did NOT ever run Mozilla from a priv'd account during this test.
Theo, what do I need to do to reproduce this problem???
Updated•24 years ago
|
QA Contact: gemal → gbush
Reporter | ||
Updated•24 years ago
|
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 3•24 years ago
|
||
I changed the protection back to W:RE for:
SYS$COMMON:[MOZILLA.COMPONENTS]MOZILLA.XPT,XPTI.DAT,XPTITEMP.DAT
using SYSTEM account and I'm able to run Mozilla under the user account.
Colin you did already the test with reinstalling M0.9.2 and upgrading to M0.9.3
so I'm a bit confused.
I changed the Status to INVALID
Assignee | ||
Comment 4•24 years ago
|
||
Very odd indeed. If you see this problem again on a future release, or if
you are able to reproduce it on 0.9.3, please re-open this bug report.
Comment 5•24 years ago
|
||
verified per comments
please reopen if problem recurs
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•