I haven't had time to verify the status yet, but there is a bit difference on keyboard handling in current fcitx package.
When using ibus, we were using X to handle keyboard layouts directly, and use ibus for holding those engines only. With current fcitx configuration, keyboard layouts (xkb) configurations are processed by fcitx before X. This is still enabled in Vivid because I want to give it more room for fixing the race incompatibilities, but we can disable it if we are really making it default for everyone but the keyboard stuff isn't worked out properly. That would mean doing the same like ibus - using X to process keyboard layouts directly. Rationale on why we need IM framework processing the keyboard stuff is that this gives portability among different display server technologies, and more importantly, users will get the same experience when moving among them using the same configuration, without being bothered by races of different display servers (X, Wayland, Mir and maybe more). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439231 Title: fcitx breaks X11 compose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1439231/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
