https://bugs.kde.org/show_bug.cgi?id=491631
--- Comment #3 from Ingo Klöcker <kloec...@kde.org> --- I can confirm a very similar problem when using the Compose key to enter special characters. Observation: * In all cases I type Compose Key followed by " followed by o (which should result in ö) * I can confirm that entering ö with Compose Key works if it's the first character. * I can also confirm that trying to enter ö as second character doesn't work. The result is "o. * Entering aaö results in aa"o I think I just found the pattern. If the list of possible completions is shown then entering ö fails. If no completions are shown (i.e. when entering the very first character or when no payee/payer matches what has been entered so far) then entering ö succeeds. I see the same problem for Tags. I don't see the problem for Category. I have never experienced this problem in any other KDE or Qt applications (or any non-Qt applications like Firefox, LibreOffice, etc.) and I'm using Compose for entering umlauts everywhere. (I should really debug this myself. It's been bothering me for a long time.) -- You are receiving this mail because: You are the assignee for the bug.