No buffer garbling on browser window, nor in any another part of Linux screen (including (FB/)console).
It seems than Xlibre Xserver not supports whole-screen gamma/HSV correction,
— but I must test the DRM ownership dmesg's message (not causing the other problems now).
Dear user, remember about uninstalling evdev when you use libinput for mouse pointer, for surety. And the old xf86-* nouveau's Xorg things, also!
No need to rebuild initcpio / initrd!!! I applied the thread-safe version of KMS by some option in X .conf /settings dirs – even if nvidia DDX (that is, Xorg's) not supports it explicitly / supports it in build-in manner already:
The /etc/X11/xorg.conf.d/xlibre.conf , for peace of mind
Section "Device"
Identifier "nvidia"
Driver "modesetting"
Option "Atomic" "on"
EndSection
#Section "ServerFlags"
# Option "IgnoreABI" "1"
#EndSection
—the other driver can be a fallback. Rather not for Wayland, as Wayland depends on another .so libraries (system objects simply – something as DLL in Windows), but Compiz is better than KWin. Rather one thing that the reversal does apply is situation when Fisheye lens effect is necessary – perfectly for showing the astronauts' big fake, the „old-old-stable” he he... hoax.
Browser's card preview is much better under Wayland (than on the old Xorg version), bur in new Xlibre Xorg, garbling of graphics is very, VERY low.
•While Blender 3D is garbling intensively under OLD X, this one (IMO) depends on GLX quality, not being possible to correct as X/even at Wayland, level.
•Not surprising if it remains even on „higher” NVIDIA cards, „new” NV open source drivers, etc.
The ABI seems to be a topic more important only when dealing with Boost libs, Qt, and/or the old buggy Xorg version.
BTW, Python also changes its API interface, a bit. Now it seems to slow down, fortunately.
Standarization is very important.
•In Linux world, the basic interface change you need would be changing LXDE into LXQT. With such DE enabled, Qt big libs can be preloaded into RAM as cache – w/o any prefetch technique!
I have NVIDIA in initcpio as standard – a key for nice 2×boot-splash (that is, starting also as systemd's sevice later!!) – not wantin' to check if standard fbdev/„NV dev” FB & so on...
I can't fully understand the console FB's, kernel console takeovers... difficult topic still. Even GRUB2, without grub-customizer application (it needed manual patching !! – I noticed that for sake of „modern” UEFI program on „old” BIOS – but a BIOS working better when DDC VGA(=D-Sub) cable is FULL in pins' number!), is difficult.
The boot process is especially DIFFICULT on the RebbeccaBlack OS – despite it has nice (not bug-free, but operating nice... before system crash) Wayland – KWin perfect speed, similar to one of Compiz's on proper NVIDIA-enabled whole-system setting.
But KWin is very quick also on the Xlibre Xorg's continuation software. Buggy, at least without system crash (as the Wayland on main system...), but Xlibre not requiring computer to restart!
The compiz start-again script seemed to have influence on Xlibre stability once, but I deactivated it – Compiz is so stable now that I not need to adapt Porteus „wait for device” thoughts into another domain.
The FireDragon Browser is now STABLE at playing Youtube – on the contrary, at OLD Xorg Server, there was hard desynchronizations of YouTube video playback VISUALS.
