Created attachment 586428 [details] Sample Xorg log Description of problem: After upgrading the X server on a host from the F16 to the F17 version, I noticed degraded performance. (For example, using plain old twm, moving a window outline frame became choppy he and borders around windows aren't redrawn properly.) Looking in the Xorg log, I see an error message that it tries to load the xaa module, but can't find it. It is indeed no longer included in the F17 Xorg package, and judging by some Google hits it is being discontinued so I guess that is intentional. If the xaa module is discontinued, it appears to me to be a bug in the mga driver to try to load it by default. Version-Release number of selected component (if applicable): xorg-x11-drv-mga-1.4.13-19.20120104git9223c44a7.fc17.x86_64 xorg-x11-server-Xorg-1.12.0-5.fc17.x86_64 How reproducible: Every time Steps to Reproduce: 1. Find a computer that still has an Matrox Millenium II or similar. (Probably the hardest step. You are welcome home to me if you are in the neighbourhood! :-) 2. Start X in default configuration. Actual results: Much less smooth experience than with the F16 version of things. Expected results: Similar performance as under F16. Additional info: Maybe this is really a bug I should report upstreams? I'm not sure how much of the configuration is done by the packager and how much is original xorg. I tried to force exa acceleration instead by setting the AccelMethod option in the Device section. The X-server seems to load it, but everything crashes when gdm is about to display the greeter. I will investigate this further to see if it is a bug in X, GDM, or simply something I have done wrong in my configuration.
Created attachment 587109 [details] Sample Xorg log I discovered there was an error in my swrast dri driver installation. This error was unrelated to the problem reported in this bugzilla, but to avoid any confusion, I attach a new Xorg log after this problem has been fixed.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.