Hello, Those apps left open and started by session restore on the next login cannot type accented chars. However, keyboard mapping seems to be correct as I can insert layout specific chars like 'ç' and any 'alt gr' variations. It does not happen with firefox but it affects konsole and kwrite. If I close them and reopen, it can type any chars again. I already reported this https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1873167 but without an answer.
That's surprising. Can you give full steps to reproduce Also could you include output of cat /proc/`pidof konsole`/environ | tr '\0' '\n' for a working and broken konsole.
marking as needs info
Created attachment 130100 [details] env from konsole where accents do not work
(In reply to David Edmundson from comment #1) > That's surprising. > > > Can you give full steps to reproduce I don't know how to reproduce it. I'm upgrading my ubuntu installation for some years and I installed kubuntu packages (while still using ubuntu gdm). > Also could you include output of > > cat /proc/`pidof konsole`/environ | tr '\0' '\n' > > > for a working and broken konsole. ~ $ diff -u konsole.err konsole.ok | grep -v '^ ' --- konsole.err 2020-07-13 22:16:30.544985468 -0300 +++ konsole.ok 2020-07-13 22:16:41.496413493 -0300 @@ -3,16 +3,15 @@ +DESKTOP_STARTUP_ID=zipper;1594689313;826606;50572_TIME32863387 -GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/luizluca/.gtkrc-2.0:/home/luizluca/.config/gtkrc-2.0 -GTK_RC_FILES=/etc/gtk/gtkrc:/home/luizluca/.gtkrc:/home/luizluca/.config/gtkrc @@ -55,7 +54,7 @@ -XAUTHORITY=/tmp/xauth-1000-_1 +XAUTHORITY=/run/user/1000/gdm/Xauthority I'll attach the files.
Created attachment 130101 [details] env from konsole where accents do work
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!
Just removing wait for info
Not quite the same as Bug 411729, but seems related.
(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?
If this issue only appears when using the autostart file, it's probably nothing we can or need to do about.