SUMMARY STEPS TO REPRODUCE 1. On a Spanish keyboard, hit the key "´" followed by an a 2. 3. OBSERVED RESULT Adds a space and then the character "á" EXPECTED RESULT Should only produce an "á" without adding a space before it. Now it has become IMPOSSIBLE to type in Spanish. Operating System: openSUSE Tumbleweed 20211008 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.9-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.3 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics
This persisted across reboot and restarting Kate a few times. Then, after a few hours leaving the computer unattended and locking and unlocking screen (and I'm not 100% sure if it goes to sleep but I don't think it does), it went away WITHOUT restarting Kate. I'm starting to wonder if this is a variant of https://bugs.kde.org/show_bug.cgi?id=438820 / https://bugzilla.suse.com/show_bug.cgi?id=1187513
I would assume so. I have here a German keyboard and the á composition works in Kate. Sorry that you have such issues, but that must be some issue on your distro, like you linked below.
Right now the ONLY application where I observe the issue is Kate. The issue linked above had similar but different symptoms; it affected Kate and other applications, and I haven't been observing it for several weeks now. For all we know it could be unrelated and fixed. An issue more similar to this one (than the one linked above) but not identical (specifically: accented characters being duplicated: I typed "á" I would get "áá") initially affected one other application (Telegram Desktop) and appeared at the same time as this one in Kate. Every time I observed one I would observe also the other, and when one went away the other did too. However, the issue in Telegram Desktop is gone now, but this one in Kate persists. Any assumption about the different issues being related with one another is speculation. The default assumption right now, until there's anything to suggest otherwise, should be that this is an issue in Kate, which is the only application where the issue is currently observed, and the only one where the issue *exactly as described here* has ever been observed. (that I know of, of course).
Here's something interesting. If I restart the system with Kate open (which will cause it to be automatically open at startup), then composition in Kate will be broken in a different way, and typing accented characters will result in plain unaccented characters. E.g. "`"+"a"="a". After that, if I restart Kate, then it start behaving as described in this report, that is, it will add a space before every accented character ("`"+"a"=" a").
I am seeing the same behavior in Kubuntu 21.10, plasma 5.23.3 in Wayland. The problem in my system happens for the "latam" layout (a variation of Spanish), the French layout, and the german layout when "dead" or composition keys are used. It affects other programs that inherit the kate part (develop, kile, e.g.) Christoph, are you working in X11 or Wayland?
(In reply to Victor Sanchez from comment #5) > I am seeing the same behavior in Kubuntu 21.10, plasma 5.23.3 in Wayland. > The problem in my system happens for the "latam" layout (a variation of > Spanish), the French layout, and the german layout when "dead" or > composition keys are used. > > It affects other programs that inherit the kate part (develop, kile, e.g.) > > Christoph, are you working in X11 or Wayland? BTW, I am using kate from 21.08.2
Just to add, the problem is present both in X11 and Wayland. Only with Kate, Kwrite, and derivatives. Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-20-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620
That means e.g. in other Qt powered things like QtCreator or let's say Konsole you can type without these issues? I can't reproduce this either on X11 nor on Wayland.
(In reply to Christoph Cullmann from comment #8) > That means e.g. in other Qt powered things like QtCreator or let's say > Konsole you can type without these issues? > > I can't reproduce this either on X11 nor on Wayland. Correct. It works well in other KDE apps like Krita and konsole and in qt applications like QtCreator and texstudio... very strange! Do you need me to check something else? This is my configuration, now running wayland: Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-20-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620
The way it types is different: when typing a "dead" character in konsole nothing shows up until the following vowel appears, ie. typing "'" shows nothing until I press "a" creating "á" the expected result. When typing in kate, typing the "dead" character "'" shows the "´" and then when the vowel is typed the character is erased, the space is left, and the correct letter appears "á" but a space is left before.
If it is of any help, my distribution has libinput 1.18.1 and libudev 248.3-1ubuntu8 and libevdev2 1.11.0+dfsg-1build1
If you're not going to fix this anytime soon, please release an update that rolls everything back to the last version before the regression. Whatever improvements or even bugfixes there have been since them, there's no way they outweigh this. Kate is now completely unusable (unless you only write in English). The default text editor in many Linux distributions. Unusable.
Hello php4fan@gmail.com The problem here is that we do not know what the problem is or, if it is a Kate bug, when it has been introduced... how far back should be go? Can this be reproduced on Kubuntu 20.10 does it reproduce on early Kubuntu 21.04?...
On OpenSUSE Tumbleweed I started observing this at the time of my report (i.e. October 18). I don't always install all updates immediately, so it may have appeared a few days or weeks earlier. Obviously I have no idea what version of Kate that is. Previously there had been similar but different composition-related bugs, but those (besides not being identical in symptoms) were affecting several other applications as well as Kate, and are since fixed: https://bugzilla.suse.com/show_bug.cgi?id=1187513
I have the same here with German umlauts. It wasn't there in early October. I've seen some input related commits, but can't tell which one could be the culprit. I think this bug is CRITICAL
I would for sure like to help you to fix this, but I can neither reproduce that with 21.08/5.88.0 nor with the current development branch. (on neither Wayland nor X11)
If you're trying to reproduce, do you use a dead-key keyboard? It is NOT simply umlauts, it is the dead keys that do not work in general. A little history shows that the initial direct input from the keyboard was replaced by the ibus framework. I realized this as the character of my US_intl keyboard would not directly appear, but you would see first ' and then type e. They would stand for a ms as 'e and merge to é. In kate does precisely that. First appears " plus a will give ä. First " appears on the screen, then a, then the system merges them rightward to ä, leaving the initial field for " as a space. Then I tried to have " as a character by typing " plus space. Again, this merges rightwards and one gets _" with the additional space. So there MUST be something wrong in kate with the use if ibus and dead key keyboards. If you're not using dead keys, it will be impossible to reproduce IMHO.
If I use Meta-p for ö, it works as expected. So it MUST be in the ibus dead key handling and its use in kate. It works normally in other kde apps not using ibus (like kbibtex field filling), but e.g. kile, the latex editor, is equally affected. IMHO there could be an incompatible change either in ibus or in kate-part.
I use here dead keys, e.g. ' + later a ;) But perhaps the issue is that I don't use ibus, at least I am not aware of using that.
(In reply to Christoph Cullmann from comment #19) > I use here dead keys, e.g. ' + later a ;) By ' you mean ` or ´, right?
Yes, ;=) after typing space that is here converted that way.
Could somebody try the patch from bug 357062? Thanks!
Ok, I can reproduce on Wayland now. My issue was mostly that no ibus did run ;=) If you do e.g. in a terminal ibus-daemon -drxR then configure ibus e.g. via the panel applet that for me did popup then run export QT_IM_MODULE=ibus kwrite you get interesting behavior. For me ' + e (bugzilla replaces the right char here) will lead to é, but with some "space" before the e... And other such strange things. Guess the input method variant of the input is really broken :/
*** Bug 447584 has been marked as a duplicate of this bug. ***
Hmm, funny enough, it not always "doesn't work" here. I have no typed a lot of `e that just combined and some not, in the same session :/ Strange :(
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/237
I would appreciate if people could test: https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/237 One will loose the properly adjusted cursor for IM text but for me this fixes the issue. But perhaps I didn't fix all cases or this is not acceptable.
Thanks for suggesting a fix
Created attachment 144901 [details] ibus-setup workaround Just FYI, While we're working on a fix, you may workaround it by unchecking "embed preedit in application" in ibus-setup for now.
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/239
Git commit 3ebdf31474b8d816d5ca7deedd1a23254af2b5c4 by Christoph Cullmann, on behalf of Weng Xuetian. Committed on 28/12/2021 at 18:33. Pushed by cullmann into branch 'master'. Validates the input method attributes received from input method. A buggy input method may send invalid values to the widget. E.g. out of range cursor position. Make sure we don't use such value directly. M +7 -5 src/view/kateviewinternal.cpp https://invent.kde.org/frameworks/ktexteditor/commit/3ebdf31474b8d816d5ca7deedd1a23254af2b5c4
*** Bug 444473 has been marked as a duplicate of this bug. ***
*** Bug 445701 has been marked as a duplicate of this bug. ***
(In reply to Weng Xuetian from comment #29) Yes, that fixed it for me. So thanks a lot! I started ibus-setup as a normal user and un-ticked the box as described. Additionally, the input is much faster than before for normal ISO-8859-15 charcter set input (I use UTF-8, but my language skills are limited to the European character set). Thanks for finding the workaround. I think I will not enable "embed preedit ..." again, even after a workaround. I think (as we are in a KDE bugtracker), it is also a bug that ibus-setup can not be found in the KDE settings application.