Bug 454570 - Dead keys do not register outside of application launcher
Summary: Dead keys do not register outside of application launcher
Status: RESOLVED DUPLICATE of bug 411729
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keyboard (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2022-05-29 12:34 UTC by teadrinkingprogrammer
Modified: 2022-06-06 22:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Settings menu with English (US, intl., with dead keys) set as the only keyboard layout (74.53 KB, image/png)
2022-05-29 12:34 UTC, teadrinkingprogrammer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description teadrinkingprogrammer 2022-05-29 12:34:48 UTC
Created attachment 149313 [details]
Settings menu with English (US, intl., with dead keys) set as the only keyboard layout

SUMMARY
I do not know if this is the right place to file this bug, if it is incorrect, my apologies. 
I have changed my keyboard layout to English (US, intl., with dead keys). The layout is working as expected in the application launcher, but not in any other application as far as I can see. I tested: Settings, Kwrite, Firefox (native), Discover and Onlyoffice (Flatpak)


STEPS TO REPRODUCE
1. Set the only keyboard layout to English (US, intl., with dead keys)
2. Open Application launcher
3. Type " and <space>: this works
4. Open Kwrite
5. Type " and <space>: only a space

OBSERVED RESULT
A space
EXPECTED RESULT
a " character

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 36
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.11-300.fc36.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15,6 GiB of RAM
Graphics Processor: AMD Radeon RX 5700 XT
Comment 1 Nate Graham 2022-06-01 18:00:54 UTC
Can you paste the output of `env | grep QT_IM_MODULE`? Might be Bug 411729.
Comment 2 teadrinkingprogrammer 2022-06-01 19:12:20 UTC
(In reply to Nate Graham from comment #1)
> Can you paste the output of `env | grep QT_IM_MODULE`? Might be Bug 411729.

Output is:  
QT_IM_MODULE=ibus

Curiously, cat /env/environment returns nothing.
Comment 3 Nate Graham 2022-06-01 19:17:56 UTC
Yup, then you're experiencing Bug 411729. IBus is taking over and causing problems.

*** This bug has been marked as a duplicate of bug 411729 ***
Comment 4 teadrinkingprogrammer 2022-06-06 11:59:10 UTC
I have tried all the possible fixes on the issue 411729 page but it doesn't seem to fix it.
I have tried:
setting /etc/environment to:
INPUT_METHOD=ibus
GTK_IM_MODULE=ibus
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus

AND

QT_IM_MODULE=ibus

AND

QT_IM_MODULE=

and rebooting afterwards.
That didn't work. I tested in Firefox native  (no flatpak) if that could be that problem.
Am I missing something here?
Comment 5 Nate Graham 2022-06-06 17:32:10 UTC
After you set `QT_IM_MODULE` to nothing in /etc/environment can you verify that it was actually unset? What does `env | grep -i QT_IM_MODULE` say? If there's still a value there, then it's being set by something else.
Comment 6 teadrinkingprogrammer 2022-06-06 20:27:17 UTC
(In reply to Nate Graham from comment #5)
> After you set `QT_IM_MODULE` to nothing in /etc/environment can you verify
> that it was actually unset? What does `env | grep -i QT_IM_MODULE` say? If
> there's still a value there, then it's being set by something else.

I have set /env/environment to `QT_IM_MODULE=` and rebooted. Now it suddenly works. Probably missed something before then I think. Thank you for your help!
Comment 7 Nate Graham 2022-06-06 22:40:51 UTC
You're welcome!