Is '/etc/xdg/lxsession/Lubuntu/* cx, # LP1273524' actually part of the
file? If so, remove that. This is what it should look like on 16.04:
$ cat /etc/apparmor.d/lightdm-guest-session
# vim:syntax=apparmor
# Profile for restricting lightdm guest session
#include <tunables/global>
/usr/lib/lightdm/lightdm-guest-session {
# Most applications are confined via the main abstraction
#include <abstractions/lightdm>
# chromium-browser needs special confinement due to its sandboxing
#include <abstractions/lightdm_chromium-browser>
}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1578938
Title:
systemd[1]: apparmor.service: Control process exited, code=exited
status=123
Status in apparmor package in Ubuntu:
Incomplete
Bug description:
Get that logged:
apparmor[451]: * Starting AppArmor profiles
apparmor[451]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
apparmor[451]: 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'
apparmor[451]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
apparmor[451]: 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'
apparmor[451]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
apparmor[451]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
apparmor[451]: ...fail!
systemd[1]: apparmor.service: Control process exited, code=exited status=123
systemd[1]: Failed to start LSB: AppArmor initialization.
systemd[1]: apparmor.service: Unit entered failed state.
systemd[1]: apparmor.service: Failed with result 'exit-code'.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apparmor 2.10.95-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri May 6 09:03:55 2016
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
SourcePackage: apparmor
Syslog: May 6 06:55:04 u64 dbus[856]: [system] AppArmor D-Bus mediation is
enabled
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1578938/+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
