256496 - browser UI transparent, no page loaded - after new installation and with pre-existing profile

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Eyal Rozenberg]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: 

When loading browser or mailnews, UI is transparent and I see black text over 
my other windows. The build is a nightly downloaded ~30 minutes ago.

Reproducible: Always
Steps to Reproduce:

Comment 1

[Eyal Rozenberg]

Attachment: screenshot of mozilla 'window'

Comment 2

[Prognathous]

WFM with the Win32 build currently on the FTP.

http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest/mozilla-win32-installer.exe
(21-Aug-2004 11:26   12M)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040821

Please test this again with a new profile.

Prog.

Comment 3

[Eyal Rozenberg]

Yes, well, _doesn't_ wfm with build 07 of 2004-08-22. When I switch to a new 
profile - it does work. Also doesn't wfm with my profile and 1.8a3. Will try 
pinpointing the last build with which it does wfm.

Comment 4

[Eyal Rozenberg]

Attachment: deteriorating UI with build 2004-07-21-10

Comment 5

[Eyal Rozenberg]

Attachment: javascript console following previous screenshot

Comment 6

[Eyal Rozenberg]

Attachment: javascript console following previous screenshot

Comment 7

[Eyal Rozenberg]

removing only the chrome directory causes it to wfm.

Comment 8

[Eyal Rozenberg]

Perhaps a conflict with the BiDiext extension? hmm...

Comment 9

[Eyal Rozenberg]

installing new versions of all chrome I previously had works fine (except an 
uninstaller which I couldn't find the webpage of, but I doubt it was fscking me 
up). Anyway, resolving as WFM for now.

Comment 10

[Eyal Rozenberg]

using the same chrome which WFM, I have re-installed 1.8a3 and it again does 
not WFM.

Comment 11

[Tracy Walker [:tracy]]

this WFM with windows trunk build 2004-11-10-06-trunk

please try the latest builds with a clean install and new profile.

Comment 12

[Eyal Rozenberg]

> please try the latest builds with a clean install and new profile.

I think you misunderstand the problem: the behavior of a new installation of
Mozilla when an older profile exists with many nasty and unruly bits within it.

Comment 13

[Andrew Schultz]

does not block development

Comment 14

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 15

[Eyal Rozenberg]

Well, I know it _can_ happen sometimes...

Comment 16

[Peter Weilbacher]

Cleaning up a heavily broken profile will not be implemented any more in the SeaMonkey 1.x line. If you need help with with cleaning up that profile, Bugzilla is not the place to ask for help. Instead use one of the options from <http://www.seamonkey-project.org/community>.

SeaMonkey 2.0 (the current trunk development builds) will migrate old profiles and thereby throw away all rubbish anyway.

Comment 18

[Eyal Rozenberg]

I was too hasty to verify. I just saw this again with SM trunk nigthly 2008-03-01. So I guess the underlying issue is not resolved by the toolkitization.

Comment 19

[Peter Weilbacher]

And how exactly did you see this this time? I mean what did you do? Did you use that trunk nightly to migrate an old profile? Or did you just upgrade from an older trunk nightly? If so from which one? And what extensions do you have installed, any hints on what other specialities are in your profile? (I take it that this still doesn't happen with a clean profile.)

Comment 20

[Eyal Rozenberg]

Had SM trunk nightly 2008-02-27 installed, then installed some older nightlies (September 2007 and later), to pinpoint when exactly some non-related bug began manifesting. After the 2008-03-01 installation I got the 'transparent window' phenomenon.

Extensions:
- 4chan 0.4.5.0
	(Disabled)
- Adblock Plus 0.7.5.3+.2008032513
- Adblock Plus: Element Hiding Helper 1.0.2+.2008011108
- BiDi Mail UI 0.9
- BugMeNot 1.3
	(Disabled)
- ChatZilla 0.9.81
	(Disabled)
- Console² 0.3.9.1
- CustomizeGoogle 0.71
- DOM Inspector 1.9b2pre
- DownThemAll! 1.0b2
- Enigmail 0.96a
	(Disabled)
- Extension List Dumper 1.8.0
- Full Page Zoom 1.0
	(Disabled)
- Greasemonkey 0.7.20070607.0
- JavaScript Debugger 0.9.87.3
	(Disabled)
- Lightning 0.6a1
	(Disabled)
- Live HTTP Headers 0.13.1
	(Disabled)
- Make ynet links behave like links 2.0.4
- mid 0.6.74
	(Disabled)
- Mozilla QA Companion 0.1.8
- Nuke Anything Enhanced 0.6
	(Disabled)
- Palm Sync 1.9b2pre
- PDF Download 1.0.1.1
- Remember Mismatched Domains 1.4.3
- Remove Duplicate Messages (Alternate) 0.3
- SeaMonkey Debug and QA UI 1.0pre
- Sync Kolab 0.6.0 27-02-2008 17:34
- XPCOMViewer 1.0a1

A good chance it wouldn't happen with a clean profile, but who knows.

Comment 21

[Peter Weilbacher]

OK, so there wasn't any migration involved, because all versions were after the profile directory change.

But, oh my, that's a lot of extensions. Can you not narrow that down somehow? Like is one of the extensions still active that you already had when it appeared some years ago? Then try to remove/disable that.

Comment 22

[Eyal Rozenberg]

I can't even reproduce the bug...

Comment 23

[Peter Weilbacher]

Well, next time you do see the problem you could try to backup the profile and remove extensions by hand, a few at a time.

Comment 24

[Tony Mechelynck [:tonymec]]

Eyal, have you seen this problem recently?

Comment 25

[Eyal Rozenberg]

Haven't been using SM recently... if nobody else can attest to this manifesting I suppose it's WFM.

Comment 26

[Phoenix]

Resolved per whiteboard