User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7a) Gecko/20040108 Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7a) Gecko/20040108 When opening the Mail Window on a Xinerama-configured system with two displays, moving the window to display 0 will leave the scroll bars and menu bars transparent, showing whatever windows that lie under the Message Window to show through. Moving the Message Window completely to display 1 will restore the transparent bits. Opening, then closing or moving another window on top of the Message Window while on display 1 or 0 will cause the transparency problem to reappear. Occurs on systems running Solaris 8-10, with all known windowing patches applied. Problem does not exist in 1.3, but does exist in 1.4 to current. Reproducible: Always Steps to Reproduce: 1.Start mozilla on xinerama-configured system. 2.Open Message Window. Window should open at the centerpoint of the two displays. 3.Drag Message Window to display 0 Actual Results: Observe scroll bars and menus disapear from Message Window. Underlying window content shows through. Expected Results: Draw window correctly. Default Theme
Mark: Which framebuffer do you use (XVR-1000 ?) ?
OS: SunOS → Solaris
In this case, it's dual-headed SunRays. Don't know exactly how to describe the framebuffer otherwise.
Just saw similar behavior in 1.6, but in my case it was the message list pane (top right in the default config). Also, in my case, moving the window from one display to another didn't fix it; the only thing that worked was to disable and reenable the message pane (via View->Show/Hide->Message Pane, and I don't mean the list pane!) My system is an Ultra 80 with two ffb2+ (rev. 3) framebuffers, running Solaris 8 07/03, kernel patch 22. I'm using the Pinball theme from themes.mozdev.org.
Alan: Any ideas ?
I've seen problems like this as well. I'm not sure how early I first saw it (I thought it might be a problem with my build), but it certainly exists in 1.7 and 1.8. Hardware I've seen this with: Sun Blade 1500 w/ XVR-100 & TechSource GFX-450C Sun Blade 150 w/ PGX-64 & TechSource GFX-450C Sun Blade 150 w/ PGX-64 & TechSource GFX-32C Ultra 5 w/ PGX-24 & TechSource GFX-32C Ultra 5 w/ PGX-24 & PGX-32 (TechSource Raptor GFX) These have all been running Solaris 8, with patches that were current at the time. Oh, and from the builds, I've noticed the following: checking for XineramaIsActive in -lXinerama... no checking for X11/extensions/Xinerama.h... no I'm thinking that this might be significant??
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
(In reply to comment #7) > 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. This bug still exists. We still see: checking for XineramaIsActive in -lXinerama... no checking for X11/extensions/Xinerama.h... no from running configure
You need to log in before you can comment on or make changes to this bug.