Hum, there are some issues there

* ibus/fcitx integrate into the toolkits by using modules, for example
to have a gtk3 software working with ibus you need "ibus-gtk3"
installed, for fctix you need "fcitx-frontend-gtk3" ... do we expect
every snap to have to include those?

* those have an user session daemon, that's the part where I though we
would need an interface/plug (or we need the snaps to ship the daemon
and start a custom dbus bus and make their own service use that) ... or
we need to have the personal core including ibus/fcitx

* the client needs to be able to talk to im service


I didn't get it to work yet but I'm working using the gnome-calculator example 
and building the snap with "ibus-gtk3" listed in the stage-packages. 
To have ibus working you need to
- have ibus installed
- go to unity-control-center -> text input, add a input source using (e.g 
"chinese (pinyin) (ibus)")
- have ibus configured as input method, that should be default (check 
GTK_IM_MODULE and use "im-config -n ibus"/restart session if needed)
- select the pinyin layout in the indicator
- type some text in a gtk entry (e.g the calculator one)

that should display a popover widget with chinese symbols



** Changed in: snapd (Ubuntu)
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580463

Title:
  Snap blocks access to system input methods (ibus, fctix, ...)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to