Closed Bug 15987 Opened 25 years ago Closed 25 years ago

mozilla doesn't start with corrupted configuration files

Categories

(SeaMonkey :: General, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: rb, Unassigned)

Details

I am not able to start mozilla as a "normal" user under linux. =>
-------------------------------------------------
rbrunner@bobb:~/package > mozilla-apprunner.sh
MOZILLA_FIVE_HOME=/home/rbrunner/package
  LD_LIBRARY_PATH=/home/rbrunner/package
      MOZ_PROGRAM=./apprunner
      MOZ_TOOLKIT=
        moz_debug=0
     moz_debugger=
.//run-mozilla.sh: line 29:  2245 Speicherzugriffsfehler  $prog ${1+"$@"}
--------------------------------------------------
For all "non-german-speakers" "Speicherzugriffsfehler" means "segfault" :-)

The first time I recognized this problem was 2 weeks ago (nightly build), same
problem with M-10.

System:
SuSE 6.2 with kernel 2.2.12
glibc 2.1
Assignee: chofmann → leger
Component: other → Browser-General
Moving this to Browser-General, because I don't know where it goes.

This works for the rest of us... I'm not sure what the problem is.  Since you
have glibc 2.1, this doesn't seem like the threading bug (I forget the symptoms
of that bug, and also the bug#).

Is there any more information you have?
Reporter responded by email:

I deleted /home/user/.mozilla and since then all is working normal.
Summary: not able to start mozilla with user other than root → mozilla doesn't start with corrupted configuration files
Reassigning all of leger's unscreened Browser-General bugs to nobody@mozilla.org
for pre-screening and triage.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
rb@blumenstrasse.vol.at : do you still consider this to be an issue?

The format of the registry and other config files has changed during development
and there is no point in gracefully handling this until these formats stabilize.
The release notes do indicate that the ~/.mozilla/registry must be deleted
before installing, etc.

I'm marking this INVALID, but please re-open if you consider this to be an
issue.
Old bug.  Build works great.  Marking Verified/invalid
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.