[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#988540: im-config: breaks the keyboard configuration



Hi,

> -----Original Message-----
> From: Vincent Lefevre <vincent@vinc17.net>
> To: Osamu Aoki <osamu@debian.org>
> Cc: Gunnar Hjalmarsson <gunnarhj@debian.org>, 988540@bugs.debian.org, brian m.
> carlson <sandals@crustytoothpaste.net>
> Subject: Re: Bug#988540: im-config: breaks the keyboard configuration
> Date: Tue, 24 May 2022 12:54:54 +0200
> 
> On 2022-05-23 11:49:21 +0900, Osamu Aoki wrote:
> > Users may no longer be able to use xterm **reliably for some
> > non-ASCII inputs** when ibus is **activated**.
> 
> I'm wondering what you mean by that. I recall that:
> 
> 1. If im-config is run after my XKB settings, then my keyboard
>    configuration is broken (probably overridden by im-config's
>    own settings). This means that ibus is activated, right?

Yes.  (To be precise, your XKB settings are *ignored*.  Since keyboard inputs goes
through ibus to reach xterm. ibus is not run under your XKB settings nor under its
influence.  I guess this is the situation but I haven't investigated exact
situation.)

ibus activation may be by the default setting of im-config or by the Desktop
environment such as recent GNOME.

> 2. If after that, I apply my XKB settings again, then things work
>    as usual (even for xterm), possibly except for applications
>    that are currently running (in particular xterm, but this is
>    not related to ibus, as this is an issue I reported in 2012:
>    bug 661295).

To be honest, I don't want to create nor deal such a complicated situation.

If you want to use classic XKB setting, just don't activate ibus.  (or don't install
ibus.)

>  So, if ibus is activated (see (1)), this would
>    mean that it shouldn't affect xterm, even for most non-ASCII
>    inputs (I recall that I use accented letters, possibly via
>    dead keys, and math symbols: xterm is receiving the Unicode
>    character correctly, so I wonder why it would depend on the
>    code point).

I don't know what do you mean by code point.

> Or did you mean that if I want to remap the keyboard with ibus
> instead of XKB, then it would not work with xterm[*]?

You make it sounds total breakage.  problem was rare.

Some particular keyboard inputs may cause problem but mostly functional for keyboard
-> ibus -> XIM -> xterm path.  If you re-read my updated page, I describe this subtle
situation carefully.  Please read https://wiki.debian.org/Keyboard . Especially, I
address your concern at
https://wiki.debian.org/Keyboard#Multi-language_keyboard_configuration_strategy

XIM bug for ibus seems to impact particular combination of input sequences anyway.

> [*] in case of testing, bug 661295 needs to be taken into account,
> i.e. one should test by starting xterm after any config change.

No no no... let's not create unmanageable system.

Osamu


Reply to: