Bug 417651 - Monospaced text in Firefox and Thunderbird is displayed in a non-monospaced font with no whitespace
Summary: Monospaced text in Firefox and Thunderbird is displayed in a non-monospaced f...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_style (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL: https://bugzilla.opensuse.org/show_bu...
Keywords: regression
Depends on:
Blocks:
 
Reported: 2020-02-14 17:05 UTC by Nate Graham
Modified: 2020-02-14 18:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Mis-rendered monospaced text (411.91 KB, image/png)
2020-02-14 17:05 UTC, Nate Graham
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2020-02-14 17:05:28 UTC
Created attachment 126027 [details]
Mis-rendered monospaced text

I've been shamefully living with this bug for a few weeks and haven't reported it until now. It seems like a regression in 5.18.

I have my monospaced font set to Ubuntu Mono 11pt in the Fonts KCM, but since sometime in the last month, monospaced text in Firefox and Thunderbird has been rendering in a non-monospaced font, and all whitespace is removed. It's very reproducible on Phabricator code reviews in Firefox and replies to plaintext emails in Thunderbird. See attached screenshot.

It seems to happen no matter which GTK theme I use.

Here's my gtk3 config file:

cat /home/nate/.config/gtk-3.0/settings.ini
[Settings]
gtk-application-prefer-dark-theme=0
gtk-button-images=1
gtk-cursor-theme-name=breeze_cursors
gtk-decoration-layout=icon:minimize,maximize,close
gtk-enable-animations=1
gtk-fallback-icon-theme=Adwaita
gtk-font-name=Ubuntu, Regular 11
gtk-icon-theme-name=breeze
gtk-menu-images=1
gtk-primary-button-warps-slider=1
gtk-theme-name=Breeze
gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ
Comment 1 Nate Graham 2020-02-14 18:32:08 UTC
Upon further investigation, this seems more likely to be a distro packaging/configuration bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1163734