SUMMARY Since I switched to Mega-release master builds in openSUSE, various text content field show crispy texts. See Attchment. STEPS TO REPRODUCE 1. try to read text content in akregator or kmails OBSERVED RESULT crispy text, more difficult to read EXPECTED RESULT clear test Operating System: openSUSE Tumbleweed 20231127 KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.6.2-1-default (64-bit) Graphics Platform: Wayland Processors: 20 × 13th Gen Intel® Core™ i7-13700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: TUXEDO Product Name: TUXEDO InfinityBook Pro Gen8 (MK1)
Created attachment 163573 [details] crispy text reading akregator feed
Created attachment 163574 [details] clear text in akregator feed list
Which others?
until now I recognized it for: -Texts in Akregator and Kmail (always -Texts in Plasma notes (I think if it is not active; when click into it, the text changes from crispy to clear) -Titles in the plasma panel (might be, that here only the lower part is not rendered if full screen app touches the panel) - see attachments
Created attachment 163602 [details] crispy in panel
Created attachment 163603 [details] clear in panel
Are you by any chance using a scale factor other than 100% or 200%?
I am quite sure, that the answer is YES, but I cannot look it up, because the Display & Monitor KCM is crashing here every time
(In reply to Robby Engelmann from comment #1) > Created attachment 163573 [details] > crispy text reading akregator feed I think this one is due Qt6 QtWebEngine bug: https://bugreports.qt.io/browse/QTBUG-113574 For Falkon I use `QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor` workaround.
Indeed, this workaround solves the issue. For the time being, I export it on session start. Is this bug now resolved -> upstream?
(In reply to Robby Engelmann from comment #10) > Indeed, this workaround solves the issue. For the time being, I export it on > session start. > Is this bug now resolved -> upstream? Well, I'm not sure about this: (In reply to Robby Engelmann from comment #5) > Created attachment 163602 [details] > crispy in panel This one uses AFAIK QtQuick, so shouldn't be affected by WebEngine bug.
(In reply to Mykola Krachkovsky from comment #11) > (In reply to Robby Engelmann from comment #10) > > Indeed, this workaround solves the issue. For the time being, I export it on > > session start. > > Is this bug now resolved -> upstream? > > Well, I'm not sure about this: > > (In reply to Robby Engelmann from comment #5) > > Created attachment 163602 [details] > > crispy in panel > > This one uses AFAIK QtQuick, so shouldn't be affected by WebEngine bug. This one is resolved as works for me. Possible there only the lowest part was not shown at all. But look fine now since some days