Bug 582856
Summary: | Under Compiz windows don't update consistently | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ira Malinich <thub> |
Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | ajax, awilliam, xgl-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-04-16 19:22:53 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
Ira Malinich
2010-04-16 00:07:26 UTC
A new version of the Intel driver, xorg-x11-drv-intel-2.11.0-1.fc13, has just been added: https://admin.fedoraproject.org/updates/xorg-x11-drv-intel-2.11.0-1.fc13 . Can you please test with this version and see if the bug is reproducible? If you have an installed Fedora 13, you can download and install the driver from the Koji link. If you are testing with live images, the nightly live images from 2010-04-17 (or possibly 2010-04-18) onwards should include this version: http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ . This comment is being added to all open Fedora 13 intel bugs, please ignore if it does not make sense in the context of your bug. Since upgrading to xorg-x11-drv-intel-2.11.0-1.fc13 I haven't been able to reproduce this bug. Interesting side effects of this update: - glxgears no longer uses 60% CPU, now down to a tasteful 3% - glxgears reported framerates appear to be locked to exactly the vertical refresh rate of my monitor (either 60 FPS or 74.6 FPS) where it used to show between 1200 and 1800 FPS. *** This bug has been marked as a duplicate of bug 577142 *** |