Closed
Bug 172787
Opened 22 years ago
Closed 21 years ago
Mozilla fails to start under Win2K for users with only "User" privilages.
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: achowe, Assigned: asa)
Details
(Whiteboard: M_V)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 Mozilla will not start for users who only have "User" privilages under Windows 2000. In a cyber cafe environment or a restricted work place, the majority of users would only have "User" rights (not administrator or power-user rights). Reproducible: Always Steps to Reproduce: 1. Create a user account who is only a member of the "Users" group. 2. Login as this user and start Mozilla. Actual Results: Mozilla banner appears and nothing further happens. Expected Results: That the program starts and presents a window. There is a work-around. I found that if you set the security rights for "Users" on the c:/Program Files/mozill.org directory to "modify" (essentially the same as for Power Users), then the program will start. However, this shouldn't be necessary.
Updated•22 years ago
|
Whiteboard: M_V
Comment 1•22 years ago
|
||
WFM for users with no write permissions with 2003010108 on win2000. you do need to run mozilla once as a user with write privs for the mozilla folder, as it mentions in the release notes, but after that it should work as any user. Reporter: Can you reproduce this bug with a recent build of Mozilla (for example, 1.3a)? If so, then please comment again with details. If not, then please resolve this bug as WORKSFORME. Thanks.
Comment 2•21 years ago
|
||
no response from reporter for >30 days. resolving INVALID. reporter - if you can reproduce this with a recent build of mozilla, please reopen and add a comment. thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•