User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925 Periodically the window(s) will not re-paint properly. Page may be viewed by resizing window or sliding scrollbar. Clicking on a link will load the next page, but window won't display it without further jiggering. Persists with both new windows and new tabs. Problem remains between sessions. Clearing the cache does not remedy. Occurs in mail client as well. Does not go away until soft reset. Has been observed in versions 1.3 and 1.4 as well. Has occurred with Radeon 8500, 9000, and 9700 versions in 1600x1200 dual-head mode (i.e. 3200x1200. Also in 1024x768. Has persisted over multiple driver updates, and on 3 different mobo chipsets (KT266, KT266a, TigerMP). Have not seen it on Matrox G500 in similar mode. Not related to temperature of system/video chipset. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. Appears to occur randomly 2. 3. Feel free to contact me for further discussion. I manage a network which includes over 100 Windows workstations of various ages, with a wide assortment of video cards and display modes (about 1/3 are some sort of dual-head). Have been using Mozilla as the primary element in a 2-year campaign to break the IE habit among a group of corporate investors with some success. More than happy to speak in person if things aren't too crazy. My direct number is 203/351-2833. As my company also develops software, and my supervisors appreciate the security benefits of Mozilla over IE, there is no issue with me contributing time and knowledge during work hours. BIG fan since 1.0. Feeling guilty for not reporting this 9 months ago.
Is it something similar with what is reported in bug 220040? (see the attached image there) That was marked as duplicate of bug 205893.
Summary: DIsplay becomes and remains corrupted in dual-head mode with ATI Radeon → Display becomes and remains corrupted in dual-head mode with ATI Radeon
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.