which indeed fixed the tearing, but also disabled SPDIF audio somehow. Another recommendation is to dump X11 and use Wayland, but when I go to MATE Tweak, the only option for Window Manager I see is Marco.
The tearing is well visible in Chrome and VS Code. I didn't notice it with other applications. Any advice how to fix it or how to get Wayland working?
In MATE-Tweak you can choose Marco with Compton GPU Compositor.
I also used to get tearing with Intel chipsets, and I used Compton to solve this.
It just might work for you too.
At the moment there is not yet a Wayland-protocol compatible compositor for Mate that is ready for prime time. It is still in experimental phase and there is still a lot of work to do before it is ready.
You would think that, because the wayland-protocol is a standard, that every 'wayland'-compositor would be usable.
Yeah, well, no.
Every desktop-environment has its own quirks and demands that must be implemented in the compositor as additions to the standard protocol
(like support for MATE-panel in MATE-desktop) so we can't just drop in 'mutter' or 'kwin' (wayland-protocol-compatible-compositors of resp. Gnome and KDE) and call it a day. It won't work on MATE.
I have Marco (Compton GPU Compositor) now, but the tearing is still there. I could argue it's a bit worse: instead of a tear along a single scan line, I have tears along multiple scan lines in the same area now.
Even without '20-intel.conf' ? (which might get in the way)
That is stunning.
The weird part is that you get tearing with an IDE and a browser (something i've never encounterd before) instead of tearing with video (which usually is the case)
Well, there is another compositor for you to try: compiz
I tried Compiz (advanced GPU accelerated desktop effects) and no cigar. To be clear, I observe tearing in portrait mode when scrolling with web technology based applications, e.g. Chrome, Typora (Webkit) and VS Code (Electron). Other applications, e.g. Okular, don't tear.
If you only have tearing with web-engine based applications...
Maybe a stupid idea, but could you also test with firefox ?
AFAIK Chrome, Typora snd Electron are all (more or less) webkit based.
Firefox has a completely different render-engine so that could point to a conflict with webkit and portrait-display-handling.
Oh, btw, if you want to test this with wayland, try a live-ISO of Fedora
As far as I know, Fedora has wayland by default.
Probably the fastest way to discover if wayland would be a solution.
Then it's not an render engine problem.
It also can not be solved by using a compositor.
I'm afraid that this is due to the immediate-mode drawing of the Xserver.
In my opinion, the only options you have are:
keep the 20-intel.conf and see if you can solve the sound issue
OR
switch over to wayland, which means:
Try the highly experimental MATE version
(lots of things will be broken)
OR
Try a (live)distro that fully supports wayland (like Fedora-live-ISO)
If anyone wants to chime in with other solutions, please do.
I'm out of ideas