> I have a running Debian Jessie using systemd with SELinux set to enforcing for a year now - without these problems.
Yes, SELinux is actually maintained in Debian. > Would it be possible that you discuss this with the SELinux-Ubuntu people, There are no "SELinux Ubuntu" people. As I said, this isn't supported in Ubuntu and nobody works on this, so the profiles available in universe are a best-effort basis. Personally I don't know the first thing about SElinux, and I'm afraid I don't have the time to deal with this myself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1563354 Title: systemd-tmpfiles-setup.service fails after switching SELinux to enforcing Status in systemd package in Ubuntu: New Bug description: After switching SELinux to enforcing, the systemd-tmpfiles- setup.service failed: Mar 29 16:12:42 systemd-tmpfiles[546]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Mar 29 16:12:42 systemd-tmpfiles[546]: Unable to fix SELinux security context of /var: Permission denied Mar 29 16:12:42 systemd-tmpfiles[546]: Unable to fix SELinux security context of /var/log: Permission denied Mar 29 16:12:42 systemd-tmpfiles[546]: Unable to fix SELinux security context of /var/lib: Permission denied Mar 29 16:12:42 systemd-tmpfiles[546]: Unable to fix SELinux security context of /home: Permission denied Mar 29 16:12:42 systemd-tmpfiles[546]: Unable to fix SELinux security context of /srv: Permission denied Mar 29 16:12:42 systemd-tmpfiles[546]: Unable to fix SELinux security context of /var/lib/systemd: Permission denied Mar 29 16:12:42 systemd-tmpfiles[546]: Unable to fix SELinux security context of /var/lib/systemd/coredump: Permission denied Mar 29 16:12:43 systemd-tmpfiles[546]: Unable to fix SELinux security context of /var/cache: Permission denied Mar 29 16:12:43 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Mar 29 16:12:43 systemd[1]: Failed to start Create Volatile Files and Directories. Mar 29 16:12:43 systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state. Mar 29 16:12:43 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. No further AVC or audit.log is logged. When manually setting 'setenforce 0' and starting this service, it obviously works fine. My environment: # lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 (Build / packages from last night) # apt-cache policy systemd systemd: Installed: 229-3ubuntu1 Candidate: 229-3ubuntu1 If you need more infos, please drop a short note. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1563354/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
