Skip to content

Tearing/Vsync issues in Cinnamon/Clutter #3423

Closed as not planned
Closed as not planned

Description

Running nVidia hardware on multiple machines, and along with other nVidia users I have bad screen tearing in Cinnamon/Clutter unless the game has a VSYNC option which forces it on, then things work fine. For some reason VLC doesn't have tearing that I can notice, but Totem always has horrible tearing.

The solution being done by several users right now is to switch to the Compton compositor instead and forcing on VSYNC for everything through that, but can't we get an option to force it on for Cinnamon instead? For some reason the usual Cluttter options do NOT force on VSYNC. See the following threads on the Linux Mint forums and Reddit:

http://forums.linuxmint.com/viewtopic.php?f=59&t=171020
http://www.reddit.com/r/linux_gaming/comments/28skqt/psa_do_you_have_screen_tearing_issues_only_in/

Also found this suggestion to add a VSYNC option to Cinnamon options, but if that option doesn't work anyway then that won't fix the problem.

#1773

Using nVidia closed driver.

Activity

  1. mtwebster commented on Aug 12, 2014

    @mtwebster
    Member

    Is this something demonstrable with Intel graphics?

  2. pinumbernumber commented on Aug 12, 2014

    @pinumbernumber

    Intel here (4500MHD) and there is tearing everywhere out of the box. Adding some Clutter environment variable hacks gets rid of it but then everything is jerky and slow to respond (dragged windows lag behind the cursor).

  3. pinumbernumber commented on Aug 12, 2014

    @pinumbernumber

    Tried each of those as well as both, no dice. Note: GNOME and most other Xorg DEs also seem to do this. Weston doesn't.

  4. pinumbernumber commented on Aug 12, 2014

    @pinumbernumber

    Sorry, yes the CLUTTER_PAINT line fixes tearing by itself but it causes the other problems I described.

    As for the other fix, it says to install Openbox. Is it possible to use Compton with Cinnamon?

  5. mtwebster commented on Aug 14, 2014

    @mtwebster
    Member

    So, here: linuxmint/muffin#86, we made detection of these types of programs better, to improve their performance (by not compositing them). People were beating down the doors saying we needed to do this if Cinnamon was to be a gaming platform. (I'm not exaggerating!)

    So, now, we seem to have exposed this side effect of tearing (of course), which I can't reproduce yet, but I'm going to keep trying.

    Ideally, we have the performance and the no-tearing, but aren't the two mutually exclusive to a degree? Honestly I'm not very familiar anymore with the different drivers and manufacturers out there. I'd welcome more input (and of course I'll continue to look for more info too).

  6. mtwebster commented on Aug 14, 2014

    @mtwebster
    Member

    The thing that gets me (unless I'm misreading about Compton) is an easy fix would just be to force redirection (compositing) on these windows, or simply provide a switch (like in an applet) to allow you to disable unredirect detection - nothing to do with vsync at all.

    Discussing with someone who knows a bit more about video cards, and reading a bit myself, it seems like they all have their own way to force vsync on or off, and as you mentioned, some of the programs themselves do as well. So would it be satisfactory to simply avoid the issue and force compositing in these cases?

  7. AlbertJP commented on Aug 15, 2014

    @AlbertJP
    Contributor

    Has any of you already tried Gnome Shell to see if the tearing (and other vsync issues) also happen there?

  8. startas commented on Aug 18, 2014

    @startas

    I also have a tearing issue on the desktop - about 10-15 pixels wide lane is tearing, everything else is good. This bug exists in all cinnamon versions, intel hd graphics here.

  9. 49 remaining items

  10. AlpakaSiedler commented on Jan 30, 2020

    @AlpakaSiedler

    I have tearing in Linux Mint 19.3 (Cinnamon, 64-bit) with Nvidia GTX 1060 (3GB) (driver: 440.48.02), using desktop applications such as firefox, as well as in games (i recently tried CounterStrike:CZ, Torchlight 2, No Man's Sky and various different Unity3d Games, also self made Unity3d Games).

    To solve this, i tried what they said here: #3355
    also added "ForceFullCompositionPipeline" to both of my monitors.

    I've read that it should be less issue on MATE, but i would prefer to stay with Cinnamon.

  11. leigh123linux commented on Jan 30, 2020

    @leigh123linux
    Member

    I have tearing in Linux Mint 19.3 (Cinnamon, 64-bit) with Nvidia GTX 1060 (3GB) (driver: 440.48.02), using desktop applications such as firefox, as well as in games (i recently tried CounterStrike:CZ, Torchlight 2, No Man's Sky and various different Unity3d Games, also self made Unity3d Games).

    Why do you need the nvidia beta vulkan driver?, ubuntu vulkan packages aren't new enough to benefit from the new extensions.

    To solve this, i tried what they said here: #3355
    also added "ForceFullCompositionPipeline" to both of my monitors.

    I doubt adding that option will help with the newer nvidia drivers

    I've read that it should be less issue on MATE, but i would prefer to stay with Cinnamon.

  12. AlpakaSiedler commented on Jan 30, 2020

    @AlpakaSiedler

    @leigh123linux
    the newest driver was recommended in a forum cause i had problems with Unity3d using Vulkan and No Man's Sky using also only vulkan.

    ForceFullCompositionPipeline helped a bit for desktop application, its way better for me with enabled, but didn't get rid of it completly

  13. genachka commented on Mar 5, 2020

    @genachka

    Seeing the same problem with Nvidia RTX 2070 on Ubuntu 19.10 and Cinnamon 4.2.4 (though same was with previous versions for the past year+) and as others have tried ForceFullCompositionPipeline and other settings to no avail. Beyond it be annoying for me, apparently it's pretty bad on web meettngs - I need to be on zoom often and share my screen which makes the attendees see the desktop or window or I'm sharing disappear and show my background and then reappear periodically. After months of trying to resolve this, regrettably I'd had to switch to the default GNOME (3.34.2) and everything has been fine but I do miss my Cinnamon. Would love to see a fix for this.

  14. echuber2 commented on Mar 5, 2020

    @echuber2

    Have you tried the various Vsync modes in the control panel?

    https://www.reddit.com/r/CinnamonDE/comments/dx4lyk/vsync_method/

  15. cppcooper commented on Mar 5, 2020

    @cppcooper

    Honestly I am skeptical the vsync modes do anything, there is no discernible difference between any of them for me. After rebooting between changing the modes.

  16. echuber2 commented on Mar 6, 2020

    @echuber2

    Check the source if you're skeptical. They do something; I saw it make a difference on one of my machines instantly after changing the setting. (That did not have an nvidia GPU though.) If anything I bet this all comes down the drivers you have installed. Although, if there is something distinctively wrong with Cinnamon's vsync then I'd also like to know about it.

  17. AlpakaSiedler commented on Mar 6, 2020

    @AlpakaSiedler

    I also tried different vsync modes but it did not make a noticeable difference. I also tried different driver versions, the recommended one, the newest, older stable drivers that were recommended by community users, nothing helped.

  18. genachka commented on Mar 6, 2020

    @genachka

    @echuber2 I too have tried those various Vsync modes and followed the steps in the link. No change. I'm on an Nvidia. And I don't think it's the drivers as I don't have this issue anymore with GNOME :( Open to trying other things as would love to switch back.

  19. github-actions commented on Mar 2, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had
    any activity in over 2 years.

    If this issue is still relevant:

    • Please test on a current version of this package.
    • Add a comment with your findings

    If no activity occurs in the next 30 days, this issue will be
    automatically closed. Issues can be reopened if needed.

  20. github-actions commented on Apr 2, 2026

    @github-actions

    This issue has been automatically closed due to inactivity.

    If you can still reproduce this issue on a current version,
    please feel free to reopen it with updated information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions