Bug 390629 - Fonts not being rendered in bold in spite of removing the face name from the configuration files.
Summary: Fonts not being rendered in bold in spite of removing the face name from the ...
Status: RESOLVED DUPLICATE of bug 378523
Alias: None
Product: konsole
Classification: Applications
Component: font (show other bugs)
Version: 17.12.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-17 20:21 UTC by Aayush Agarwal
Modified: 2018-04-30 15:02 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Konsole configuration (224 bytes, text/plain)
2018-02-17 20:21 UTC, Aayush Agarwal
Details
kdeglobals configuration (3.37 KB, text/plain)
2018-02-17 20:22 UTC, Aayush Agarwal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aayush Agarwal 2018-02-17 20:21:24 UTC
Created attachment 110756 [details]
Konsole configuration

I may have missed something, but after installing Tumbleweed on another machine and following the workarounds mentioned in bug 378523 and bug 384445, Konsole does not render intense fonts in bold. Unlike in the previous report, Kate renders bold fonts correctly.
Comment 1 Aayush Agarwal 2018-02-17 20:22:26 UTC
Created attachment 110757 [details]
kdeglobals configuration
Comment 2 Ahmad Samir 2018-02-17 21:08:15 UTC
Just to be sure, did you restart konsole after saving the changes to kdeglobals?
Comment 3 Christoph Feck 2018-02-18 02:11:35 UTC
Konsole also has per-profile font configuration. It is possible that these still contain the face name. Please check ~/.local/share/konsole/*.profile
Comment 4 Aayush Agarwal 2018-02-18 05:41:13 UTC
(In reply to Ahmad Samir from comment #2)
> Just to be sure, did you restart konsole after saving the changes to
> kdeglobals?

I did. Rebooted my computer to be doubly sure.

(In reply to Christoph Feck from comment #3)
> Konsole also has per-profile font configuration. It is possible that these
> still contain the face name. Please check ~/.local/share/konsole/*.profile

I did, and attached the current version of Profile 1.profile when creating this bug.
Comment 5 Mike Lui 2018-03-19 20:32:24 UTC
I'm seeing the same problem on a fresh install in ArchLinux, all default settings.
Comment 6 Nate Graham 2018-03-26 21:03:17 UTC
What version of Qt are you using?
Comment 7 Mike Lui 2018-03-27 16:44:22 UTC
I was able to get this workaround working again.

When the workaround did NOT work:
My .kdeglobals file had no entries for fonts, so everything was at system defaults.

When the workaround DID work:
- I went to Font settings and brought up the font dialog to just select the default fonts, and applying the changes.
- This put font entries in my .kdeglobals
- I deleted the new font-related occurrences of "Regular"
- I killed all running Konsole instances

After that Konsole renders intense colors as bold correctly.

Perhaps some KDE-related font cache had to get updated by font dialog, or the font entries in .kdeglobals.
Comment 8 Mike Lui 2018-03-27 18:46:51 UTC
To clarify, bold fonts works as expected with this entry in my .kdeglobals:

[General]
ColorScheme=Default
Name=Breeze
dbfile=/home/mdlui/.mozilla/firefox/xo4nvchd.default/places.sqlite
fixed=Hack,9,-1,0,50,0,0,0,0,0,
font=Noto Sans,10,-1,0,50,0,0,0,0,0,
menuFont=Noto Sans,10,-1,0,50,0,0,0,0,0,
shadeSortColumn=true
smallestReadableFont=Noto Sans,8,-1,0,50,0,0,0,0,0,
toolBarFont=Noto Sans,10,-1,0,50,0,0,0,0,0,



This did not render intense colors as bold:

[General]
ColorScheme=Default
Name=Breeze
dbfile=/home/mdlui/.mozilla/firefox/xo4nvchd.default/places.sqlite
Comment 9 Vadim A. Misbakh-Soloviov (mva) 2018-04-30 09:20:56 UTC
I also having than on Gentoo (so, not only arch and suse are affected).

And, the workaround about kdeglobals seems to work (although, I'm not sure if it was workaround of dropping ",Regular" helped, or it was also necessarily to switch all the fonts to Droid Sans in the font dialog (previously I had Roboto for all, and PragmataPro Mono for monospace).
Comment 10 Ahmad Samir 2018-04-30 15:02:37 UTC

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