Closed Bug 35594 Opened 25 years ago Closed 25 years ago

Numerous drawing problems on Linux

Categories

(Core :: XUL, defect, P2)

Product:
Core
Component:
XUL
Platform:
x86
Linux
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: dead, Assigned: blizzard)

Details

I'm noticing several drawing problems on today's Linux build, some of which cause functionality problems, others just cosmetic. Here's what I've found so far. Most of these can be made to paint if you cause an expose event by hiding that part of the window. - Highlights in select boxes not drawing - Values in dropdown boxes not updating when you select an element - Selected text highlight is not getting drawn - Toolbar not painting completely on startup - Scrollbars on list boxes not drawing completely - Menu mouseover highlights not drawing
Pavlov, could this be related to your checkins in gfx/src/gtk yesterday?
Keywords: smoketest
I don't think this is really a smoketest blocker ...
sounds like a big problem, but I'm not sure if it's part of the smoketests or not. emailed the smoketesters asking them for feedback.
Here's my rationale for that: The selection drawing problem makes any test involving selecting text very awkward. I believe the fact that select boxes and dropdowns aren't drawn correctly may impact the ability to correctly set up a profile & mail account, as well.
While it's difficult, i still wouldn't hold the tree closed for it. Peter, can you get this sucker assigned to someone?
Assigning to Pavlov as p2 for m15
Assignee: trudelle → pavlov
Priority: P3 → P2
Target Milestone: --- → M15
The typical drawing problems in IM have gotten a bit worse making IM pretty unusable on Linux. We've had a bug on Pavlov for this several weeks now.
I have seen this before too, but not allways. I sometimes lost menubar mouseover hilight when opening and closing some mozilla- and prefs-windows. Now this happens every time when mozilla is started with -ProfileManager, if started without (opt-build), mouseovers works ok, selection also.
I'm not seeing this except when starting with the profile manager either. Don, feel free to clear the smoketest blocker status if you don't think it should be there.
I see this on debug builds (profile manager starts). this is pretty bad. why would we close this bug?
Hmmmm, on second thought this looks pretty bad (I know because my build finally finished). Let's let Pav make the call.
I think this is a blocker. It makes the browser pretty unusable.
using 2000.04-12-11-m16 (opt comm), i tried collapsing the sidebar, saw a bunch of "Gfx Scrollbar Special case hit!!" spew in the console, then crashed. i'm guessing it's due to this bug (pls tell me if it's not :-). talkback incident #8546871: http://cyclone/reports/incidenttemplate.CFM?reportID=124&style=0&tc=82&cp=1&ck1=SUser+email+address&cd1=%25sairuh%40netscape%2Ecom%25&co1=like&bbid=8546871
Keywords: crash
this isn't mine. I only changed image drawing.
also noticed that cpu usage for mozilla is around 100% and resizing a browser window doesn't resize the content (you end up with a large border on left and bottom sides).
If you run mozilla without a profile, the profile manager will start and you will have the problems listed. Close mozilla and start it again, and it creates a second default profile, and you have these problems again. Close mozilla and start it again, and it runs fine using the second default profile. Perhaps this is a profile manager isue?
What I see with 2000-04-12-11m16 linux build in mail 3-pane window, is the header doesn't redraw to reflect the newly selected message and then clicking on another message sometimes the message isn't highlighted in the thread pane but the correct message body is displayed in the message pane. If this is a different bug please let me know and I will log a new one.
I see this on the main browser windows (back/forward arrows not drawn until you force a redraw), but a better place to see them is the prefs pane (e.g. go to the main Browser prefs panel and click on any radiobox; note that it doesn't update until you force a redraw of the prefs window).
Why is this marked m15? if it just showed up today, it's m16. Also, does it keep the tree closed or not? It's not clear to me that it blocks anyone specifically.
Target Milestone: M15 → M16
This is probably a long standing problem that just was made worse by some checkin made in the past day or two. My recommendation is that this is probably worthy of a serious effort, i.e., take a snapshot of the tree, start backing out changes made in the past day or two, see what caused the problem and how it affects the general problem we have been seeing in Linux for sometime, related to windows not redrawing themselves without forcing an expose event. And start working on an architecture that is not so prone to flakiness as the one we have. We probably have some event-related, timing related problem that needs to get straightened out; this bug is just another symptom of that IMHO, as I've been seeing redraw issues in commercial like these for weeks now (and had filed a separate bug). We probably aren't going to resolve this quickly, so I'm inclined to suggest, if management puts a body on the problem for a reasonably long enough period of time, that we open the tree. But only if we treat this problem with the seriousness that it deserves. Just my 2 cents.
leaf - this really blocks usability for mail/news if you take a look at Esther's comments earlier.
So, something interesting about this is that if you enter a bad url in the url bad and cause the dialog to come up, the problem goes away. Could be related to modal windows?
Adding danm to cc; dan, see last comment by blizzard. Changed bug ownership to blizzard.
Assignee: pavlov → blizzard
didn't this get backed out? if so, can someone remove the smoketest keyword so it no longer shows up on the smoketest blocker list?
I'm doing a build now. If the problem isn't there I'll remove the keyword.
I don't think the crash mentioned here is related, and it's not a smoketest blocker now. Removing both keywords.
Keywords: crash, smoketest
Ok, supposedly this is fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Please ignore the spam. Changing address.
Assignee: blizzard → blizzard
Status: RESOLVED → NEW
put back to RESO FIXE ...
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
... and verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.