After installing: tomoyo-tools-2.5.0-4.mga4 lib64tomoyotools3-2.5.0-4.mga4 and modifying the commandline for the kernel in GRUB by adding security=tomoyo i get: [FAILED] Failed to start LSB: TOMOYO Linux MAC logging daemon. in /var/log/boot.log And journalctl -b shows me: Command line: BOOT_IMAGE=linux root=UUID=65f5a484-73d6-49aa-bc63-7f78f3479b82 splash quiet resume=UUID=f641866c-fe7a-4a83-b5cb-0409c738a001 security=tomoyo kernel: Calling /sbin/tomoyo-init to load policy. Please wait. kernel: TOMOYO: 2.5.0 kernel: Mandatory Access Control activated. tomoyo-auditd[765]: ccs-auditd wird gestartet: tomoyo-auditd [remote_ip:remote_port] tomoyo-auditd[765]: See /etc/tomoyo/tools/auditd.conf for configuration. tomoyo-auditd[765]: [ERROR] tomoyo-auditd.service: control process exited, code=exited status=1 systemd[1]: Failed to start LSB: TOMOYO Linux MAC logging daemon. systemd[1]: Unit tomoyo-auditd.service entered failed state. systemd[1]: tomoyo-auditd.service: control process exited, code=exited status=1 systemd[1]: Failed to start LSB: TOMOYO Linux MAC logging daemon. systemd[1]: Unit tomoyo-auditd.service entered failed state. How reproducible: Steps to Reproduce: 1. Install Tomoyo Linux packages via MCC 2. follow the installation steps provided at the Tomoyo Homepage After consulting the Tomoyo User List I got the following advice: edit the /etc/rc.d/init.d/tomoyo-auditd file and change OPTIONS="/dev/null /var/log/tomoyo/reject_log.conf" to OPTIONS="" That did solve the problem and Tomoyo starts without producing errors Reproducible: Steps to Reproduce:
Keywords: (none) => TriagedAssignee: bugsquad => tmbSource RPM: (none) => tomoyo
This is still present with Mageia 5_x64 Same problem, same solution!
Hardware: All => x86_64Version: 4 => 5
Summary: Tomoyo Linux wont start without errors => Tomoyo Linux wont work out of the box
Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change it's status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja
CC: (none) => marja11
No reply, so closing as OLD
Resolution: (none) => OLDStatus: NEW => RESOLVED