Description of problem: Clean install of Fedora Scientific (KDE) does not include the ibus-table* packages that are necessary for local distributions of the keyboard. Version-Release number of selected component (if applicable): How reproducible: Haven't tried Steps to Reproduce: 1. Install Fedora Scientific 2. Try to type using dead keys in any KDE program or LibreOffice. 3. Actual results: Vowel letters don't include accents. Expected results: áàäâéèéêíïîóòöôúùüû Additional info: To fix the problem, the user must install ibus-table* packages, which is not described in the documentation, but it should not be necessary to search it in the documentation anyway.
ibus-table-* is mostly for typing Chinese. Looks like you have only a problem with dead keys, not Chinese, is that right? My guess is, you don't need ibus-table at all.
Up until I installed ibus-table-* I could not use dead keys. Now, I can use them. Nevertheless, the keyboard is not well setup yet. As third level keys are misplaced with respect to my keyboard configuration. For example, in my keyboard, the "@" symbol is located in AltGr+2. Instead, I need to type AltGr+Q
(In reply to ubach from comment #2) > Up until I installed ibus-table-* I could not use dead keys. > > Now, I can use them. Did you only install the packages or also add one of the ibus-table input methods in the gnome control center? This is certainly not related to ibus-table. Can you try to remove the ibus-table packages again and install ibus-typing-booster instead? It is possible that in some circumstances, when no input method at all is installed and added in the gnome control center, that the dead keys are not handled by ibus but by gtk. If you install and configure at least one ibus input method, then dead keys are handled by ibus. Can you please try that? > Nevertheless, the keyboard is not well setup yet. As third level keys are > misplaced with respect to my keyboard configuration. > > For example, in my keyboard, the "@" symbol is located in AltGr+2. Instead, > 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 ...
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 input > 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 > ibus-typing-booster instead? 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. Paquets instal·lats 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ó | Alterat ----------------------------------------------------------------------------------------------- 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 Instal·la ibus-typing-booster-2.9.7-1.fc33.noarch @anaconda 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 all is > 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 dead keys > 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 keys are > > misplaced with respect to my keyboard configuration. > > > > For example, in my keyboard, the "@" symbol is located in AltGr+2. Instead, > > 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 screenshot). 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.
Created attachment 1757877 [details] System configuration with keyboard layouts
> 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). No, apparently ibus-typing-booster was already installed. I don't think that your installing ibus-table packages did anything for your deadkeys. You don't use any of the ibus-table input methods, right? You only want to use your Catalan keyboard layout, if I understand you correctly. Are you using KDE with Wayland or with X11?
Can you add a screenshot of your whole desktop please? I would like to see whether you have an ibus-icon in your panel. Are some ibus processes running? Check with ps aux | grep ibus
This is the output of ps aux: [ubach@Euler ~]$ ps aux |grep ibus ubach 2392 0.0 0.0 609120 10348 ? Sl de febr.15 1:42 /usr/bin/ibus-daemon -r --xim ubach 2467 0.0 0.0 448980 5744 ? Sl de febr.15 0:00 /usr/libexec/ibus-dconf ubach 2468 0.0 0.3 982352 54204 ? Sl de febr.15 0:19 /usr/libexec/ibus-ui-gtk3 ubach 2471 0.0 0.2 903372 43692 ? Sl de febr.15 0:17 /usr/libexec/ibus-extension-gtk3 ubach 2479 0.0 0.2 822128 38700 ? Sl de febr.15 0:00 /usr/libexec/ibus-x11 --kill-daemon ubach 2482 0.0 0.0 736252 6580 ? Ssl de febr.15 0:03 /usr/libexec/ibus-portal ubach 2571 0.0 0.0 375188 5708 ? Sl de febr.15 0:20 /usr/libexec/ibus-engine-simple ubach 147286 0.0 0.0 221584 2576 pts/2 S+ 00:50 0:00 grep --color=auto ibus I am running X11, apparently: [ubach@Euler ~]$ loginctl show-session 2 -p Type Type=x11 Before installing the ibus packages reported in #c4 the deadkeys where not working. After installing those packages the deadkeys started to work. > You only want to use your Catalan keyboard layout, if I understand you correctly. Yes, I want to use my Catalan keyboard layout. But I also want to be able to switch layouts in the case I write in some other language with special characters, like for example the German "beta". See the screenshot for the iBus in the panel.
Created attachment 1758480 [details] Full screen screenshot including panel and ibus applet.
Do you see a "dead key preview"? I.e. if you type a dead key, for example a dead tilde ~, is that dead key already shown before you type the next key?
And if you click on the "Input Method" tab in the "IBus Preferences" dialog seen in your screenshot, how does that look like, what input methods have you configured there?
Are you using KDE with Wayland or with Xorg?
(In reply to Mike FABIAN from comment #10) > Do you see a "dead key preview"? I.e. if you type a dead key, for example a > dead tilde ~, is that dead key already shown before you type the next key? When you see such a dead key preview in KDE, it means that the dead keys are handled by ibus. If you don't see such a preview, for example if you see nothing when typing a dead tilde and then type an n and finally see ñ, then this means that the deadkeys are not handled by ibus but by Xorg instead (or GTK if you use a GTK program).
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.
Let's move this to the main KDE component - since this clearly looks like a KDE regression. I assume it was working in F32?
(In reply to Mike FABIAN from comment #10) > Do you see a "dead key preview"? I.e. if you type a dead key, for example a > dead tilde ~, is that dead key already shown before you type the next key? Yes, I do.
Created attachment 1758660 [details] Input Method tab of the iBus Preferences
(In reply to Mike FABIAN from comment #11) > And if you click on the "Input Method" tab in the "IBus Preferences" dialog > seen in your screenshot, how does that look like, what input methods have > you configured there? I have included above the screenshot of the Input Method tab.
(In reply to Mike FABIAN from comment #12) > Are you using KDE with Wayland or with Xorg? [ubach@Euler ~]$ loginctl show-session 2 -p Type Type=x11
(In reply to Mike FABIAN from comment #13) > (In reply to Mike FABIAN from comment #10) > > Do you see a "dead key preview"? I.e. if you type a dead key, for example a > > dead tilde ~, is that dead key already shown before you type the next key? > > When you see such a dead key preview in KDE, it means that the dead keys are > handled by ibus. > > If you don't see such a preview, for example if you see nothing when typing > a dead tilde and then type an n and finally see ñ, then this means that the > deadkeys are not handled by ibus but by Xorg instead (or GTK if you use a > GTK program). In LibreOffice and in Kate (and in Firefox's nav bar), I do see the dead tilde preview.
(In reply to Mike FABIAN from comment #14) > 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. Thanks for the explanation. However, my computer is not running on Wayland. It is running on X11. And I do see the dead tilde previews. Therefore, I am in the situation of KDE under Xorg, and with iBus. In this situation dead keys are working with preview. Before I installed the packages reported, dead keys were not working; neither with nor without preview.
(In reply to Jens Petersen from comment #15) > Let's move this to the main KDE component - since this clearly looks like a > KDE regression. > I assume it was working in F32? I can't give you an answer to that. This is a laptop that is new, although it was sitting for a while before I installed it. This is a DELL Latitude E5450. Fedora 33 is the first and only system I have installed on it.
(In reply to ubach from comment #18) > (In reply to Mike FABIAN from comment #11) > > And if you click on the "Input Method" tab in the "IBus Preferences" dialog > > seen in your screenshot, how does that look like, what input methods have > > you configured there? > > I have included above the screenshot of the Input Method tab. Yes, as I suspected, you are not using any ibus-table input methods at all. Actually you are using only keyboard layouts in ibus. And that helps your problem with the dead keys because the dead key support in ibus works and also gives you that nice dead key preview and the dead key support in KDE apparently doesn't work (at least in F34 Wayland it doesn't work for me, in F34 X11 it works for me). Surely you can uninstall all ibus-table* packages and you dead keys will still work, you only need the main ibus package apparently. The main ibus-package already contains all the keyboard layouts you have setup in your ibus-setup.
(In reply to ubach from comment #19) > (In reply to Mike FABIAN from comment #12) > > Are you using KDE with Wayland or with Xorg? > > [ubach@Euler ~]$ loginctl show-session 2 -p Type > Type=x11 Good, I think this is better at the moment, with Wayland there are more problems with this input stuff.
(In reply to ubach from comment #2) > Up until I installed ibus-table-* I could not use dead keys. > > Now, I can use them. > > Nevertheless, the keyboard is not well setup yet. As third level keys are > misplaced with respect to my keyboard configuration. > > For example, in my keyboard, the "@" symbol is located in AltGr+2. Instead, > I need to type AltGr+Q For me, in Fedora 34, KDE, Wayland, both AltGr+2 and AltGr+Q produce the "@" symbol when using the Catalan keyboard layout.
Now I tested also on Fedora 33. I had no problem using the Catalan keyboard layout, neither in Wayland nor in Xorg. Both in Wayland and Xorg the dead keys worked, without any running ibus processes and nothing configured in ibus. Of course no dead key preview then, typing a dead acute shows nothing and when the following a is typed I get á. Both AltGr+2 and AltGr+Q produce the "@" symbol. This is the image of Fedora 33 I installed in qemu: Fedora-Everything-netinst-x86_64-33-20200921.n.0.iso
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
I believe this was fixed in the F36 release, though there are some remaining ibus issues to be ironed out.