Ok, I looked at this quite a bit today. I'll summarize some stuff that was already said to justify the path forward.
1. bug #1509829 reports that the lightdm guest session fails to start fcitx and mozc input methods 2. the fix as implemented was to create apparmor abstractions for fcitx and mozc for the lightdm guest session policy to use. The bug lies in that lightdm wasn't updated to Depends on the packages providing the abstractions that the guest session policy #included 3. the abstractions in the fcitx and mozc policy is for running these services under the guest session and not for fcitx and mozc clients to access these services 4. apparmor is the correct place to ship abstractions and is interested in fcitx and mozc client policy, but the existing abstractions are inappropriate for inclusion in upstream apparmor The path forward is: 1. lightdm adds to the guest session policy the contents of ./debian/apparmor.d/abstractions/fcitx from the fcitx source package and ./debian/apparmor/mozc_server from the mozc source package and removes '#include <abstractions/fcitx>' and '#include <abstractions/mozc_server>'. This fixes this bug and keeps bug #1509829 closed 2. mozc and fcitx stop shipping abstractions/fcitx and abstractions/mozc_server 3. apparmor adds abstractions/mozc, abstractions/fcitx and abstractions/fcitx-strict policy (needed for other reasons unrelated to this bug) and does a conffile mv on fcitx -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1581187 Title: AppArmor parser error for /etc/apparmor.d/lightdm-guest-session in /etc/apparmor.d/lightdm-guest-session at line 14: Could not open 'abstractions/fcitx' Status in lightdm package in Ubuntu: New Bug description: The current yakkety lightdm version has a regression in its AppArmor profile: $ sudo systemctl status apparmor.service ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2016-05-12 18:03:37 CEST; 3h 17min ago Docs: man:systemd-sysv-generator(8) May 12 18:03:37 autopkgtest apparmor[493]: * Starting AppArmor profiles May 12 18:03:37 autopkgtest apparmor[493]: AppArmor parser error for /etc/apparmor.d/lightdm-guest-session in /etc/apparmor.d/lightdm-guest-session at line 14: Could not open 'abstractions/fcitx' May 12 18:03:37 autopkgtest apparmor[493]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd May 12 18:03:37 autopkgtest apparmor[493]: AppArmor parser error for /etc/apparmor.d/lightdm-guest-session in /etc/apparmor.d/lightdm-guest-session at line 14: Could not open 'abstractions/fcitx' May 12 18:03:37 autopkgtest apparmor[493]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd May 12 18:03:37 autopkgtest apparmor[493]: ...fail! May 12 18:03:37 autopkgtest systemd[1]: apparmor.service: Control process exited, code=exited status=123 May 12 18:03:37 autopkgtest systemd[1]: Failed to start LSB: AppArmor initialization. May 12 18:03:37 autopkgtest systemd[1]: apparmor.service: Unit entered failed state. May 12 18:03:37 autopkgtest systemd[1]: apparmor.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu3 Architecture: amd64 Date: Thu May 12 21:20:13 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
