https://bugs.kde.org/show_bug.cgi?id=420522
--- Comment #9 from Luiz Angelo De Luca <luizl...@gmail.com> --- (In reply to Nate Graham from comment #8) > Not quite the same as Bug 411729, but seems related. I'm affected by both on different systems. That one in OpenSUSE Tumbleweed (wayland only) and this one only in Ubuntu. It's difficult to isolate this problem as it only happens with software launched by session restore. If I launch a new one, even from inside a konsole that is manifesting the problem, the new process work as expected. In the case of Ubuntu, QT_IM_MODULE is defined as ibus, even for those problematic processes. I gave another try to debug it: I noticed that there is no ibus-daemon running. The moment I launch it, konsole starts to type accent chars correctly. If I kill ibus-daemon afterwards, it stops to type anything. It looks like it started in a "basic input fallback mode" when it failed to use ibus. After KDE is up, KDE might offer another option for input, which new konsole processes take and it works as expected. It is just a guess. Now, as I know it is related to ibus, I grepped my .config and found: .config/systemsettingsrc: ... [Open-with settings] CompletionMode=5 History=ibus-daemon --xim --replace --panel=/usr/lib/ibus/ibus-ui-gtk3 ... .config/autostart/ibus-daemon.desktop: ... Exec=ibus-daemon --xim --replace --panel=/usr/lib/ibus/ibus-ui-gtk3 ... If I manually run that line after ibus-daemon was manually started, konsole returns to the broken state. The "--panel=/usr/lib/ibus/ibus-ui-gtk3" is the one generating the issue. That autostart file is old, from 2017, probably from the time I used unity or gnome3. I disabled that autostart and now it works as expected. What is broken? QT? Ibus? Someone that added that autostart and left it there? -- You are receiving this mail because: You are watching all bug changes.
