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 APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.19.10+deb14-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_AUX Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages konsole depends on: ii kio6 6.23.0-2 hi konsole-kpart 4:24.12.0-1+b1 ii libc6 2.42-14 ii libkf6colorscheme6 6.23.0-1 ii libkf6configcore6 6.23.0-2 ii libkf6configgui6 6.23.0-2 ii libkf6configwidgets6 6.23.0-1 ii libkf6coreaddons6 6.23.0-1 ii libkf6crash6 6.23.0-1 ii libkf6dbusaddons6 6.23.0-1 ii libkf6globalaccel6 6.23.0-1 ii libkf6guiaddons6 6.23.1-1 ii libkf6i18n6 6.23.0-2 ii libkf6iconthemes6 6.23.0-1 ii libkf6kiowidgets6 6.23.0-2 ii libkf6notifyconfig6 6.23.0-1 ii libkf6service-bin 6.23.1-1 ii libkf6service6 6.23.1-1 ii libkf6widgetsaddons6 6.23.0-1 ii libkf6windowsystem6 6.23.0-2 ii libkf6xmlgui6 6.23.0-1 ii libqt6core6t64 6.9.2+dfsg-4+b1 ii libqt6gui6 6.9.2+dfsg-4+b1 ii libqt6widgets6 6.9.2+dfsg-4+b1 ii libstdc++6 16-20260322-1 konsole recommends no packages. Versions of packages konsole suggests: pn lrzsz <none> -- no debconf information
