[konsole] [Bug 343539] "Draw intense colors in bold font" not respected with a fresh installation

Mike Lui bugzilla_noreply at kde.org
Fri Apr 7 06:27:08 UTC 2017


https://bugs.kde.org/show_bug.cgi?id=343539

Mike Lui <mike.d.lui at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike.d.lui at gmail.com

--- Comment #17 from Mike Lui <mike.d.lui at gmail.com> ---
(In reply to Roberto Benfatto from comment #16)
> I'm giving a bump on this, I actually triggered this bug today, after a long
> time having it work as expected. I'm on Arch Linux, using Konsole 16.12.3
> 
> Before today, I was using Fira Code as font in Konsole profile, and Fira
> mono in sistem wide settings for monospaced fonts. It's important to say
> that I set up my system wide monospace settings when I installed my system,
> back in august 2016. Since then, I did not change it from there, but I
> rather changed the font from the specific application I wanted the font on.
> 
> Today I changed the font to Fira Mono in the konsole profile settings, and
> suddendly the "bold on intense" functionality broke. I changed it back to
> fira Code, but I had to restart konsole to have it working again, all of
> these changes where made from Konsole profile settings.
> 
> Then, out of curiosity, I changed the monospaced font system wide in system
> settings from Fira Mono to Fira Code, and that was the thing that made
> everything stop working and unable to get it working again. After that I
> tried restarting konsole, reverting system wide settings for monospaced
> fonts, reinstalled fira fonts, but nothing worked.
> 
> It's a thing that I can effectively get the bold on intense functionality
> working only when I'm using the "monospace" family fonts, wich I think uses
> Dejavu Sans Mono as standard font. But if I specify Dejavu Sans Mono
> instead, bold on intense stops working again, even if it was previously
> working when used with monospace family.
> 
> I hope this helps somehow.

This specific issue is a Qt issue(In reply to Roberto Benfatto from comment
#16)
> I'm giving a bump on this, I actually triggered this bug today, after a long
> time having it work as expected. I'm on Arch Linux, using Konsole 16.12.3
> 
> Before today, I was using Fira Code as font in Konsole profile, and Fira
> mono in sistem wide settings for monospaced fonts. It's important to say
> that I set up my system wide monospace settings when I installed my system,
> back in august 2016. Since then, I did not change it from there, but I
> rather changed the font from the specific application I wanted the font on.
> 
> Today I changed the font to Fira Mono in the konsole profile settings, and
> suddendly the "bold on intense" functionality broke. I changed it back to
> fira Code, but I had to restart konsole to have it working again, all of
> these changes where made from Konsole profile settings.
> 
> Then, out of curiosity, I changed the monospaced font system wide in system
> settings from Fira Mono to Fira Code, and that was the thing that made
> everything stop working and unable to get it working again. After that I
> tried restarting konsole, reverting system wide settings for monospaced
> fonts, reinstalled fira fonts, but nothing worked.
> 
> It's a thing that I can effectively get the bold on intense functionality
> working only when I'm using the "monospace" family fonts, wich I think uses
> Dejavu Sans Mono as standard font. But if I specify Dejavu Sans Mono
> instead, bold on intense stops working again, even if it was previously
> working when used with monospace family.
> 
> I hope this helps somehow.

I noticed your issue on ArchLinux recently, too. I believe both of our issues
are related to Qt, so beyond Konsole. I recently asked about it on the forums
and might make a Qt bug report if it looks to be the root cause.

https://forum.qt.io/topic/78036/bold-fonts-not-working-for-many-fixed-width-fonts-in-linux

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the konsole-devel mailing list