Bug 1877521 - ibus-panel breaks keyboard layout on plasma-wayland desktop
Summary: ibus-panel breaks keyboard layout on plasma-wayland desktop
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-desktop
Version: 36
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1882465
TreeView+ depends on / blocked
 
Reported: 2020-09-09 18:55 UTC by Martin
Modified: 2023-05-25 16:57 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 16:57:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Ibus-panel vs "plasma keyboard layout" (225.58 KB, image/png)
2021-02-25 15:44 UTC, Martin
no flags Details

Description Martin 2020-09-09 18:55:17 UTC
Description of problem:
In Plasma(wayland) im-chooser/emoji start by default(not start in X11)changing layout CZ to US works for a while and then change back it self.


Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1.log Plasma wayland session
2.emoji is present in syst tray
3.changing keyboard layout
4.try write something in kwrite
5.layout change back 

Actual results:
keyboard layout cant be changed while emoji running

Expected results:
dont start ibus-emoji in wayland session by default, like in X11 session

Additional info:

Comment 1 Martin 2021-02-25 15:44:28 UTC
Created attachment 1759336 [details]
Ibus-panel vs "plasma keyboard layout"

Comment 2 Bernie Innocenti 2021-03-25 08:36:36 UTC
> In Plasma(wayland) im-chooser/emoji start by default(not start in X11)changing layout CZ to US works for a while and then change back it self.
> ...
> Expected results:
> dont start ibus-emoji in wayland session by default, like in X11 session

What do you mean with "im-chooser/emoji" and "ibus-emoji"? I don't have these processes in my Plasma Wayland session on F34.
These are all the processes I see:

  |   |   |   \_ /usr/bin/ibus-daemon -r --xim
  |   |   |       \_ /usr/libexec/ibus-dconf
  |   |   |       \_ /usr/libexec/ibus-ui-gtk3
  |   |   |       \_ /usr/libexec/ibus-extension-gtk3
  |   |   |       \_ /usr/libexec/ibus-engine-mozc --ibus
  |   |   |       \_ /usr/libexec/ibus-engine-simple
  \_ /usr/libexec/ibus-x11 --kill-daemon
  \_ /usr/libexec/ibus-portal

I have /usr/libexec/ibus-ui-emojier, but it isn't running.

Comment 3 Bernie Innocenti 2021-03-25 10:33:51 UTC
Another question: is QT_IM_MODULE set in your session?

Fedora 34 sets QT_IM_MODULE from /etc/X11/xinit/xinput.d/ibus.conf, which (afaict) won't run in the Plasma Wayland session.

Comment 4 Martin 2021-03-25 15:38:46 UTC
by default its installed package im-chooser (/usr/share/applications/im-chooser.desktop)
remove this package make keyboard layout united for all applications.

in X11 plasma session its just one keyboard menu from KDE in systray (with white font "CZ")
in wayland seasson starts the second keyboard menu(with blue font "EN" on picture).

Comment 5 Rex Dieter 2021-04-27 16:43:19 UTC
I'm not well-versed in how all this works, anyone who knows more, can you offer concrete suggestions on how best to address issues raised in this bug?

So far, I see these:
1.  set QT_IM_MODULE env somehow.  I'd argue this should be done in ibus packaging (somehow), the existing xinit snippet is less that ideal (and obviously only works for X sessions).  Alternatives include:
* (plasma-specific) sh snippet under /etc/xdg/plasma-workspace/env/
* sh snippet under /etc/profile.d/  (unfortunately, that will set if for all login shells, not just GUI, not sure if that's bad or not)

2.  remove im-chooser.  pros/cons?

Comment 6 Bernie Innocenti 2021-04-28 03:31:12 UTC
I have this workaround in my profile:

  # temporary for F34 Plasma Wayland
  QT_IM_MODULE=ibus
  IBUS_USE_PORTAL=1
  export QT_IM_MODULE IBUS_USE_PORTAL

The ibus package could set these two vars from /usr/lib/environment.d/10-ibus.conf. This should be executed by the systemd user session for both X11 and Wayland, both GNOME and KDE.


> 2.  remove im-chooser.  pros/cons?

im-chooser could still override the im module by writing to ~/.config/environment.d/*.conf.

I believe ibus is currently the only input method which works well in Wayland for both GNOME and KDE.
So im-chooser should probably be removed from the default install avoid confusion for users (and imsettings-qt should stop depending on it).

Comment 7 Ben Cotton 2022-05-12 15:36:00 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 8 Bernie Innocenti 2022-05-12 17:18:52 UTC
Still present in Fedora 36. We could still do this:

> im-chooser should probably be removed from the default install to avoid
> confusion for users (and imsettings-qt should stop depending on it).

Comment 9 Ben Cotton 2023-04-25 16:40:39 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 10 Ludek Smid 2023-05-25 16:57:53 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.