168913 - GUI gone haywire!

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[B. Charles Reynolds]

Symptoms started when Mail/News failed to load properly (1.2a) then GUI gone completely haywire at program launch. Was not able to run any trace or other debug. Running Mac OS X 10.1.5

Roll back to previous version (tried both 1.1 and 1.0.1) failed to resolve error. Removal of all preference and config files hiding in Library folders failed to resolve error. Change of theme failed to resolve error.

E-mail me for a screen capture. I dunno... Maybe it'll help.

Comment 1

[Jo Hermans]

Try to create a new profile, that will solve it.

Comment 2

[Malcolm Rowe]

Could you attach a screen capture to this bug report, please?

Comment 3

[David Tenser [:djst]]

Make sure you uninstall Mozilla *completely* (e.g. first uninstall, then remove
all files in the /mozilla.org/Mozilla program directory. 

Then delete all under the /chrome directory in your profile.

Finally, reinstall Mozilla. Please report back if the problem persists.

Comment 4

[Greg K.]

Reporter, can you reproduce this problem using another Mozilla user profile?

(Reassigning to Browser-General.)

Comment 5

[Matthias Versen [:Matti]]

Please attach a screenshot (gif, jpeg) in this bug (use the "create new
attachment" link)

Comment 6

[B. Charles Reynolds]

Attachment: window capture of what this looks like at startup (post-slpash screen

The splash screen works okay. This is what it looks like at startup after
splash screen (I'm set for Mail/News to open first and this did not change when
I removed all the preferences.)

Comment 7

[B. Charles Reynolds]

removing old profile and creating new solved error.

What caused the error in the first place, though?

Comment 8

[Greg K.]

I've seen that screen capture before. This is a dupe. Adding DUPEME/qawanted.

Comment 9

[Malcolm Rowe]

Me too.  XUL debug boxes pref?

Comment 10

[Malcolm Rowe]

Resolving INVALID (it's a dupe, really).

This sounds like it was possibly caused by profile corruption due to installing 
over an older/newer version, and the original reporter can't reproduce it 
anymore.

Please reopen this bug if you can reproduce it.