Closed Bug 454804 Opened 17 years ago Closed 17 years ago

Component Load Error upon launching SeaMonkey or component

Categories

(SeaMonkey :: General, defect)

SeaMonkey 1.1 Branch
x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: lapenn64, Unassigned)

Details

(Keywords: platform)

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11 Upon launching SeaMonkey, I get the following error message dialog box: Title bar: Minimize To Tray - Component Load Error Box Message: Cannot find binary component Icon in Box: Yellow triangle with ! exclamation Buttons: OK Reproducible: Always Steps to Reproduce: 1. Launch SeaMonkey from system tray icon 2. When error message appears, click its OK button to make component (e-mail or browser) appear 3. The correct component (e.g. e-mail client) window will finally open normally, but not until that error message is removed by clicking its OK. Actual Results: Component will open normally upon clicking the error message's OK button. No noticeable effects afterward. Expected Results: Just opened the component window without displaying a message requiring clicking an OK button. This problem has persisted on my Win98se machine since version 1.1.14; current version is 1.1.19
Keywords: platform, polish
Version: unspecified → SeaMonkey 1.1 Branch
Keywords: polish
Did you install any extensions? Can you try (while SeaMonkey is closed) deleting the XUL.mfl file and see if this changes anything? It is located under C:\Documents and Settings\[user name]\Local Settings\Application Data\Mozilla\Profiles\[your profile name]. If this does not help, can you then try to delete the chrome.rdf file in your profile? See http://seamonkey.ilias.ca/profilefaq/#locations for your profile location.
(2+ months later) No reply from reporter. R.Incomplete Reopen if you can reproduce with SeaMonkey v1.1.13.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.