Closed
Bug 92227
Opened 24 years ago
Closed 24 years ago
Error dialogue after install and before first load
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
People
(Reporter: Peter, Assigned: asa)
Details
(Keywords: regression)
Attachments
(1 file)
26.00 KB,
image/jpeg
|
Details |
Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.2+) Gecko/20010724
Error dialogue after install and before first load.
For the past couple of days, I get an error message after istall is completed
and while moz is loading the first time (splash screen is visible). See the
attached screenshot with the error message.
Reporter | ||
Updated•24 years ago
|
Reporter | ||
Comment 1•24 years ago
|
||
Comment 2•24 years ago
|
||
This bug is invalid !
Translated error message: "Entry point not found"
Never install an older build over a newer one !
(read the Release notes -> Install in a fresh directory)
Uninstall Mozilla, delete all files that the uninstaller had not deleted and
reinstall Mozilla.
This should fix your problem !
I mark this as a dupe of bug 71010 (this bug is only open for the release notes)
*** This bug has been marked as a duplicate of 71010 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•24 years ago
|
||
I didn't install an older build over a newer one. I installed the newer build
over the older one, *as I have been doing for the past 6+ months*!
I must be possible to update an installation without uninstalling the previous
one - thus loosing all settings one had made (custom dir, custon Start-Menu
entry, etc.) I see no reason why it worked for so many months and then suddenly
it doesn't.
Reopening to clarify misunderstanding.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
please read the bug against which you were duped before you reopen.
*** This bug has been marked as a duplicate of 71010 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•