Bug 35939
Summary: | scrolling help window loses white background | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Marty Shannon <martys> |
Component: | anaconda | Assignee: | Brent Fox <bfox> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-04-24 19:42:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marty Shannon
2001-04-14 22:43:19 UTC
Weird. We have not seen this during our internal testing. Sounds like GTK+ is not repainting the screen properly. Ok, here's a few questions: 1) Does this happen in every screen or just the keyboard? 2) Is it reproducible? 3) Are you doing the install in a non-English language? 4) Have you gone to a virtual console and then come back to the GUI? 5) Does this happen if you start the install with the 'nofb' option? Using English. Using FB. Pretty sure I didn't flip to another console. Will check on other questions as I start next (re-)install. Ok, it is definitely reproducible, but it only appears on the "select keyboard" screen. Will try "nofb" tomorrow if that's still useful. I've verified this problem in both framebuffer and non-framebuffer mode. It's not clear whether this is a GTK problem or not. It doesn't happen with any other screens that I can tell. Also, clicking "Hide help" and then "Show help" causes the problem to stop. That is, until you back up to the beginning of the installer and then go forward again. The installer uses the GtkXHtml widget for the online help. This widget is being replaced with the release of GTK+ 2.0, so this problem will go away once we make the switch to the new GTK. This is a bug in GtkXHtml, which is unmaintained, so we cannot fix this without porting to GTK+ 2.0 |