I had the Intel Media Driver installed on this system at some point in
the distant past, and it installed /etc/profile.d/intel-media.sh - which
overrode the libva-intel-driver, and caused gstvaapi.so to fail to load
correctly on Wayland... which then caused GDM to fail to start. Note
that X11 worked fine because of using a different code path.
If we had the Xorg Drivers section still with xf86-video-nouveau there,
this probably would've gone over there originally, but this place fits
well.
The original plan was to put this into LFS, but I decided against it
since it works fine until you start using programs such as Epiphany or
KDE Plasma.
1. Remove redundant paragraph for Cantarell, left over from when it
was at gnome (latest gnome versions do not ship the fonts, only
the source - prepared TTF fonts are at Google fonts).
2. Reword the old KDE comment in Noto fonts, replace by mentioning
that Noto fonts are preferred for everything in KDE Plasma and
applications, except for monospace - and add link to Hack for that.
3. Comment Oxygen fonts.
I'm pretty sure most desktop apps can use variable fonts today (even
Xterm renders variable fonts fine). But there is indeed something not
working, notably xelatex.
PRC contains mainland China, Hong Kong, Macao, and Taiwan. (In some
uses "mainland" also contains Hong Kong and Macao, but it depends on
the context).
In mainland China many users want TC and JP fonts alongside SC font
because once you know SC you can just read TC seamlessly, and many
Chinese Linux users (not including me) are Japanese cartoon or game
fans. IMO using the monolithic CJK .ttc font file is easier.
1. mention variable fonts (not generally useful for the desktop)
2. Cantarell is now at google fonts
3. The organization of Noto fonts has changed. Provide an example
for how to download, and working links for the CJK variants (now
just Noto Sans JP etc).
4. Oxygen Sans and Mono now at google fonts, but each is separate.
5. Comment the Noto Sans CJK item, the links are no longer useful
and the fonts have been renamed.
6. Fix the debian UMing link to point to the tarball.
One of the things I've been doing over the past week is building
packages that list &qt5-deps or &qt5-components with Qt Alternate and Qt
Components.
For each one I've been checking logs for relevant information to Qt. It
doesn't show up in my logs, so I checked the Configure script and didn't
notice anything in there either.
When checking the NEWS file, I found out that several backends have been
removed - including cogl, qt, and DirectFB.
With Mesa-23, all of the tests other than the ES2 tests will fail due to
minor differences in behavior between Mesa-22 and Mesa-23.
This doesn't seem to cause any problems at runtime, so we'll just
document the failures.
