anti-apXos
Thanks, @andyprough. After changng to the devuan xlibre repo and doing an apt update, I was able to purge libelogind0 and libelogind-compat and it just “updated” xserver-xlibre-core instead of wanting to uninstall it, so it does seem this is the better repo to use with antix.
Note that at least as of today, this devuan xlibre repo still calls the Bookworm-compatible repository “stable” and the Trixie-compatible repository “testing”, but that will probably change soon as Devuan itself has already changed, so you may be better off using the Devuan names “daedalus” and “excalibur” to be sure of which repo you’re using.
Since it doesn’t bring elogind this way, I think I’ll probably switch my main install over to xlibre now. Being able to use the modesetting driver without screen tearing is really a noticeable improvement over having to use the poorly supported Intel DDX driver like I was before just becuse it has the TearFree option.
however switching to fullscreen mode results in an image that appears to be a horrible screen tearing, image hardly recognizable.
Are you using a compositor (like picom, compton, or xfwm4)? It’s pretty common for those to get disabled when you switch to fullscreen, which results in screen tearing since the compositor is what’s doing the vsync if your X driver doesn’t. If this is the issue, there should be an option you can set that keeps the compositor active even for fullscreen windows.
"--"