Funny, but that gives me completely different broken behaviour. im-config writes to ~/.xinputrc:
# im-config(8) generated on Thu, 07 Aug 2014 08:26:49 +0200 run_im xim # im-config signiture: 89512b7941127eeda7d3e3ac5703f05e - And then I indeed get the same environment variables as you. (en_US) In other applications the input works like expected, regular compose and my extra combinations. In chromium, the following happens: - in the address bar, regular compose works, but my extra combinations *don't* - as soon as I press enter in the address bar, the compose key stops working altogether: both keys of the combination get discarded - however, after the third attempt at reproducing, the regular compose stopped working: chromium now consistently silently eats all compose characters, even at startup. That last behavioural change sounded like a local config issue, but removing ~/.config/chromium did not resolve anything. Also, switching the compose key from right-alt to right-ctrl does what you'd expect: - in all applications the compose key is changed - in chromium, the composed keys -- now with right-ctrl -- are eaten -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309145 Title: Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1309145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
