Closed Bug 27695 Opened 25 years ago Closed 24 years ago

Components not registered when running with read-only access to Mozilla directory

Categories

(Core :: XPCOM, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: rzach, Assigned: dveditz)

Details

On Linux build 2000.02.14.09, I get the following messages upon startup when I run as root. When I run as a normal user (with read-only access to the Mozilla distribution directory) I do not get them. Wondering if this potentially is a problem. RegSelf Unicode to Big5 converter complete RegSelf Unicode to x-x-big5 converter complete RegSelf Big5 to Unicode converter complete registering component://netscape/editor/htmleditor under command-line-argument-handlers registering component://netscape/appshell/component/browser/instance under command-line-argument-handlers registering component://netscape/messenger under command-line-argument-handlers registering component://netscape/messenger/nntpservice under command-line-argument-handlers registering component://netscape/messengercompose under command-line-argument-handlers registering component://netscape/addressbook under command-line-argument-handlers nNCL: registering deferred (0)
On install we need write access to the component registry. For future runs, we dont. Scott has atleast one bug on this. Scc you can mark this dup of other similar ones.
Assignee: dp → scc
Status: NEW → ASSIGNED
Target Milestone: M18
I don't think I have any similar bugs anymore. Dveditz and I worked on some bugs related to this. Dan, do you want this one? We talked about this situation while we were working on the other stuff.
OK, I'll take it, but I think this is a dup of the other one you just gave me.
Assignee: scc → dveditz
Status: ASSIGNED → NEW
I think I must be misunderstanding this bug. If we have read-only access then we cannot write to the component.reg, so by definition we shouldn't expect any registering to be going on.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Agreed. marking Verified.
Status: RESOLVED → VERIFIED
Component: XPCOM Registry → XPCOM
QA Contact: leger → xpcom
You need to log in before you can comment on or make changes to this bug.