Bug 482596 - The bold text on my terminal are blue
Summary: The bold text on my terminal are blue
Status: RESOLVED INTENTIONAL
Alias: None
Product: konsole
Classification: Applications
Component: font (show other bugs)
Version: 24.02.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: qt6
: 483347 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-03-06 22:08 UTC by yunusaydin590
Modified: 2024-03-12 15:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
The bug itself (8.05 KB, image/png)
2024-03-06 22:08 UTC, yunusaydin590
Details
The bug without any terminal theme, please ignore the extra newline between echo and its output (5.32 KB, image/png)
2024-03-06 22:14 UTC, yunusaydin590
Details

Note You need to log in before you can comment on or make changes to this bug.
Description yunusaydin590 2024-03-06 22:08:17 UTC
Created attachment 166513 [details]
The bug itself

SUMMARY
The title is pretty self-explanatory, whenever a program tries to write a bold text without specifying a color, it comes out as blue instead of white.

STEPS TO REPRODUCE
1. Run a program that prints a bold text

OBSERVED RESULT
Bold text is printed as blue

EXPECTED RESULT
Bold text should be printed as just bold

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 6.1.71-1-lts (64-bit)
(available in About System)
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
I've tested this with fish, bash and zsh. I also tried disabling my terminal theme, but it didn't fix it.
Comment 1 yunusaydin590 2024-03-06 22:14:44 UTC
Created attachment 166514 [details]
The bug without any terminal theme, please ignore the extra newline between echo and its output
Comment 2 fanzhuyifan 2024-03-07 18:13:45 UTC
This uses the intense color setting, which defaults to blue. You can change that edit current profile - appearance - edit
Comment 3 fanzhuyifan 2024-03-12 15:47:07 UTC
*** Bug 483347 has been marked as a duplicate of this bug. ***