Are you sure the selected font has a "bold" variant? You can check this in the "Font Style" column of the font selector dialog.

Yes, I selected "DejaVu Sans Mono" in Book style as my default font.

I have the same issue using Terminus TTF font. I also have Yakuake installed which is using konsolepart4 and with the same font settings works properly.

I'm experiencing this too. I can confirm that it works in Yakuake, but not Konsole. Also, I tried toggling the checkbox on and off (restarting Konsole in between), as suggested by Médéric, but that doesn't work for me.

Okay, a little more info. This seems to work with some fonts, but not others. One example of a font which it used to work for before a recent update is https://github.com/DeLaGuardo/Inconsolata-LGC.

This certinaly looks like a regression due to Qt5 / KF5 porting. For more info on the difference between yakuake and konsole on my systems, take a look at this:

% ldd /usr/bin/yakuake |grep font
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f389c572000)

% ldd /usr/bin/konsole |grep font
[nothing]

% ldd /usr/bin/yakuake |grep -i qt
        libQtCore.so.4 => /usr/lib/libQtCore.so.4 (0x00007f5b5e948000)
        libQtDBus.so.4 => /usr/lib/libQtDBus.so.4 (0x00007f5b5e6cb000)
        libQtGui.so.4 => /usr/lib/libQtGui.so.4 (0x00007f5b5d9dc000)
        libQtXml.so.4 => /usr/lib/libQtXml.so.4 (0x00007f5b5ce70000)
        libQtNetwork.so.4 => /usr/lib/libQtNetwork.so.4 (0x00007f5b5c40a000)
        libQtSvg.so.4 => /usr/lib/libQtSvg.so.4 (0x00007f5b5c1b2000)
        libdbusmenu-qt.so.2 => /usr/lib/libdbusmenu-qt.so.2 (0x00007f5b5aa88000)

% ldd /usr/bin/konsole |grep -i qt
        libQt5Widgets.so.5 => /usr/lib/libQt5Widgets.so.5 (0x00007f225ecc1000)
        libQt5Gui.so.5 => /usr/lib/libQt5Gui.so.5 (0x00007f225e77e000)
        libQt5Core.so.5 => /usr/lib/libQt5Core.so.5 (0x00007f225e2b0000)
        libQt5PrintSupport.so.5 => /usr/lib/libQt5PrintSupport.so.5 (0x00007f22620c7000)
        libQt5Xml.so.5 => /usr/lib/libQt5Xml.so.5 (0x00007f2262087000)
        libQt5Network.so.5 => /usr/lib/libQt5Network.so.5 (0x00007f225cd3f000)
        libQt5DBus.so.5 => /usr/lib/libQt5DBus.so.5 (0x00007f2262006000)
        libphonon4qt5.so.4 => /usr/lib/libphonon4qt5.so.4 (0x00007f225cabc000)
        libQt5Svg.so.5 => /usr/lib/libQt5Svg.so.5 (0x00007f2261faa000)
        libQt5X11Extras.so.5 => /usr/lib/libQt5X11Extras.so.5 (0x00007f2261fa4000)
        libdbusmenu-qt5.so.2 => /usr/lib/libdbusmenu-qt5.so.2 (0x00007f22574b3000)

A bit more information, in case it's helpful. Just confirming that after downgrading to Arch's kdebase-konsole 4.14.3 package, with exactly the same font as above (Inconsolata LGC), everything works as expected. In case it's useful, with a working (old) version:

% konsole --version
Qt: 4.8.6
KDE Development Platform: 4.14.5
Konsole: 2.14.2

% ldd /usr/bin/konsole |grep font
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007fda6e62a000)

% ldd /usr/bin/konsole |grep -i qt
        libQtCore.so.4 => /usr/lib/libQtCore.so.4 (0x00007fac7e1cb000)
        libQtGui.so.4 => /usr/lib/libQtGui.so.4 (0x00007fac7d2bf000)
        libQtNetwork.so.4 => /usr/lib/libQtNetwork.so.4 (0x00007fac7c821000)
        libQtDBus.so.4 => /usr/lib/libQtDBus.so.4 (0x00007fac7c5a4000)
        libQtXml.so.4 => /usr/lib/libQtXml.so.4 (0x00007fac7c0ea000)
        libQtSvg.so.4 => /usr/lib/libQtSvg.so.4 (0x00007fac7be92000)
        libdbusmenu-qt.so.2 => /usr/lib/libdbusmenu-qt.so.2 (0x00007fac7a34d000)

