Closed Bug 17123 Opened 25 years ago Closed 25 years ago

Crash on startup, apparently during XPCOM registry initializing

Categories

(Core :: XPCOM, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED DUPLICATE of bug 9120

People

(Reporter: djarb, Assigned: dp)

Details

djarb@/usr/local/src/mozilla/dist/bin$ ./mozilla-apprunner.sh
MOZILLA_FIVE_HOME=/usr/local/src/mozilla/dist/bin
  LD_LIBRARY_PATH=/usr/local/src/mozilla/dist/bin
      MOZ_PROGRAM=./apprunner
      MOZ_TOOLKIT=
        moz_debug=0
     moz_debugger=
nsNativeComponentLoader: autoregistering begins.
.//run-mozilla.sh: line 29: 31591 Segmentation fault      $prog ${1+"$@"}
Somehow I suspect this is another case of M10 or later after a previous earlier
install. If so, you need to delete you Mozilla registry, see
http://www.mozilla.org/projects/seamonkey/release-notes/m10.html.

Please mark this invalid if that fixes the problem.
Status: NEW → ASSIGNED
Target Milestone: M11
Did deleteing the registry fix the problem. Please confirm.
Deletion of the registry did not resolve the error.
Can you try deleting the component registry : package/component.reg and try this
again.
I think I've narrowed this one down.

The account that I'm using to run mozilla does not have write permission in the
source tree. If that user attempts to load mozilla when component.reg does not
exist, mozilla segfaults. If a user with write permission runs mozilla and
thereby creates component.reg, the original user is then able to run mozilla. If
component.reg is then deleted, behavior reverts to the original.

Since mozilla will often be used by accounts which do have write permission,
this is still a serious bug. It worst, it should display an error and abort.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
I agree. I have another bug on this one...

*** This bug has been marked as a duplicate of 9120 ***
Status: RESOLVED → VERIFIED
[bugday] seen this one before. it's a dupe - marking verified. It's also a good
thing that i've never installed mozilla anywhere other than ~
Component: XPCOM Registry → XPCOM
QA Contact: dp → xpcom
You need to log in before you can comment on or make changes to this bug.