https://bugzilla.redhat.com/show_bug.cgi?id=1916743
--- Comment #14 from Mike FABIAN mfabian@redhat.com --- My guess is that you are using KDE under Wayland and that the dead key support in KDE under Wayland doesn't work.
But if you use ibus, that is a workaround because then you can use the dead key support from ibus which works under KDE Wayland as well.
That doesn't require ibus-table though, any ibus input method will do.
This bug is about f33 but as I had a f34 virtual machine handy I tested there first and found:
KDE under Wayland:
Dead keys work only when ibus is used or in gtk programs like gedit.
Let’s assume ibus is setup correctly and running.
If you then start kate like this: env -u QT_IM_MODULE then dead keys don't work in kate, typing a dead acute shows nothing, typing an a next just gives an a as the final result. Starting kate as above, without QT_IM_MODULE=ibus in the environment, prevents the use of ibus in kate, so dead key support can come only via something else like the Xorg compose support or something KDE/Qt does. And this doesn't seem to work in KDE when using wayland
When starting kate like this: env QT_IM_MODULE=ibus kate and ibus is running, then dead keys work in kate typing a dead acute shows the preview of the acute and then typing an a gives á. When QT_IM_MODULE=ibus is in the environment and ibus is running, the dead key support of ibus is used which gives you the dead key preview and works in KDE Wayland as well.
KDE under Xorg:
Dead keys work with or without ibus. When ibus is used the preview is shown, when ibus is not used there is no preview, i.e. typing a dead acute shows nothing but when the next typed character is an a one gets á.
To use the dead key support in ibus, ibus-table is not necessary. You can configure ibus with any input methods you like it does not have to be ibus-table.