Closed Bug 61686 Opened 24 years ago Closed 24 years ago

Odd existing mimeTypes.rdf makes mozilla' preferences dialog choke

Categories

(SeaMonkey :: Preferences, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 50914

People

(Reporter: anthony, Assigned: matt)

Details

Attachments

(2 files)

Some time recently the mime types helper applications has stopped working for me. To get it to work again, I had to create a new profile and copy the mimeTypes.rdf file from the new profile over my old one. It appears to be quite a different format - I'll attach the broken one and the new one that worked to this bug report. The symptoms I was seeing was that I was completely unable to use the helper applications editing - if I brought up an edit window, and hit 'Ok' nothing would happen. Stdout gets the following message: JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x8 0004005 (NS_ERROR_FAILURE) [nsIRDFContainer.Init]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://communicator/content/pref/overrideHandler.js :: anonymous :: line 242" data: no] I don't know exactly what it is in the RDF that makes it choke - but I've not used anything but the preferences dialog to edit it. It's also been seen by a couple of other users here. The fix (creating a new profile to get a fresh mimeTypes.rdf file) is fairly ugly.
QA Contact: sairuh → shrir
Reporter is this the same as bug 57624?
Bug 57624 might have been related - that's possibly how the file got stuffed, but the symptoms I was seeing was that I was completely unable to use or edit the helper applications...
I am thinking about marking this WONTFIX because the cause of the bug cannot be determined. Thoughts?
No, let's leave this open, parhaps mark as new to get someone from the component to look at it. Maybe it is a known issue... shrir?
Keywords: qawanted
Ok, there's obviously a bit of confusion here - what I meant in this bug was not that the mimeTypes.rdf file got munched, but that the broken file completely fragged the preferences dialog. There was also no way to fix this other than creating a new profile and copy the file out of it - this is extremely non-obvious. If the file is fragged to the point of uselessness, the system should _at_ _least_ put up a notice to that effect, and ideally offer a way of repairing it. If that's too hard, at least make it so that deleting the file and restarting will make moz recreate a default one.
ok, this is the same problem as in bug 50914. At some point of time, mimetypes.rdf was changed and any old profiles would be seeing this problem. Bug 50914 gives a good explanation of this problem. *** This bug has been marked as a duplicate of 50914 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Summary: Odd existing mimeTypes.rdf makes mozilla's preferences dialog choke → Odd existing mimeTypes.rdf makes mozilla' preferences dialog choke
verif dup
Status: RESOLVED → VERIFIED
Keywords: qawanted
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: