I don't see documentation about this either, subscribing Tyler and Jamie. I also don't think it's adequate to make lightdm depend on fcitx, as that's both just one input method amongst several (and most people don't need it), so I think the cleanest way might be to actually move the fcitx rules into lightdm. I figure fcitx itself won't need apparmor rules as it runs as user, and these were added only for the benefit of the lightdm greeter?
-- 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