Comment 9 for bug 1761585

I successfully tested ibus 1.5.11-1ubuntu2.1 from xenial-proposed, following the test case in the bug description:

I installed the chromium snap from the stable channel (version 65.0.3325.181, revision 274) and monitor the system journal for apparmor denials while launching it:

    journalctl -f | grep chmod

I observed a denial similar to that one:

    audit[16919]: AVC apparmor="DENIED" operation="chmod" profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/" pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000

I then rebuilt and installed the snap with libibus-1.0-5 and ibus-gtk3 from xenial-proposed (version 1.5.11-1ubuntu2.1):

    cd /tmp
    cp /var/lib/snapd/snaps/chromium_274.snap ./
    unsquashfs chromium_274.snap
    wget https://launchpadlibrarian.net/364009842/libibus-1.0-5_1.5.11-1ubuntu2.1_amd64.deb
    wget https://launchpadlibrarian.net/364009838/ibus-gtk3_1.5.11-1ubuntu2.1_amd64.deb
    dpkg -x ibus-gtk3_1.5.11-1ubuntu2.1_amd64.deb squashfs-root/
    dpkg -x libibus-1.0-5_1.5.11-1ubuntu2.1_amd64.deb squashfs-root/
    snapcraft pack squashfs-root
    snap remove chromium
    snap install --dangerous chromium_65.0.3325.181_amd64.snap
    snap connect chromium:browser-sandbox

I launched it again while monitoring the system journal, and observed that the chmod denial was gone.

I also verified that ibus input still works in the snap (tested with ibus-cangjie for traditional Chinese).