On 05/11/2016 10:22 AM, Jamie Strandboge wrote: ... > > We then have dbus-session-strict: > unix (connect, receive, send) > type=stream > peer=(addr="@/tmp/dbus-*"), > > There is a problem with this policy though; that access is not very > strict at all and we should adjust the unity7 interface accordingly (and > test that ibus still works).
I'm not sure how we could do that without code changes. There's nothing differentiating the session bus' abstract socket name from the ibus bus' abstract socket name. > Is ibus-daemon actually a dbus service or is it something else? It looks to me like it is its own bus daemon. In other words, the equivalent of something like `dbus-daemon --session` instead of simply being a dbus service. -- 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