Thanks!

In my Kubuntu 14.10 system, this option only works with the default Monospace font but not the other fonts.

I'm seeing the same lack of font WEIGHT-change on 'bold' in

	lsb_release -rd
		Description:    openSUSE 13.2 (Harlequin) (x86_64)
		Release:        13.2

	konsole --version
		Qt: 4.8.6
		KDE Development Platform: 4.14.5
		Konsole: 2.14.2

	bash --version
		GNU bash, version 4.3.33(1)-release (x86_64-suse-linux-gnu)
		...

There's no bold-ing with any of the fonts I've tried -- monospace or other.

and, fwiw,

ldd /usr/bin/konsole |grep -i qt
        libQtCore.so.4 => /usr/lib64/libQtCore.so.4 (0x00007fedfe2ed000)
        libQtGui.so.4 => /usr/lib64/libQtGui.so.4 (0x00007fedfd40e000)
        libQtNetwork.so.4 => /usr/lib64/libQtNetwork.so.4 (0x00007fedfc908000)
        libQtDBus.so.4 => /usr/lib64/libQtDBus.so.4 (0x00007fedfc68a000)
        libQtXml.so.4 => /usr/lib64/libQtXml.so.4 (0x00007fedfbf08000)
        libQtSvg.so.4 => /usr/lib64/libQtSvg.so.4 (0x00007fedfbcb0000)
        libdbusmenu-qt.so.2 => /usr/lib64/libdbusmenu-qt.so.2 (0x00007fedf9f74000)

Any news on this? This bug is a blocker to upgrading to KF5 for me.

If I uncheck "Draw intense colors in bold font" and check it again it works fine. It looks like the option is checked by default but not activated.

--
If this works for some people, then the code is wrong somewhere.  I'll see what I can find out.

For me nothing makes bolded fonts work, no matter what font family used (apart from *all*-bold fonts of course). Checking and unchecking doesn't work either.

I tested it with the command 
> echo `tput bold`bold`tput sgr0`
using konsole v2.14.2.

On other terminals it works for me.

On my up-to-date Arch Linux system (Qt 5.4.1, KDE Frameworks 5.10.0, Konsole 15.04.0, zsh 5.0.7), the only three fonts which I've found where the "Draw intense colors in bold font" rendering works in Konsole, are:

  Monaco
  Monospace
  Nimbus Mono

Whereas it *doesn't* work with at least these fonts:

  Andale Mono
  Bitstream Vera Sans Mono
  Consolas
  DejaVu Sans Mono
  Droid Sans Mono
  FreeMono
  Inconsolata
  Liberation Mono
  Oxygen Mono
  Terminus
  Ubuntu Mono

When I select the bold variant of any of those fonts as my Konsole font, then *all* text is rendered in bold. However when I select their "Regular/Book" variant, nothing is *ever* rendered in bold.
Checking and unchecking the "Draw intense colors in bold font" option doesn't make it work either.

I think it's especially bad that it doesn't work with the Oxygen font, since that is supposed to be the 'official' KDE font (and I like it).

Yes, I echo Sam's experience. Also, Kurt's "toggle it off and back on again" doesn't work for me. It seems to be deeper than that. Still running an old 4.x version of konsole because of this :-(

Any news on this?

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.

(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

Created attachment 104994 [details]
Difference between kdeglobals before and after font change

I followed Mike's qt bug report and as he suggested, I tried to look in kdeglobals. I took an old KDE5 installation where this bug does not appear, I updated it to the latest arch release. Then, confirming that it indeed works if I don't touch anything, I changed the monospace font in the system settings, then I compared the new kdeglobals file with the old one. I attached the diff, as you can see all fonts where changed to a new format in the configuration file, and that is the thing that breaks everything.
To double check, I restored the old kdeglobals file and bold fonts started working again.

I think that the problem resides exactly there, as if konsole and other programs (I suppose a lot of programs are affected by this) cannot apply a different font style if one is explicitly specified in kdeglobals.
So, if this is the case, that's not a konsole only bug.

Looks like the issue you pinpointed is already tracked by Bug 378523, and we're centralizing duplicate reports there. So I'll do that here too. Thanks for the investigation!

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

Since this ticket is older than the issue referenced in comment #20, which is the result of a change in Qt 5.8, it cannot be a duplicate.

Let's hope the original issue just vanished.

Yes, that was my conclusion, since all the most recent comments were describing the bug I duped this to.