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

Hi, Maybe I used too strong word to describe XIM + ibus combination situation. But I still feel unsafe to do so. Please note I am not saying use of xterm under pure X environment (without ibus) with xmodmap to be unsafe nor buggy. That's fine good old system. > -Original Message- >

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

On 2022-05-25 15:54:13 +0900, Osamu Aoki wrote: > > I recall that I do not use any desktop environment.  > > What do you mean? Just hand written shell to start X? Or you start X > server from Linux virtual console manually? I normally use the lightdm display manager to start X (or in case of

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

Oops Let me correct. I mean non-deterministic. > Since I don't know exactly what is happening on your system and I know the > upstream > has been aware of timing involved race condition bug, I am not surprised you > are > getting somewhat **non**-deterministic results. (If you are

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

Hi, Your message made me to look into subtle points on Xsession etc. Thanks. In order for me to track what I did/do with im-config, I added new section. https://wiki.debian.org/Keyboard#Overview_of_keyboard_input The environment in which im-config runs is complicated. Let me ask a few

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

On 2022-05-24 22:54:01 +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

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

Hi, > -Original Message- > From: Vincent Lefevre > To: Osamu Aoki > Cc: Gunnar Hjalmarsson , 988...@bugs.debian.org, brian m. > carlson > Subject: Re: Bug#988540: im-config: breaks the keyboard configuration > Date: Tue, 24 May 2022 12:54:54 +0200 > > O

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

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

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

Hi, > -Original Message- > From: Osamu Aoki ... > Users may no longer be able to use xterm **reliably for some non-ASCII > inputs** > when > ibus is **activated**. > I thought about this issue over combination of pure-X GUI and ibus for non-terminal programs. gitk (TK based) and

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

Hi, > But this is very unclear (and perhaps wrong for other users). I thought that some flexible table based fully custom input may be available using either ibus-table or ibus-m18n with some user data. (This is my vague idea without proof.) Then looking at Debian repository, I found

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

Hi, After reading your message, I have revised text around https://wiki.debian.org/Keyboard#Input_method_and_XIM > -Original Message- > From: Vincent Lefevre > To: Osamu Aoki > Cc: Gunnar Hjalmarsson , 988...@bugs.debian.org, brian m. > carlson > Subject: Re: Bug

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

On 2022-05-23 06:23:58 +0900, Osamu Aoki wrote: > Anyway, XIM is dead end for some foreseeable future. My conclusion is "don't > use > XIM" as backend of ibus. https://wiki.debian.org/Keyboard#Input_method_and_XIM So, if I understand correctly, users may no longer be able to use xterm when ibus

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

Hi, > -Original Message- > From: Vincent Lefevre ... > On 2022-05-22 21:59:35 +0900, Osamu Aoki wrote: > > I also have updated around XIM bugs with more subdued tone. As long > > as you type ASCII characters only, you may not hit bugs (I hope.) > > I use XKB specifically to enter

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

On 2022-05-22 21:59:35 +0900, Osamu Aoki wrote: > I also have updated around XIM bugs with more subdued tone. As long > as you type ASCII characters only, you may not hit bugs (I hope.) I use XKB specifically to enter non-ASCII characters: accented characters (either with a direct mapping to the

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

Hi, I also have updated around XIM bugs with more subdued tone. As long as you type ASCII characters only, you may not hit bugs (I hope.) > -Original Message- > From: Vincent Lefevre > I can read that xterm uses XIM mechanism and XIM mechanism is buggy. :( > I use mostly xterm

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

On 2022-05-22 16:06:28 +0900, Osamu Aoki wrote: > I have updated https://wiki.debian.org/Keyboard. > > (debian-reference was updated in 2020-2021, I think.) > > These should give clearer view on XKB/input method situation. > > If you find errors, please feel free to correct them. I can read

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

Hi, I have updated https://wiki.debian.org/Keyboard. (debian-reference was updated in 2020-2021, I think.) These should give clearer view on XKB/input method situation. If you find errors, please feel free to correct them. Regards, Osamu

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

Hi, On 2022-05-21 11:16:53 +0900, Osamu Aoki wrote: > > If multiple Debian users reach out to them, they *might* act after all. > > Done with strong words. One year ago, I tweeted to Zoom about that, IIRC because I had not found a way to report a bug:

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

Hi, > If multiple Debian users reach out to them, they *might* act after all. Done with strong words. Aside from unjustified listing of "ibus" in "Depends:" in ZOOM, Vincent has a point. Need to support user moving from bare XKB setting to ibus's setting. This side of needs need to be

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

The right fix is to make Zoom drop the dependency on ibus. Any feedback here on my attempt to do that? https://devforum.zoom.us/t/annoying-ibus-dependency-in-zoom-deb-files/67293 Was I not clear enough, or not patient enough? If multiple Debian users reach out to them, they *might* act after

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

Hi, > -Original Message- > From: Vincent Lefevre ... > > This happened because ZOOM (this package is external to Debian) > > provides its DEB package with its "Depends" listing ibus. > > > > It is reasonable for ZOOM to support Chinese and Japanese input and > > list ibus as dependency.

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

On 2022-05-21 00:05:09 +0900, Osamu Aoki wrote: > Classic X environment supports to enter non-ASCII (latin) characters > via XKB input and some people still want to use this via this old > setting method. > > Bug was filed by an annoyed user who lost access to functionalities > offered by his old

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

Control: summary -1 0 im-config can be disabled to avoid breaking the keyboard input using XKB input (ZOOM user) thanks

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

Control: tags -1 wontfix Control: severity -1 wishlist Control: retitle -1 im-config: breaks the keyboard input using XKB input (ZOOM user) Control: summary -1 0 thanks Classic X environment supports to enter non-ASCII (latin) characters via XKB input and some people still want to use this via

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

On 2022-04-08 22:57, Gunnar Hjalmarsson wrote: The ibus dependency in the zoom .deb file is getting annoying. Besides this bug there is , and the other day I noticed this case: https://github.com/mike-fabian/ibus-typing-booster/issues/107#issuecomment-1089262983

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

The ibus dependency in the zoom .deb file is getting annoying. Besides this bug there is , and the other day I noticed this case: https://github.com/mike-fabian/ibus-typing-booster/issues/107#issuecomment-1089262983 So I made an own attempt to get in touch

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

On 2021-05-22 13:46:50 +0900, Osamu Aoki wrote: > At least, zoom should have used RECOMMENDS and user should have avoided > to install ibus. I would even say "Suggests:", so that ibus isn't installed by default. It seems that one cannot report a bug to Zoom without a Zoom account. So I've just

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

Gunnar, Thank you for very accurate assessment of the situation. On Tue, 2021-05-18 at 00:22 +0200, Gunnar Hjalmarsson wrote: > On 2021-05-17 22:19, Vincent Lefevre wrote: > > On 2021-05-17 21:11:16 +0200, Gunnar Hjalmarsson wrote: > > > I think it's too much to ask from a simple Xsession plugin

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

On 2021-05-17 22:19, Vincent Lefevre wrote: On 2021-05-17 21:11:16 +0200, Gunnar Hjalmarsson wrote: I think it's too much to ask from a simple Xsession plugin such as im-config that it should be responsible for preventing any kind of possible conflicts. Then it should not be started by

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

On 2021-05-17 21:11:16 +0200, Gunnar Hjalmarsson wrote: > On 2021-05-17 10:10, Vincent Lefevre wrote: > > I don't think that this is a special combo, at least when not used > > a desktop environment like GNOME. You can see other users doing the > > same thing: > > > > > >

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

On 2021-05-17 10:10, Vincent Lefevre wrote: I don't think that this is a special combo, at least when not used a desktop environment like GNOME. You can see other users doing the same thing:

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

On 2021-05-17 01:25:32 +0200, Gunnar Hjalmarsson wrote: > As regards the main topic I don't think it's really an im-config specific > issue. im-config is run as an Xsession script, and possibly your setup with > fvwm and an xkbcomp call in ~/.xsession is a rather special combo where > things

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

I pushed this commit: https://salsa.debian.org/input-method-team/im-config/-/commit/47941de4 So, Vincent, this bug report has resulted in a tiny improvement at least. ;) As regards the main topic I don't think it's really an im-config specific issue. im-config is run as an Xsession script,

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

On 2021-05-15 18:55, Vincent Lefevre wrote: It doesn't output everything that is set. For instance, I use LC_TIME=en_DK.utf8, and reportbug doesn't output it. However, this setting is still available. That is just a consequence of the fact that LC_ALL is set.

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

On 2021-05-15 17:54:39 +0200, Gunnar Hjalmarsson wrote: > But due to that, the "locale output" section in /usr/share/bug/im-config > isn't so useful. Previously I mentioned the idea to add "unset LC_ALL" in > the script. Or should we better drop the "locale output" section? > > Quoting from

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

On 2021-05-15 17:20, Vincent Lefevre wrote: On 2021-05-15 16:07:46 +0200, Gunnar Hjalmarsson wrote: What's the contents of your /etc/default/locale file? # File generated by update-locale #LANG="en_US.UTF-8" LANGUAGE="en_US:en" Can you please replace #LANG="en_US.UTF-8" with

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

Hi Changwoo, On 2021-05-15 16:35, Changwoo Ryu wrote: 2021년 5월 15일 (토) 오후 8:21, Gunnar Hjalmarsson 님이 작성: I see one thing which looks suspicious: You have set the LC_ALL environment variable to C. LC_ALL is not supposed to be set permanently. Ever. Especially not to C, which disables UTF-8

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

On 2021-05-15 16:07:46 +0200, Gunnar Hjalmarsson wrote: > > > What's the contents of your /etc/default/locale file? > > > > # File generated by update-locale > > #LANG="en_US.UTF-8" > > LANGUAGE="en_US:en" > > Can you please replace > > #LANG="en_US.UTF-8" > > with > > LANG="C.UTF-8" > >

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

Hello, 2021년 5월 15일 (토) 오후 8:21, Gunnar Hjalmarsson 님이 작성: > > I see one thing which looks suspicious: You have set the LC_ALL > environment variable to C. LC_ALL is not supposed to be set permanently. > Ever. Especially not to C, which disables UTF-8 encoding. Actually LC_ALL=C is set by

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

On 2021-05-15 14:27, Vincent Lefevre wrote: im-config can be disabled if you don't need it. To do that you can use the "Input Method Configuration" GUI and select "none". The command line equivalent is: im-config -n none Thanks, that works. But the default should not modify the user's

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

Hi Gunnar, On 2021-05-15 13:11:04 +0200, Gunnar Hjalmarsson wrote: > I see one thing which looks suspicious: You have set the LC_ALL environment > variable to C. LC_ALL is not supposed to be set permanently. Ever. > Especially not to C, which disables UTF-8 encoding. Well, I don't have that in

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

Severity: normal Tags: moreinfo Hi Vincent, I see one thing which looks suspicious: You have set the LC_ALL environment variable to C. LC_ALL is not supposed to be set permanently. Ever. Especially not to C, which disables UTF-8 encoding. What's the contents of your /etc/default/locale

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

Something else... On 2021-05-15 11:49:50 +0200, Vincent Lefevre wrote: > === /etc/default/im-config == [...] > # List of desktop systems which starts ibus if available > # Applicable desktops are excluded for applying IM_CONFIG_PREFERRED_RULE > DESKTOP_SETUP_IBUS="GNOME" [...] Note that I

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

On 2021-05-15 11:49:50 +0200, Vincent Lefevre wrote: > The installation of im-config breaks the keyboard configuration: > accented characters no longer work, etc. I forgot to say: this happens only after logging out and logging in again. My configuration by xkbcomp is just ignored. Running

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

Package: im-config Version: 0.46-1 Severity: grave Justification: renders package unusable The installation of im-config breaks the keyboard configuration: accented characters no longer work, etc. Note: This package is automatically installed via dependencies (ibus, needed by Zoom). --