Bug#1054622: im-config: can set GTK_IM_MODULE to xim, which causes GTK 4 to complain
Hi,
Let's not repeat our discussion on im-config by discussing how ZOOM (external to
Debian with poor record to provide proper dependencies in its deb package
despite our advise to correct it) interacts with Debian default settings.
Having said it, I still think it is worth discussing how im-config should set
environment variables in near future especially with how wayland is getting its
popularity.
Please read notable links on this topics first:
* Input Method Hub --
- https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/39
* Wayland and input methods -- wayland-protocol description
- https://dorotac.eu/posts/input_method/
* Using Fcitx 5 on Wayland -- view by fcitx community
- https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland
* about Input Method wayland protocols #2331 -- view by ibus maintainer
- https://github.com/ibus/ibus/issues/2331
* New ideas using Wayland Input Methods -- view by QT people? August 3, 2023
-
https://blog.davidedmundson.co.uk/blog/new-ideas-using-wayland-input-methods/
I don't understand all the details but this topic for input method in wayland
seems to be very much in development phase as of October/2023. I think it is
worth tracking this technical development.
Most interesting part was: "Do we still need XMODIFIERS, GTK_IM_MODULE and
QT_IM_MODULE?" --> For XMODIFIERS, yes, we do. X11 application running under X11
and XWayland has nearly no difference.
Let me comment on this bug report.
On Fri, 2023-10-27 at 00:17 +0000, brian m. carlson wrote:
> On 2023-10-26 at 22:51:19, Gunnar Hjalmarsson wrote:
> > On 2023-10-26 23:51, brian m. carlson wrote:
> > > I have a system with Zoom installed, which necessitates installing
> > > ibus, which I don't want to use (because it overrides my shortcut
> > > keys without consent). Thus, the advice I've received is to install
> > > im-config and use to set the module to "xim".
Have you read the previous bug report thoroughly before posting this.
Specifically:
* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988540
> > That's bad advice. Where did you get it?
Setting to "xim" was only mentioned by the bug reporter and we corrected it as
bad idea and promoted to use "none".
> > Don't set it to "xim", set it to "none" instead, which means that im-config
> > does not touch any environment variables (and does not launch ibus-daemon).
>
> I believe I got it when I filed a bug report on ibus about some bug
> where it affected my input in some way. I don't recall, since it's been
> some time.
> > > I don't think, given that GTK+ 4 is used for a wide variety of
> > > software in Debian, that it's safe to set GTK_IM_MODULE to "xim"
> > > anymore, and im-config needs to not do that.
Please present links to support your technical references.
By the way, the GTK+ was used for only up to version 3. I think its name is now
GTK4 library.
> > Your observation is not a sufficient reason to conclude that "xim" is never
> > useful and should be removed as an option. im-config does not set that
> > option automatically, but only if the user chooses it explicitly. In your
> > case due to a bad advice. ;)
> >
> > So I'm inclined to close this bug as a "wontfix", but await possible further
> > input on the matter.
I agree.
> I'd argue that setting any environment variables that make programs
> scream to the terminal is not okay. I'm fine with im-config setting any
> value that doesn't do that.
Since wiki page https://wiki.debian.org/Keyboard is referenced in README.Debian
of im-config, I updated this wiki page to make it easier to find this proper
work around.
https://wiki.debian.org/Keyboard#IM_framework_disabled_case_.28XKB.29
Regards,
Osamu
Reply to: