getsolus / packages

Solus Package Monorepo & Issue Tracker
50 stars 68 forks source link

libvte doesn't display fonts properly on plasma (T9594) #236

Open celticmagic opened 10 months ago

celticmagic commented 10 months ago
Joey Riches (#joebonrichie), 2021-02-24 15:23:22 UTC

Affects any terminal using libvte e.g. tilix, gnome-terminal {F7094722}
celticmagic commented 10 months ago
TraceyC (#TClark77), 2021-02-24 15:50:48 UTC

I don't see that problem on Tilix v 1.9.4 on Plasma In the Fonts settings for plasma - Fixed width I'm using Hack 10pt In my default profile for Tilix I have "custom font" checked and am also using Hack 10pt What font are you using that profile?
celticmagic commented 10 months ago
Joey Riches (#joebonrichie), 2021-02-24 16:59:24 UTC

thanks for the reply. For me, the _only_ font that renders properly is hack, every other font i try has the same issue, including the default font. Could you confirm?
celticmagic commented 10 months ago
TraceyC (#TClark77), 2021-05-27 01:12:23 UTC

Sorry for the really late reply. I just noticed the task had an update. I had to look, to confirm, is Source Code Pro the default font on tilix now? I checked quite a few fonts in tilix and konsole. All of the monospace fonts I looked at in tilix displayed OK for me. These are the ones I checked: Fira Code Medium - ok ✅ Garuda Regular - not ok ❌ (not a monospace font) Source Code pro - ok ✅ Inconsolata Powerline - ok ✅ Kinnari Regular - not ok ❌ (not monospace) DejaVu Sans Mono - ok ✅ Liberation Mono for Powerline - ok ✅ Interestingly enough, the fonts that looked bad in tilix aren’t available in konsole’s preferences unless I check “show all fonts”. Without that checked, konsole only shows fonts it considers to be monospace. The ones that look good are available without this being checked. It looks like tilix is showing all or most fonts, not filtering out the non-monospaced ones. What monospace fonts aren’t displaying properly on your system? I’d like to try them on mine.
celticmagic commented 10 months ago
TraceyC (@TraceyC77), 2023-08-03 19:43:52 UTC

Hey @joebonrichie , is this still an issue on your system?
TraceyC77 commented 9 months ago

@joebonrichie , is this still an issue? Forgive me if this is a duplicate notification, I don't know if you got the last one during systems migrations

joebonrichie commented 9 months ago

Yes, this is still a problem with an OOTB install of any libvte based terminal on plasma. The solution is to use a custom font.

EbonJaeger commented 1 month ago

Here are some observations from further investigation:

  1. The issue does not occur on Fedora KDE. That said, they also don't use Hack (or even have it packaged, as far as I can tell). Installing Hack manually and setting it as the font in GNOME Terminal renders as expected.
  2. On Solus Plasma, checking the box to use a custom font, but not actually setting one, also fixes the rendering. It appears to be still the same font, but displayed correctly.

This is what it looks like with the incorrect rendering: image

And after checking the Custom Font option, without setting a new font: image

This all makes me much less inclined to say this is an upstream issue. I have a feeling that we're missing something, but I don't know enough about font handling to guess where. The VTE package is basically the same between Solus and Fedora. Does anyone else have any ideas on where to start looking?