Description of problem: I observe the same problem on an old thinkpad with a trident cyber 9397dvd video card, than the one described here: https://www.redhat.com/archives/fedora-test-list/2005-March/msg00248.html When gdm starts, the screen becomes completely white, and only the hw cursor remains reactive. The laptop still runs fine, and is reacheable with ssh. When switching back to a VT, the console is also completely garbled (vesafb is in use), but it still works. I suspect a problem with the trident driver. Version-Release number of selected component (if applicable): Fedora development packages (xorg-x11-6.8.2-10) How reproducible: Always The problem appeared since a few days, maybe when xorg-x11-6.8.2-10 was released, but I'm not 100% sure about this.
Created attachment 112185 [details] Xorg log file
Please file a bug report in X.Org bugzilla, which is located at http://bugs.freedesktop.org in the "xorg" component. This will ensure that the maintainer of this video driver, as well as other developers who work with this driver are aware of the issue, and can investigate fixing it in the next release. Once you've filed your report to X.Org, if you paste the URL here, Red Hat will track the issue in X.Org bugzilla with upstream developers, and will review any fixes that become available for potential inclusion in future Fedora Core updates.
Setting status to "NEEDINFO", awaiting upstream bug URL for tracking.
here is the X.org bugzilla : https://bugs.freedesktop.org/show_bug.cgi?id=2976
Thanks, setting status to "UPSTREAM" for tracking.
*** Bug 154502 has been marked as a duplicate of this bug. ***
Bug #160500 appears to be a duplicate of this bug. Just FYI.
This bug seems to be possibly a duplicate of bug #161242. Everyone experiencing this issue, please read that bug and try the workaround mentioned in it and provide feedback. If the workaround works, we can close this as a dupe of bug #161242, and it'll be fixed when we release an update for that bug. Thanks for testing.
cool, it works for me.
Thanks for the update.
*** This bug has been marked as a duplicate of 161242 ***