Bug 510676

Summary: Konsole: bug in ANSI escape sequences: instead of bold a blue color will shown
Product: [Applications] konsole Reporter: Christoph Dunschen <christoph.dunschen>
Component: generalAssignee: Konsole Bugs <konsole-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: ninjalj
Priority: NOR    
Version First Reported In: 25.08.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Above is LXTerminal with correct ouput, below Konsole not

Description Christoph Dunschen 2025-10-16 09:16:33 UTC 
Created attachment 185834 [details]
Above is LXTerminal with correct ouput, below Konsole not

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
Blue color instead of bold if using ANSI escape sequences

STEPS TO REPRODUCE
1. Open Konsole
2. See screenshot "konsole_bold.jpg"
3. Enter: echo -e '\033[1mYOUR_STRING\033[0m'
4. Or: python and enter print("\33[1m TEST \033[0m Bold on")

OBSERVED RESULT
See screnshot "konsole_bold.jpg", below result

EXPECTED RESULT
See screnshot "konsole_bold.jpg", above result (like in LXTerminal)

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.10.0

ADDITIONAL INFORMATION
I use Default settings for Konsole
Comment 1 Christoph Dunschen 2025-10-16 09:17:37 UTC 
Comment on attachment 185834 [details]
Above is LXTerminal with correct ouput, below Konsole not

Above LXTerminal is OK,
below Konsole not
Comment 2 Christoph Dunschen 2025-11-04 15:50:02 UTC 
Latest Konsole version 25.08.2 still has the bug too.
Comment 3 ninjalj 2025-11-08 12:53:39 UTC 

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