After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 697073 - Input sources are 'xkb' xor 'ibus', unable to be both
Input sources are 'xkb' xor 'ibus', unable to be both
Product: gnome-settings-daemon
Classification: Core
Component: keyboard
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
Depends on:
Reported: 2013-04-01 21:14 UTC by fakey
Modified: 2019-03-20 11:09 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description fakey 2013-04-01 21:14:12 UTC
Xkb manages keyboard layouts and IBus manages IMs, but the two concepts are kind of orthogonal to one another.

e.g. one might want to choose Pinyin IM on US QWERTY keyboard layout, or Anthy IM on French AZERTY keyboard layout.

Instead of having (type, id) :: (s, s) as an input source, maybe we could have (layout, IM) :: (s, ms) instead? This would also require some changes to the g-c-c region panel in order to allow the user to choose what combinations he wanted.
Comment 1 Rui Matos 2013-04-01 21:35:22 UTC
Yeah, we need to address this somehow. Let's get designers involved.
Comment 2 Jens Petersen 2013-04-15 07:58:06 UTC
The main thing I see lacking for this currently is sufficient metadata
about keyboard layouts and input methods though it should not be so hard
to determine/provide. There needs to be a simple way to determine
if a layout supports ASCII input, and if a input method requires/assumes
a particular layout.  A more basic X problem is that it does not really
treat xkbmaps as "objects" (I mean they are basically write-only) -
this part could hopefully be solved by Wayland?

I don't think there is a immediate simple solution for this,
but it is important and yes needs some design work to get right.
Comment 3 GNOME Infrastructure Team 2019-03-20 11:09:02 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: