Closed Shimazu-X closed 5 years ago
The problem is actually that Compton is failing to start since xfwm4's built-in (and very buggy) compositor is starting up instead. This will be fixed for new installs by the time we drop the final 3.0 iso. My post here describes how to fix it. https://old.reddit.com/r/GalliumOS/comments/bz9wrm/psa_compositing_is_currently_borked_on_30_beta/
Chromebook model - Celes Firmware - MrChromebox Coreboot Installation method - ISO , Nightly Build
Desktop experiences screen tearing with compton enabled in all situations.
Disabling compton has no effect as the Compositor settings under window management tweaks are completely absent in this distro.
Xfwm4 has had working vsync with intel hardware for quite some time now. Enabling the Compositor tab and allowing the use of Xfwm4 native vsync would as far as I know resolve the issue and make compton unnecessary.