Bug 410748 - Font rendering changes to grayscale once any amount of transparency is applied
Summary: Font rendering changes to grayscale once any amount of transparency is applied
Status: RESOLVED DUPLICATE of bug 397645
Alias: None
Product: konsole
Classification: Applications
Component: font (show other bugs)
Version: 19.04.3
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-09 03:09 UTC by Ryan Reamsbottom
Modified: 2019-08-20 19:27 UTC (History)
1 user (show)

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


Attachments
showing the bug zoomed in on the font in a man page, solid on the left semitransparent on right (307.47 KB, image/png)
2019-08-09 03:09 UTC, Ryan Reamsbottom
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Reamsbottom 2019-08-09 03:09:47 UTC
Created attachment 122030 [details]
showing the bug zoomed in on the font in a man page, solid on the left semitransparent on right

Not sure if this is intended behavior, but when you switch the background of Konsole to use a transparent background (with blur looks nice!), the font rendering setting appears to change.

STEPS TO REPRODUCE
1. Set your font rendering to RGB subpixel
2. Open Konsole (restarting it if already opened)
3. Change background to include transparency

OBSERVED RESULT
Konsole renders fonts with grayscale font smoothing when the background is transparent, even if the setting is for RGB. The titlebar is rendered with rgb but not the semitransparent window content. This may be a limitation with transparency but I'm not sure just a layman.



EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.16
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.60.0
Qt Version: 5.12.3
Kernel Version: 5.0.0-23-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz
Memory: 15.6 GiB of RAM
Comment 1 Christoph Feck 2019-08-20 19:27:30 UTC

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