285973 - opening and closing Mozilla blanks out desktop icons, then reopens with colors changed and blooming, and crosshatch on screen, also AOL icon and several others

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[steve chichester]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; AOL 9.0; Windows NT 5.1; CustomExchangeBrowser; .NET CLR 1.1.4322; Alexa Toolbar)
Build Identifier: 1.7.5

Opening and closing Mozilla blanks out desktop icons, then reopens with colors 
changed and blooming on AOL, and crosshatch on screen. AOL icon and several 
others have crosshatch. 
Blooming and color reversals makes reading AOL top toolbar info difficult. All 
functionality is fine otherwise. Browsing multiple tabs, opening sites is fine 
on Mozilla. Opening sites through AOL is fine also.
Removed and reinstalled 1.7.5 4 times, no change

Reproducible: Always

Steps to Reproduce:
1. Click on Mozilla icon to open. Or close via x out, or task manager, or 
toolbar.
2.
3.

Actual Results:  
As described

Comment 1

[steve chichester]

Operating system windows XP office small business. 

Comment 2

[Zook Valem]

Could it be that it is encountering a slow response from the O/S somehow??

Comment 3

[steve chichester]

[e-mail]   said "Could it be that it is encountering a slow 
response from the O/S somehow??" 

The shutdown is virtually instantaneous whether I go from desktop icon, or 
quick launch. That doesn't happen with Basi Firefox 1.4(?) Also, screen color 
goint to crosshatch would seem a problem relating to programs interacting. 

If that's registry, I'm no where near astute enough to chase it down. The only 
Regular peculiarity I have is that when AOL opens it prevents Internet Explorer 
from opening and blocks Crazy Browser and an email program. All respond (page 
not found), 

Comment 4

[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 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 6

[steve chichester]

Any body got anything on this?  It's Mozilla 1.7

Comment 7

[Wayne Mery (:wsmwk)]

(In reply to comment #6)
> Any body got anything on this?  It's Mozilla 1.7

Steve, Nope. WFM with nightly. PLease test a newer build and report back with failure and build number or success (in which case you can close the bug).
Newer versions:
Alpha: http://www.mozilla.org/projects/seamonkey/
nightly: http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/

Comment 8

[Wayne Mery (:wsmwk)]

-> INVALID
lacking info