197050 - Failed to write xpti manifest

Status: RESOLVED EXPIRED

(Firefox Build System :: General, defect)

Description

[Martin Mokrejs]

User-Agent:       Mozilla/4.78 [en] (X11; U; OSF1 V5.1 alpha)
Build Identifier: 

Starting mozilla-1.4a on OSF1/Tru64Unix 5.1A I get:

$ mozilla
No Persistent Registry Found.
Type Manifest File: /afs/gsf.de/@sys/usr/lib/mozilla-1.4a/components/xpti.dat
###!!! ASSERTION: Failed to write xpti manifest!: 'Error', file
xptiInterfaceInfoManager.cpp, line 1940
Break: at file xptiInterfaceInfoManager.cpp, line 1940
nsNativeComponentLoader: autoregistering begins.



Is it really necessary that
/afs/gsf.de/@sys/usr/lib/mozilla-1.4a/components/xpti.dat
is writable to anyone? Why doesn't "make install" make sure it is writable to
everyone!



Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

-> build config for the "Why doesn't "make install" make sure it is writable to
everyone!" suggestion

Comment 2

[Martin Mokrejs]

Actually the resulting mozilla binary should spit out a clear message that
xpti.dat has to be world writable and exit immediately, if it isn't. Of do you
want a patch for the shellscript wrapper calling mozilla-bin?

Comment 3

[cls]

'make install' doesn't ensure that xpti.dat is writable because it's a security
hole and it's not required for the browser to run correctly.


*** This bug has been marked as a duplicate of 128436 ***

Comment 4

[Martin Mokrejs]

But could mozilla exit immediately?

I cannot find in mozilla the bugreport on xpti.dat, where is discussion how to
remove it. At the end of that report, there was a list of places which call that
function. The intention I think was to collect list of places/cases when it
gets' acalled and fix it. I'll attach what I get on startup with current
cvs-version build.

Comment 5

[Martin Mokrejs]

Attachment: gdb output

I hope this helps, especially, if someone find the other bugreports. ;)

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.