Created attachment 204103 [details]
Image showing working qml in Vbox
It contains the test case invisbletext and the attached pngs. It works as you can see in a virtual machine, but on bare metal it i7-3770 CPU it does not.
/boot/modules/i915kms.ko was installed by package drm-fbsd12.0-kmod-4.16.g20190424
Created attachment 204104 [details]
Image showing working qml in Vbox and not working qml on bare metal
Maybe layering rather than rendering artifact. I can't reproduce even inside 11.2 amd64 jails (under 13.0-CURRENT).
Does the application print anything on terminal? Something about missing fonts, theme components, etc.
Can you reproduce outside of host desktop environment? Try a simple window manager (or none at all).
I wonder if it is the same as my problem in https://bugs.kde.org/show_bug.cgi?id=399143
Can you try out workaround proposed there?
To which port does this PR apply?
(In reply to Mark Linimon from comment #4)
x11-toolkits/qt5-declarative, I think.
(In reply to Gleb Popov from comment #3)
export QML_DISABLE_DISTANCEFIELD=1 works.
(Whatever that actually does behind the scenes)
(In reply to Jesper Schmitz Mouridsen from comment #6)
It only strengths my belief that the bug is within our video drivers. Relevant bug report on kms-drm GitHub: https://github.com/FreeBSDDesktop/kms-drm/issues/109
I have drm-fbsd12.0-kmod-4.16.g20190305, a fairly recent 12-STABLE kernel and whatever KDE Plasma is current. With an i7 6700, the major general is displayed in yellow, white, yellow, white, and in several different typefaces (i.e. "can't reproduce the problem").
This suggests that we need to collect information more carefully to figure out where the problem lives. I might have an older i3 around here somewhere.
In the meantime it'd be useful to have a procedure for the collection of needed data: I can't, for instance, easily spot what SVN version my kernel is from, nor which driver X is actually using.
Created attachment 204194 [details]
simple script that tries to gather relevant system info.
Created attachment 204239 [details]
wayland platform has same isssue
FWIW: "--platform xvnc" does render the text visible.
I installed sway and recompiled kernel with evdev, and as the
images shows the text is still rendered invisble on platform --wayland.
I also tried different x11-drivers vesa and scfb, both having the same issue.
sway both under X11 and started directly exposes the issue of invisible rendered text..
Just a little more research.
I have the same issue on Intel(R) Pentium(R) CPU N4200 @ 1.10GHz
Setting QSG_DISTANCEFIELD_ANTIALIASING=gray solves it.
No need for QML_DISABLE_DISTANCEFIELD=1.
(In reply to Jesper Schmitz Mouridsen from comment #11)
I deleted QML_DISABLE_DISTANCEFIELD=1 from /etc/xprofile and set QSG_DISTANCEFIELD_ANTIALIASING=gray.
And it works for me on Intel Core i5-2500 with /boot/modules/i915kms.ko or VESA driver.
CPU: Intel(R) Atom(TM) Processor E3930 @ 1.30GHz (1286.40-MHz K8-class CPU) works without issues, being apollo lake like non working Intel(R) Pentium(R) CPU N4200 @ 1.10GHz this does not seem to be a generation question..