288367 - Regenerated XUL.mfl corrupt, no text in menu or toolbar; caused by chrome.rdf corruption?

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[Kenneth Porter]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217

After an upgrade from 1.8a5 to 1.8b1 my menus were gone. When I looked at my
bookmarks using the separate menu in the toolbar, I could see the separators but
no text, suggesting that the content was there but the font rendering was gone.

I created a new profile which worked and copied stuff to it until I finally
copied the XUL.mfl and then it had the same symptom. Reading about the file, I
tried deleting it and regenerating it but I get the same symptom. I then created
another new profile and copied its XUL.mfl back to my original profile and it
started working.

Reproducible: Always

Steps to Reproduce:




I'll run some more tests and report back.

Comment 1

[Kenneth Porter]

After more investigation I found that chrome.rdf, yet another cache file, was
corrupted. Renaming it and allowing it to be regenerated brought back my menu text.

Now to see the nature of the corruption....

Comment 2

[Brendan Eich [:brendan]]

Garbage in, garbage out works for the FastLoad file too, so it may be irrelevant
except as a cache.

Note that unlike chrome.rdf, the FastLoad file is protected by a checksum.

/be

Comment 3

[Benjamin Smedberg]

And chrome.rdf is suite-only. Changing components.

Comment 4

[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 5

[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.