Bug 411044 - Badly rendered font after adding Flathub to sources
Summary: Badly rendered font after adding Flathub to sources
Status: RESOLVED DUPLICATE of bug 407202
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.16.4
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-18 18:40 UTC by Marcello Massaro
Modified: 2019-08-21 14:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Sources list after adding Flathub, bad font rendering (71.68 KB, image/png)
2019-08-18 18:40 UTC, Marcello Massaro
Details
Sources list after before adding Flathub, normal font rendering (69.95 KB, image/png)
2019-08-18 18:41 UTC, Marcello Massaro
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcello Massaro 2019-08-18 18:40:20 UTC
Created attachment 122231 [details]
Sources list after adding Flathub, bad font rendering

SUMMARY
After adding Flathub as default source for Flatpak, italic fonts are not properly rendered. Closing/reopening Discover fixes it.

STEPS TO REPRODUCE
1. Fresh-install KDE Neon dev edition (on VM with Windows host)
2. Open Discover
3. Click on "Sources", bottom left
4. Click on "Add Flathub"

OBSERVED RESULT
Font in italic (and only that, AFAIK) is not rendered properly.

EXPECTED RESULT
Font in italic should be readable.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon Developer
KDE Plasma Version: 5.16.80
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
Comment 1 Marcello Massaro 2019-08-18 18:41:45 UTC
Created attachment 122232 [details]
Sources list after before adding Flathub, normal font rendering

For reference, this is how the same section looks like before clicking the "Add Flathub" button.
Comment 2 Nate Graham 2019-08-19 15:42:03 UTC
Do you happen to be using an NVIDIA graphics card by any chance?
Comment 3 Marcello Massaro 2019-08-19 15:56:47 UTC
I am. Is this a (not to me) known bug ?
Comment 4 Nate Graham 2019-08-19 16:29:43 UTC
Yep, it sure is. I can't find the original bug, so moving to KWin for now for further triage.
Comment 5 Martin Flöser 2019-08-20 06:35:18 UTC
KWin ist not responsible for don't rendering. Nate, please don't move unrelated bugs to KWin.
Comment 6 Aleix Pol 2019-08-20 10:39:13 UTC
This is not done by KWin but by Qt. Moving to KWin was wrong but also closing as not a bug.

In practice, it's something that is broken elsewhere in the stack, there's little we can do from Discover or Plasma.
Comment 7 Nate Graham 2019-08-20 13:32:43 UTC
Martin, stop abusing the NOT A BUG resolution status. This is a bug, it's just not in KWin. The correct status would therefore be RESOLVED UPSTREAM with a link to the Qt bug. Please add the relevant Qt bug report to the URL field and familiarize yourself with https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging#Identify_bugs_caused_by_external_issues_.28UPSTREAM.2FDOWNSTREAM.29 if this is unclear.
Comment 8 Aleix Pol 2019-08-21 14:32:18 UTC

*** This bug has been marked as a duplicate of bug 407202 ***