--- Comment #4 from ubach <pa_ubach(a)alum.mit.edu> ---
Hi Mike! Thanks for your support.
Let me clear something out first. As I wrote in the bug report, I am using the
Scientific Spin of Fedora, therefore the desktop environment is KDE, not Gnome.
Having said that, I'll try to answer your questions.
Did you only install the packages or also add one of the ibus-table
methods in the gnome control center?
These are the history logs of DNF when I dealed with this issue.
Instal·la ibus-wayland-1.5.23-2.fc33.x86_64 @updates
Instal·la ibus-table-1.12.1-1.fc33.noarch @fedora
Instal·la ibus-table-code-1.3.11-3.fc33.noarch @fedora
Instal·la ibus-table-latin-1.3.11-3.fc33.noarch @fedora
Instal·la ibus-table-others-1.3.11-3.fc33.noarch @fedora
This is certainly not related to ibus-table.
Can you try to remove the ibus-table packages again and install
When checking for this package, this is what comes out:
[ubach@Euler ~]$ dnf info ibus-typing-booster
Última comprovació del venciment de les metadades: fa 0:03:33 el dijous, 18 de
febrer de 2021, 18:48:58.
Name : ibus-typing-booster
Version : 2.10.4
Llançament : 1.fc33
Architecture : noarch
Size : 3.4 M
Origen : ibus-typing-booster-2.10.4-1.fc33.src.rpm
Repository : @System
Del dipòsit : updates
Summary : A completion input method
URL : https://mike-fabian.github.io/ibus-typing-booster/
Llicència : GPLv3+, ASL 2.0
Description : Ibus-typing-booster is a context sensitive completion
: input method to speedup typing.
So it is already installed. Now, checking more in depth, I can confirm it was
installed by the Anaconda installer:
[ubach@Euler ~]$ sudo dnf history list ibus-typing-booster
Id. | Línia d'ordres | Data i hora | Acció
151 | update | 2021-02-12 17:00 | E, I, O,
U | 319 E<
145 | update | 2021-02-07 00:15 | E, I, U
| 389 ><
2 | update | 2020-11-22 20:42 | I, O, U
| 1166 >E
1 | | 2020-10-20 01:35 | Install
| 3224 EE
[ubach@Euler ~]$ sudo dnf history info 1 |grep ibus-typing-booster
Therefore, I don't see the point in removing the ibus-table packages and
install ibus-typing-booster, as this would take me back to the state where the
keyboard worked worse (i.e. without dead keys). Unless you want me to verify
this could be a bug fixed in one of the latest updates (either February the 7th
or February the 12th).
It is possible that in some circumstances, when no input method at
installed and added in the gnome control center, that the dead keys are not
handled by ibus but by gtk.
I can't answer that, because I am using KDE, not Gnome.
If you install and configure at least one ibus input method, then
are handled by ibus.
Can you please try that?
How exactly should I configure an ibus input method in KDE? I thought this is
done in System Configuration. I have already done that, and there I have
configured 3 different keyboard layouts: Catalan, Spanish and United States.
> Nevertheless, the keyboard is not well setup yet. As third level
> misplaced with respect to my keyboard configuration.
> For example, in my keyboard, the "@" symbol is located in AltGr+2.
> I need to type AltGr+Q
I don't know what this could be, what keyboard layout are you using? Surely
this doesn't have anything to do with ibus ...
My physical keyboard is the Catalan variant of the Spanish layout. That is, a
QWERTY kewboard with middle dot l (l·l), Ñ and Ç.
And that is precisely the layout selected in System Configuration (see the
I thought that the output of any key stroke is managed by ibus. If dead keys
are managed by ibus, I imagined the other keys are also managed by it.
You are receiving this mail because:
You are on the CC list for the bug.