Description of problem: On systemctl start bluetooth.service, it aborts with code=exited, status=226/NAMESPACE. Note that /tmp is a symlink to sysroot/tmp due to this being an ostree-based system. Version-Release number of selected component (if applicable): systemd-231-9.fc26 bluez-5.41-1.fc26 How reproducible: Consistent Steps to Reproduce: 1. Run system based on OSTree 2. systemctl start bluetooth.service Actual results: Active: failed (Result: exit-code) Main PID: 14706 (code=exited, status=226/NAMESPACE) Expected results: Active: active (running) Additional info: If I copy bluetooth.service to /etc/systemd/system/bluetooth.service, and modify it to have ProtectHome=read-only, it starts succesfully.
Pffff, yeah, it's possible. There's been a major restructuring of the namespacing code in systemd-232 (soon to be released). Let's wait for that and see if that changes anything.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
https://github.com/systemd/systemd/pull/6293
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.