Description of problem: systemd-homed.service fails. Version-Release number of selected component (if applicable): $ rpm -qf /usr/lib/systemd/system/systemd-homed.service systemd-245.6-2.mga8 How reproducible: Always. Steps to Reproduce: 1. Boot Mageia 8 in default configuration (e.g. after install) 2. Check status of service systemd-homed.service using command: systemctl status systemd-homed.service 3. See lines like: systemd-homed.service: Main process exited, code=exited, status=1/FAILURE systemd-homed.service: Failed with result 'exit-code'. Failed to start Home Area Manager. Extra information: $ uname -a Linux marte-vm-mageia-8 5.7.5-desktop-1.mga8 #1 SMP Wed Jun 24 14:52:47 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ rpm -qf /usr/lib/systemd/system/systemd-homed.service systemd-245.6-2.mga8 $ rpm -qi systemd-245.6-2.mga8 | grep -i source Source RPM : systemd-245.6-2.mga8.src.rpm $ systemctl --version systemd 245 (245) +PAM +AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN -PCRE2 default-hierarchy=unified $ systemctl | grep fail ● systemd-homed.service loaded failed failed Home Area Manager $ systemctl status systemd-homed.service ● systemd-homed.service - Home Area Manager Loaded: loaded (/usr/lib/systemd/system/systemd-homed.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2020-06-29 23:38:46 WEST; 2s ago Docs: man:systemd-homed.service(8) Process: 1146 ExecStart=/usr/lib/systemd/systemd-homed (code=exited, status=1/FAILURE) Main PID: 1146 (code=exited, status=1/FAILURE) Status: "Processing requests..." CPU: 914ms jun 29 23:38:46 marte-vm-mageia-8 systemd[1]: Starting Home Area Manager... jun 29 23:38:46 marte-vm-mageia-8 systemd[1]: systemd-homed.service: Main process exited, code=exited, status=1/FAILURE jun 29 23:38:46 marte-vm-mageia-8 systemd[1]: systemd-homed.service: Failed with result 'exit-code'. jun 29 23:38:46 marte-vm-mageia-8 systemd[1]: Failed to start Home Area Manager. $ journalctl -b0 -u systemd-homed.service -- Logs begin at Sun 2020-06-28 00:00:24 WEST, end at Mon 2020-06-29 23:38:46 WEST. -- jun 29 23:38:46 marte-vm-mageia-8 systemd[1]: Starting Home Area Manager... jun 29 23:38:46 marte-vm-mageia-8 systemd[1]: systemd-homed.service: Main process exited, code=exited, status=1/FAILURE jun 29 23:38:46 marte-vm-mageia-8 systemd[1]: systemd-homed.service: Failed with result 'exit-code'. jun 29 23:38:46 marte-vm-mageia-8 systemd[1]: Failed to start Home Area Manager.
Thank you for the report. I copnfirm the same result. Assigning to base system maintainers. If this is wrong, pleas re-assign more corretly (I will look out for that).
CC: (none) => lewyssmithAssignee: bugsquad => basesystem
Joseph Wang said: The problem is that systemd has homed set up so that "disable" doesn't work. see https://github.com/systemd/systemd/issues/15083 The way to remove the error is systemctl mask homed.service They say that it's going to be fixed in the next release of systemd.
CC: (none) => yves.brungard_mageia
@papoteur : thanks for that useful comment.
(In reply to papoteur from comment #2) > They say that it's going to be fixed in the next release of systemd. So this bug must remain open until that arrives.
CC: lewyssmith => (none)
https://github.com/systemd/systemd/pull/15109 Fixed upstream and new version of this is already in Cauldron since a while. Also, this is now disabled by default.
Status: NEW => RESOLVEDResolution: (none) => FIXEDCC: (none) => ouaurelien