SUMMARY When the compose key is activated, an underlined middle dot character (·) and a blank space next to it are shown. This seems to cause problems in various places. Worst is in LibreOffice, where if the compose key is invoked at the end of a line with other lines below it, after the key sequence is entered the cursor just ends up on the next line and the · remains, while the character the user tried to enter does not appear. (If done at the end of the final line of a document or the middle of a line, the character still does appear properly.) This makes editing very frustrating. The display of the middle dot and space also seems to causes other issues, such as when editing the names of files on the desktop. When the compose key is invoked at the end of a file name, the cursor jumps to the beginning (but at least the character can successfully be typed). This is also why I think that this is not just a LibreOffice bug. Using the compose key used to not show any visual feedback (I think? Maybe I'm wrong there), so perhaps this problem was introduced when this feedback was added. (Apologies if this bug was not filed in the correct place.) STEPS TO REPRODUCE 1. Open LibreOffice Writer 2. Hit Enter a few times to create some lines 3. Click on any line besides the last one 4. Invoke the compose key to make a special character OBSERVED RESULT A · will appear and stay there, while the cursor moves down to the next line. EXPECTED RESULT The special character the user wanted to make using the compose key should appear. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2
Created attachment 147012 [details] LibreOffice compose key attempt The compose key was invoked on the third line to make a "é"; instead the dot remains and the cursor moved down a line.
Created attachment 147013 [details] Using the compose key to edit a desktop file name The compose key was invoked at the end of this file name: note the cursor moves to the front (though it does move back once the character is created).
These are individual app-specific bugs. So you would need to report that to the LibreOffice folks. Let's use this to track the issue renaming files on the desktop. I cannot reproduce that issue on Wayland with Plasma 5.24. 5.22 is officially unsupported; any chance you could upgrade to newer versions using the Kubuntu backports PPA and try again?
Understood, thanks, I've filed a separate one with LibreOffice (https://bugs.documentfoundation.org/show_bug.cgi?id=147647), and I've since realized it only affects Writer, not other LO applications. I have installed the Kubuntu backports via the PPA. Which seems to have broken some things, including lattedock :( The bug with the desktop file renaming (cursor moving temporarily to the beginning of the filename), however, is still there. Linux/KDE Plasma: Kubuntu 21.10 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 I am running X11 though, not Wayland.
Thanks. What font and font size are you using in Plasma?
(In reply to Nate Graham from comment #5) > Thanks. > > What font and font size are you using in Plasma? I was using the Ubuntu font at 10pt. I did reset to Noto Sans, the default, but the issue is the same with that one too.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!