On Thu, Oct 24, 2019 at 12:06:38AM -0000, Gunnar Hjalmarsson wrote: > On 2019-10-24 00:56, Steve Langasek wrote: > > Contents of the file are:
> > include "/usr/share/X11/locale/en_US.UTF-8/Compose" > > <\> <)> : "☭" # HAMMER AND SICKLE > Hmm.. Looking at <https://help.ubuntu.com/community/ComposeKey> and > wondering if that line shouldn't rather read something like this: > <Multi_key> <backslash> <parenright> : "☭" # HAMMER AND SICKLE > (which works with IBus provided that there is a defined compose key) Sure, this is a valid alternative, and just replacing the <\> with <backslash> is enough to unbreak my Delete key. (I don't care about whether it causes the compose sequence to work, I clearly forgot I had ever even configured this!) > Even if there was a regression due to the 1.5.19 -> 1.5.21 upgrade of > ibus > * the changed behavior is upstream in nature > * a possible upstream issue would basically say: "Why does IBus no > longer interpret my syntactically incorrect ~/.XCompose file in > accordance with my intention?" IBus does not define the syntax of .XCompose, and this file is an interface. It is not for ibus to retroactively declare the file to be "syntactically incorrect"; and regardless, if it has decided that the file is syntactically incorrect, this should not result in changes to the behavior of an unrelated key. > So I tend to think that this bug should be closed as invalid, unless you > have some convincing arguments for keeping it open. Your call. :) It is absolutely not invalid. I accept that it's not a high priority, but it remains the case that ibus is interpreting ~/.XCompose in a way that is inconsistent with how X itself does so. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1849399 Title: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key Status in ibus package in Ubuntu: Triaged Bug description: After upgrade to 19.10, I found that my Delete key was not working as a Delete key, but that instead if I hit Delete twice it would print the character ☭. Since others were not reporting this issue, I had a look around at my input config and remembered that I had ibus configured from a long time ago in order to support Chinese input. If I disable ibus (either by unsetting the environment variables; or by killing ibus-daemon), then the Delete key works again as expected. This is a regression in behavior since Ubuntu 19.04, where I had the same input setup on my desktop but the Delete key worked without problems. I'm also not sure how to disable ibus, now that I am in this situation; or if ibus is expected to always be running. The problem persists if I run ibus-setup and remove Chinese SunPinyin from the list of input methods, leaving only "English - English (US)". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1849399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
