Closed
Bug 64699
Opened 24 years ago
Closed 15 years ago
manifest.rdf pointing to nonexistent chrome prevents relaunch
Categories
(SeaMonkey :: UI Design, defect, P2)
SeaMonkey
UI Design
Tracking
(Not tracked)
RESOLVED
EXPIRED
Future
People
(Reporter: depman1, Assigned: jag+mozilla)
Details
builds 2001-01-08-08.
1. Go to http://jimbob/trigger3.html
2. Select a_reg_chrm_all_3_mfst.xpi from acceptance test menu. Or try another
functional menu "mfst" cases like f_reg_chrm_content_mfst. This will install a
folder (a_reg_chrm_all_3_mfst) inside of "Chrome" containing manifest.rdf file
(pointing to obsolete chrome).
3. Press Trigger. Then OK.
4. Quit Netscape 6.
5. Relaunch Netscape 6 (doesn't matter if you remove the "a_reg_chrm_all_3_mfst"
folder. same problem).
Result: It won't launch. It doesn't even reach the profile manager.
Note: If we kill the process, it still won't relaunch. Nor will rebooting work.
The app needs to be reinstalled!
Expected: More graceful behavior! App should launch, maybe with warning message
that an .rdf file is pointing to non-existing chrome.
Comment 1•24 years ago
|
||
Note that David is not expecting the product to *work*, only that it shouldn't
silently hang. We need a little emergency native dialog (native because
it's the chrome that's missing) that says "A required file, FOO.JAR, was not
found. Mozilla cannot run." or something. Similar to the messages windows puts
up when a required .DLL isn't present.
This will remove the mystery from the user. They will know 1) that mozilla is
NOT going to work, and 2) it's not Mozilla's fault since there's a file
missing. It will also give Tech support something to work with.
Updated•24 years ago
|
Keywords: mozilla1.0,
nsbeta1
Comment 3•24 years ago
|
||
nominating... This is similar to the "missing 3rd party theme" bugs which were
going to be fixed by falling back to the global default. But it's not identical
since this is about what to do if that global default is also missing (and in
particular chrome content, not chrome skin).
This could probably wait 'til after moz1.0 -- fixing the "missing theme" bugs
catches a relatively common case, this case would be about as common as missing
.dll's in the build (that is, more a developer problem than a user problem).
Comment 4•24 years ago
|
||
In fact, I'll proactively nsbeta1- it -- I'm sure Ben has more important things
to work on. This is still impt for an eventual "platform" story, though.
We really should fix this. Marking nsbeta1+, mozilla0.9.1, reassigning to pchen
Comment 8•23 years ago
|
||
-> default assignee
Assignee: pchen → trudelle
Target Milestone: Future → ---
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
Updated•20 years ago
|
Comment 10•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 11•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 12•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 13•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 14•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 15•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 16•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•