Re: im-config | Use im-config on Wayland without uninstalling IBus (!5)
Hi!
On 2020-07-10 05:23, Osamu Aoki wrote:
Hi Gunnar and Changwoo
On Mon, 2020-07-06 at 22:24 +0200, Gunnar Hjalmarsson wrote:
On 2020-05-26 02:53, Changwoo Ryu wrote:
You are talking about ignoring a large group of users including the
whole Korean language users.
No I'm not talking about ignoring anyone. But I'm acting.
I brought up the ibus-hangul/mutter issue with Ubuntu's desktop
team.
More precisely this issue:
https://gitlab.gnome.org/GNOME/mutter/-/issues/948
That made Daniel van Vugt add a couple of comments, which brought a
related MR to life:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1286
As far as I can tell the issue is now about to be fixed. I have
successfully tested the changes in that MR.
Gunnar,
Please help me understand situation assuming this MR is accepted.
== Testing/Sid system ==
* Are you sure just waiting this fix to migrate is enough to fix this
Korean input problem?
Well, I don't speak Korean and don't know how to really use ibus-hangul.
But, as mentioned at the MR, I tested the proposed changes successfully,
which means that I can no longer reproduce the problem as described in
the upstream mutter issue 948.
This is the mutter build I used for testing:
https://launchpad.net/~gunnarhj/+archive/ubuntu/mutter/+packages
Possibly you can install from that PPA in Debian and test yourself (no
guarantee, but the Debian/Ubuntu delta seems to be small and unrelated).
(If so, I will wait without touching im-config on testing/sid)
What's in im-config's devel branch right now would be nice to see
uploaded to unstable as a first step IMO. It does not make the
ibus-hangul/mutter bug worse, and it would make im-config more easy to
use on Wayland for non-IBus frameworks.
Then, together with the pending mutter fix, we would improve the
situation significantly.
== Stable system ==
* Does this fix have chance to be included in the next stable update?
(I doubt this and we should not count on this)
* Does this fix have chance to be included in the backport?
(I think this may happen but this is no excuse for not fixing this
bad situation)
Assuming those questions were not meant for me. I'm not familiar enough
with the procedures for stable updates in Debian. With that said, it
would be highly desirable to get the fix in, of course.
* What exactly is the concern to add workaround approach proposed by
Changwoo to the im-config. Breaking virtual keyboard is non-issue
since this is useless for Korean input at this moment. Since "auto"
is the place where most desirable choice is recommended, I see no
reason to reject Changwoo's proposal.
The most important reason IMO is the way that change would affect the UI
for explicitly setting the desired IM framework. The change would affect
all IM users, not only Korean ones. In addition to that, users may speak
more than one language, so dismissing the broken OSK as a non-issue for
ibus-hangul users is not correct.
If you know that
* GNOME launches and configures IBus by itself when im-config is
disabled ("none"),
* enabling im-config by setting "ibus" explicitly changes the
configuration so IBus works differently behind the scenes compared with
how GNOME is designed to make use of IBus, and
* choosing "ibus" may work around e.g. that ibus-hangul/mutter bug while
breaking other stuff on the desktop
then Changwoo's propsal makes some sense. But if you know all that, you
are an expert user, and I think it would be wrong to design im-config
for expert users.
A regular IM user wants to use an IM engine, and has good reasons to
assume that if it's an ibus IM, im-config should be set to "ibus". They
have no reason to assume that that setting may break other stuff on
their GNOME desktop which is designed to work well with IBus.
So in short I think it would be a convoluted workaround which also would
be prone to misunderstanding.
When Changwoo and I were talking on the already committed MR, and as an
alternative, I suggested a temporary measure to work around the
ibus-hangul/mutter bug. My idea was to simply have im-config set
GTK_IM_MODULE=ibus behind the scenes for ibus-hangul users without
changing the UI logic.
OTOH, considering that the ibus-hangul/mutter bug is about to be fixed,
it's a bit late IMO to introduce any kind of workaround in im-config.
(I am not sure how broken Debian stable impacts Ubuntu since it seems
to pull many packages from testing even under LTS releases. I will
leave it to you. But I need to ensure usable Debain stable release.)
Since Ubuntu is still on X, and Wayland is not even offered as a login
option by default, very few Ubuntu users are affected at this time. So
on Ubuntu, updating 20.04 with the mutter fix would be a nice thing to
have, but it's of limited importance.
--
Cheers,
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj
Reply to: