Bug 504057 - Konsole font stuck together and rendered improperly in 25.01
Summary: Konsole font stuck together and rendered improperly in 25.01
Status: RESOLVED DUPLICATE of bug 503087
Alias: None
Product: konsole
Classification: Applications
Component: font (other bugs)
Version First Reported In: 25.04.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-11 13:38 UTC by Erwin Iosef
Modified: 2025-05-15 02:56 UTC (History)
2 users (show)

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

Attachments
Screenshot of font bug 1 (17.80 KB, image/png)
2025-05-11 13:38 UTC, Erwin Iosef 		Details
Font bug 2 (16.47 KB, image/png)
2025-05-11 13:38 UTC, Erwin Iosef 		Details
font bug in vim text editor (1.01 MB, video/x-matroska)
2025-05-11 13:38 UTC, Erwin Iosef 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Erwin Iosef 2025-05-11 13:38:12 UTC 
Created attachment 181173 [details]
Screenshot of font bug 1

SUMMARY
The terminal font after the upgrade to 25.01 results in the text being "stuck" together and mushed a bit. Downgrade to konsole 24.12.3 fixes it and clearing the ~/.cache beforehand didn't help either. The default theme is also corked.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Comment 1 Erwin Iosef 2025-05-11 13:38:28 UTC 
Created attachment 181174 [details]
Font bug 2
Comment 2 Erwin Iosef 2025-05-11 13:38:56 UTC 
Created attachment 181175 [details]
font bug in vim text editor
Comment 3 Erwin Iosef 2025-05-11 15:55:21 UTC 
I found the problem, the bug triggers when word mode is enabled. Otherwise the text looks normal but still a bit.. merged and unclarified or something.
Comment 4 Daniel Petrov 2025-05-11 16:05:44 UTC 
See Bug 503087
Comment 5 John Kizer 2025-05-15 02:56:02 UTC 
Nice catch! Merging these together to keep discussion and resolution steps together under a single report. Thanks!

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