Bug 114914
Summary: | xrandr gives peculiar results on a trident cyberblade. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Telsa Gwynne <hobbit> |
Component: | XFree86 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-21 11:25:26 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
Telsa Gwynne
2004-02-04 14:13:03 UTC
I have seen this problem also. In my case it was switching from 1024x768 to 640x480 that messed up the screen. The problem remained even when I switched back to 1024x768 but now there were several "stripes" with repeated content. Like so: 1. Screen from (0,0)-(127,768) 2. Black area from (128,0)-(255,768) 3. Screen from (256,0)-(383,768) [same contents as in 1] 2. Black area from (384,0)-(512,768) I am not sure about 128, 256, 384, 512 limits. These are just estimated values (and easier to count with). With the new xorg release available (xorg-x11-6.7.0-2) I can no longer reproduce the problem. I've tried changing resolutions back and forth between the available resolutiuons without noticing any problems. This could be related to bug #120950 perhaps. That's the only thing that's changed that might affect this that I can think of off the top of my head. Telsa, can you test the current FC2 bits and let me know if this issue is still reproduceable, or wether it's resolved now? Thanks in advance, TTYL Assuming the problem is fixed now for everyone in Fedora Core 2, as per comment #2 above. Please reopen if problem returns. Thanks again. Setting status to "CURRENTRELEASE" of FC2. |