Description of problem: I've installed the latest nvidia proprietary driver and it causes a lot of flicker on the screen due to a timing bug in clutter. Version-Release number of selected component (if applicable): clutter-1.14.4-6.fc19.x86_64 How reproducible: Very Steps to Reproduce: 1. Have an up to date f19 install. 2. Update nvidia drivers to 334.21+ . 3. Open firefox or a terminal and use for a while. Actual results: Flickering artifacts on the screen. Expected results: No flicker Additional info: The fix is already available in 1.16 branch upstream. f19 uses 1.14 though. The patch applies and builds cleanly on 1.14 though, and this resolves the problem. The fix in question is https://git.gnome.org/browse/clutter/commit/?h=clutter-1.16&id=6665f47d66a871b6e1a5f4200282f42da043a0e8
This needs to be reported to nvidia. The problem isn't seen with the open drivers and if the problem occurs when you install the nvidia proprietary driver it's not something we can fix
This is a bug in clutter. The nvidia change only triggered it because timings changed. The underlying bug was due to a how GL_EXT_x11_sync_object was being incorrectly used in clutter. *The clutter people have recognized this. The clutter people have fixed this in 1.16.* [1] has a discussion of the problem. The fix itself is very simple. I'll attach a patch. [1] https://devtalk.nvidia.com/default/topic/690704/linux/-334-16-parts-of-the-ui-randomly-flicker-when-moving-the-mouse/post/4128101/#4128101
Created attachment 879570 [details] Patch to pull in buffer age fix
Reopening as a patch is available to fix the problem.
got a link to an upstream patch? I'm not pulling a random patch from some forum
The patch in my attached patch is: https://git.gnome.org/browse/clutter/commit/?h=clutter-1.16&id=6665f47d66a871b6e1a5f4200282f42da043a0e8
(In reply to Ivan Kelly from comment #6) > The patch in my attached patch is: > > https://git.gnome.org/browse/clutter/commit/?h=clutter-1. > 16&id=6665f47d66a871b6e1a5f4200282f42da043a0e8 That's against 1.16 not the 1.14 branch that is in F-19
They haven't fixed this bug in 1.14, which it looks like they're not maintaining anymore. 1.14 branch hasn't been touched in 5 months. Regardless, the patch applies cleanly on 1.14, which implies to me that the same bug exists in 1.14 as was addressed in 1.16. Without the patch, I saw the offending behaviour. With the patch, everything is back to normal.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.