Closed Bug 55169 Opened 24 years ago Closed 24 years ago

Mozilla doesn't start anymore

Categories

(SeaMonkey :: General, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 41057

People

(Reporter: arjan, Assigned: asa)

Details

Attachments

(1 file)

The latest nightly build doesn't start up anymore; that is: no window appears. strace of the startup is/will be attached. Tested on a K6-2 with Debian Woody+Helix and PentiumIII with Debian Potato+Helix both under kernels 2.2.18pre15 and 2.4.0-test7
did you try with a new profile?
Yes. Doing a "rm -rf ~/.mozilla" only differs in that it now creates a new profile directory.
what nightly are you using exactly?
This sounds like http://bugzilla.mozilla.org/show_bug.cgi?id=55183 which Asa said was working.
It is build 2000-10-03-21-M18
Arjan van de Ven have you deleted any old builds? have you wiped out .mozilla dir?
yes to both, unless a previous Mozilla put files in a _very_ strange place.
Arjan van de Ven, have you tried running it once as root?
I just tried this. Running it as root helps, in that now the mozilla window appears. However, running it as a normal user again later doesn't work still.
This seems to be a permission problem, because mozilla works when I change the ownership of all (mozilla)files to my regular user. Marking them "world readable" + "world executable" was not enough though.
I've been able to reproduce this behavior on Linux. It seems to work on a fresh build: To reproduce: rm -rf package rm -rf /root/.mozilla tar zxf mozilla-blah.tar.gz If you try to run mozilla as a regular user, the program won't start. If you start mozilla as root, the new profile manager dialog will come up and /root/.mozilla will be created. Now any user can run mozilla. If you delete /root/.mozilla, any user can still run mozilla as long as you don't blow away the package directory again. This makes me think a mozilla file is being written to. I've attached a diff file from ls -lR commands used before and after running mozilla as root. It looks like the component.reg file is updated, among other things. [steve@demon package]$ diff /tmp/out.1 /tmp/out.2 4,5c4,5 < drwxrwxr-x 11 8482 wheel 4096 Oct 19 10:23 chrome < -rw-rw-r-- 1 8482 wheel 366000 Oct 19 10:23 component.reg --- > drwxrwxr-x 12 8482 wheel 4096 Oct 19 17:24 chrome > -rw-rw-r-- 1 8482 wheel 366044 Oct 19 17:24 component.reg 50c50,53 < total 2492 --- > total 2528 > -rw-rw-r-- 1 root root 3714 Oct 19 17:24 all-locales.rdf > -rw-rw-r-- 1 root root 4657 Oct 19 17:24 all-packages.rdf > -rw-rw-r-- 1 root root 11124 Oct 19 17:24 all-skins.rdf 67a71 > drwxr-xr-x 6 root root 4096 Oct 19 17:24 overlayinfo 69a74,75 > -rw-rw-r-- 1 root root 923 Oct 19 17:25 user-locales.rdf > -rw-rw-r-- 1 root root 623 Oct 19 17:25 user-skins.rdf 3195a3202,3240 > > ./chrome/overlayinfo: > total 16 > drwxr-xr-x 3 root root 4096 Oct 19 17:24 communicator > drwxr-xr-x 3 root root 4096 Oct 19 17:24 editor > drwxr-xr-x 3 root root 4096 Oct 19 17:24 messenger > drwxr-xr-x 3 root root 4096 Oct 19 17:24 navigator > > ./chrome/overlayinfo/communicator: > total 4 > drwxr-xr-x 2 root root 4096 Oct 19 17:24 content > > ./chrome/overlayinfo/communicator/content: > total 4 > -rw-rw-r-- 1 root root 1394 Oct 19 17:24 overlays.rdf > > ./chrome/overlayinfo/editor: > total 4 > drwxr-xr-x 2 root root 4096 Oct 19 17:24 content > > ./chrome/overlayinfo/editor/content: > total 4 > -rw-rw-r-- 1 root root 242 Oct 19 17:24 overlays.rdf > > ./chrome/overlayinfo/messenger: > total 4 > drwxr-xr-x 2 root root 4096 Oct 19 17:24 content > > ./chrome/overlayinfo/messenger/content: > total 4 > -rw-rw-r-- 1 root root 910 Oct 19 17:24 overlays.rdf > > ./chrome/overlayinfo/navigator: > total 4 > drwxr-xr-x 2 root root 4096 Oct 19 17:24 content > > ./chrome/overlayinfo/navigator/content: > total 4 > -rw-rw-r-- 1 root root 258 Oct 19 17:24 overlays.rdf
this a dupe of bug 41057 *** This bug has been marked as a duplicate of 41057 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: