Public bug reported:
With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
ureadahead.service. Sometimes udisks2.service fails too.
$ uname -a
Linux lieselotte 4.14.4-041404-generic #201712050630 SMP Tue Dec 5 12:07:25 UTC
2017 i686 i686 i686 GNU/Linux
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● apparmor.service loaded failed failed LSB: AppArmor initialization
● udisks2.service loaded failed failed Disk Manager
● ureadahead.service loaded failed failed Read required files in advance
$ 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 Do 2017-12-07 18:04:51 CET; 52min
ago
Docs: man:systemd-sysv-generator(8)
Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited,
status=1/FAILURE)
Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor initialization...
Dez 07 18:04:51 lieselotte apparmor[689]: * Starting AppArmor profiles
Dez 07 18:04:51 lieselotte apparmor[689]: * AppArmor not available as kernel
LSM.
Dez 07 18:04:51 lieselotte apparmor[689]: ...fail!
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process
exited, code=exited status=1
Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor
initialization.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed
state.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result
'exit-code'.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: apparmor kernel-bug xenial
** Description changed:
- With Ubuntu 16.04.3 LTS (Xenial Xerus), and mainline kernel 4.14.3 or
- 4.14.4 systemd fails allways starting apparmor.service and
+ With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
+ 4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
ureadahead.service. Sometimes udisks2.service failes too.
$ systemctl --failed
- UNIT LOAD ACTIVE SUB DESCRIPTION
+ UNIT LOAD ACTIVE SUB DESCRIPTION
● apparmor.service loaded failed failed LSB: AppArmor initialization
● udisks2.service loaded failed failed Disk Manager
● ureadahead.service loaded failed failed Read required files in advance
- $ systemctl status apparmor.service
+ $ 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 Do 2017-12-07 18:04:51 CET; 52min
ago
- Docs: man:systemd-sysv-generator(8)
- Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited,
status=1/FAILURE)
+ Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
+ Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min
ago
+ Docs: man:systemd-sysv-generator(8)
+ Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited,
status=1/FAILURE)
Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor
initialization...
Dez 07 18:04:51 lieselotte apparmor[689]: * Starting AppArmor profiles
Dez 07 18:04:51 lieselotte apparmor[689]: * AppArmor not available as kernel
LSM.
Dez 07 18:04:51 lieselotte apparmor[689]: ...fail!
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process
exited, code=exited status=1
Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor
initialization.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed
state.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result
'exit-code'.
** Description changed:
With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
- ureadahead.service. Sometimes udisks2.service failes too.
+ ureadahead.service. Sometimes udisks2.service fails too.
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● apparmor.service loaded failed failed LSB: AppArmor initialization
● udisks2.service loaded failed failed Disk Manager
● ureadahead.service loaded failed failed Read required files in advance
$ 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 Do 2017-12-07 18:04:51 CET; 52min
ago
Docs: man:systemd-sysv-generator(8)
Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited,
status=1/FAILURE)
Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor
initialization...
Dez 07 18:04:51 lieselotte apparmor[689]: * Starting AppArmor profiles
Dez 07 18:04:51 lieselotte apparmor[689]: * AppArmor not available as kernel
LSM.
Dez 07 18:04:51 lieselotte apparmor[689]: ...fail!
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process
exited, code=exited status=1
Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor
initialization.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed
state.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result
'exit-code'.
** Package changed: apparmor (Ubuntu) => linux (Ubuntu)
** Description changed:
With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
ureadahead.service. Sometimes udisks2.service fails too.
+
+ $ uname -a
+ Linux lieselotte 4.14.4-041404-generic #201712050630 SMP Tue Dec 5 12:07:25
UTC 2017 i686 i686 i686 GNU/Linux
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● apparmor.service loaded failed failed LSB: AppArmor initialization
● udisks2.service loaded failed failed Disk Manager
● ureadahead.service loaded failed failed Read required files in advance
$ 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 Do 2017-12-07 18:04:51 CET; 52min
ago
Docs: man:systemd-sysv-generator(8)
Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited,
status=1/FAILURE)
Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor
initialization...
Dez 07 18:04:51 lieselotte apparmor[689]: * Starting AppArmor profiles
Dez 07 18:04:51 lieselotte apparmor[689]: * AppArmor not available as kernel
LSM.
Dez 07 18:04:51 lieselotte apparmor[689]: ...fail!
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process
exited, code=exited status=1
Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor
initialization.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed
state.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result
'exit-code'.
--
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/1737005
Title:
Mainline kernel 4.14 does not start apparmor
Status in linux package in Ubuntu:
New
Bug description:
With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
ureadahead.service. Sometimes udisks2.service fails too.
$ uname -a
Linux lieselotte 4.14.4-041404-generic #201712050630 SMP Tue Dec 5 12:07:25
UTC 2017 i686 i686 i686 GNU/Linux
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● apparmor.service loaded failed failed LSB: AppArmor initialization
● udisks2.service loaded failed failed Disk Manager
● ureadahead.service loaded failed failed Read required files in advance
$ 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 Do 2017-12-07 18:04:51 CET; 52min
ago
Docs: man:systemd-sysv-generator(8)
Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited,
status=1/FAILURE)
Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor
initialization...
Dez 07 18:04:51 lieselotte apparmor[689]: * Starting AppArmor profiles
Dez 07 18:04:51 lieselotte apparmor[689]: * AppArmor not available as kernel
LSM.
Dez 07 18:04:51 lieselotte apparmor[689]: ...fail!
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process
exited, code=exited status=1
Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor
initialization.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed
state.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result
'exit-code'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737005/+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
