Closed
Bug 186795
Opened 23 years ago
Closed 23 years ago
Mozilla won't start as non-root
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 163524
People
(Reporter: omgs, Assigned: asa)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.1) Gecko/20020826
In Linux, Mozilla versions 1.2.1 and 1.3a, as root, Mozilla starts OK, but as
non-root, there's no way to start. The installation is in /usr/local/mozilla,
and executing /usr/local/mozilla/mozilla, just gives the prompt back
inmediately. I've checked permissions in /usr/local/mozilla, but they all seem
to be OK. This happens every time, so it's easy to reproduce.
Reproducible: Always
Steps to Reproduce:
1.Execute as non-root /usr/local/mozilla/mozilla
2.An icon on the desktop
3.
Actual Results:
Nothing. The prompt back.
Expected Results:
Just start up
| Reporter | ||
Comment 1•23 years ago
|
||
I can't do anything by myself. I think the developers have to fix this. This is
my first bug report, so sorry if I have made something wrong.
Comment 2•23 years ago
|
||
The first time mozilla is run, it has to create a file within its installation
area. In your case this means running mozilla as a user with rights to create
new files within /usr/local/mozilla. Please review the release notes (e.g.
<http://www.mozilla.org/releases/mozilla1.3a/>) and check the section
"Multi-User installs". Make sure you're following the steps outlined there.
Please update this bug report to indicate whether this resolves your problem.
| Reporter | ||
Comment 3•23 years ago
|
||
I've tried the script, even have reinstalled mozilla again (with
/usr/local/mozilla empty), and then the script, and I get the same. One thing:
the script takes the relative directory, that is, if executed from
/usr/local/mozilla as ./script, then $dist_bin is ".", so I executed the script
specifying the full path. I don't know what regxpcom and regchrome do, but the
.rdf files in the chrome directory didn't exist before the "touch".
Comment 4•23 years ago
|
||
do you have MOZILLA_FIVE_HOME set? does the mozilla/components directory have
execute permission?
see bug 163524
| Reporter | ||
Comment 5•23 years ago
|
||
Yes, you're right. MOZILLA_FIVE_HOME is set to /usr/local/mozilla. I took a look
at the bug and that's exactly what happens. Changing the permissions for the
components directory makes it work.
Now, I'll try to mark this bug as a duplicate of #163524. I hope to be allowed.
If not, asa, or whoever is allowed, should change the status.
I'd like to say that this happens also with 1.2.1, so I don't know why this
hasn't been fixed yet.
*** This bug has been marked as a duplicate of 163524 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•