Since then, I have opened a fix attempt upstream [1]. That could be a better candidate for patch to back-port.
[1]: https://invent.kde.org/utilities/konsole/-/merge_requests/1199 On Wed, 08 Apr 2026 17:03:11 +0200 Paul Mabileau <[email protected]> wrote: > Package: konsole > Version: 4:25.04.2-1 > Severity: normal > Tags: patch upstream > X-Debbugs-Cc: [email protected] > > Dear Maintainer, > > This is basically a repeat of the [upstream bug report] that very > directly concerns me as well. Indeed, when upgrading to 4:25.04.2-1 last > year while having the "word mode" enabled in the settings to get > ligature rendering to work, the exact same symptoms could be observed: > the width and spacing of characters would get very broken, with > differences if they were before or after the cursor, making it quite > unusable. Some videos are included in the [upstream bug report] that > show the issue well. I am therefore filing this against 4:25.04.2-1 even > though this was partially generated by `reportbug` for 4:24.12.0-1+b1. > > A simple workaround is to disable the option, hence the "normal" > severity of the current bug report. However, doing so also disables > ligatures and I would really like to keep them. > > I have then downgraded and held the `konsole` and `konsole-kpart` > packages back to the latest version that does not have the issue > (4:24.12.0-1+b1) until an upstream fix is published in the hope it would > be relatively soon considering the nature of the bug. However, we are a > year later and it still does not seem on the path to being resolved. To > be fair though, I haven't tried the latest releases because rolling back > is tedious, so it could already be fixed, but if so I would have > expected that to be reported in the [upstream bug report]. > > That worked fine for quite a while, but the new problem I find myself in > is that holding these two packages back now starts to indirectly hold > about 210 other KDE and Qt packages back also since their latest > updates. While that does not seem to break anything for now, it is a bit > bothersome, but more importantly I fear that it will get to be more and > more of a problem as time goes on, and so I would like to do something > about it if possible. > > The latest messages in the [upstream bug report] indicate that some > people seem to already have identified a specific commit at fault and > that reverting it fixes the issue. The point of the current bug report > is thus: would it therefore be possible to attempt including the > upstream-reported patch in the Debian builds? It would enable me to > resume upgrading my KDE/Qt packages again, which would be nice. > > If needed, I can definitely run some temporary builds in order to > confirm that the patch still works when applied on the latest releases > and when running it using my configuration. I could also try building > them myself, but I'm not sure that will be easy. > > Thank you in advance, > Paul. > > [upstream bug report]: https://bugs.kde.org/show_bug.cgi?id=503087 > > > -- System Information: > Debian Release: forky/sid > APT prefers testing
