Created attachment 493842 [details] boot.log Description of problem: I booting Fedora 15, and I see in boot.log: Unable to fix label of /sys/fs/cgroup/systemd: No such file or directory Unable to fix label of /sys/fs/cgroup/cpuset: No such file or directory Unable to fix label of /sys/fs/cgroup/ns: No such file or directory Unable to fix label of /sys/fs/cgroup/cpu: No such file or directory Unable to fix label of /sys/fs/cgroup/cpuacct: No such file or directory Unable to fix label of /sys/fs/cgroup/memory: No such file or directory Unable to fix label of /sys/fs/cgroup/devices: No such file or directory Unable to fix label of /sys/fs/cgroup/freezer: No such file or directory Unable to fix label of /sys/fs/cgroup/net_cls: No such file or directory Unable to fix label of /sys/fs/cgroup/blkio: No such file or directory Is this a regression? Version-Release number of selected component (if applicable): systemd-25-1.fc15.x86_64 How reproducible: Steps to Reproduce: 1. Turn on my computer. :) Actual results: Error messages (and don't turning off my computer, but I tested this only once). Expected results: Systemd working fine. Additional info: kernel-2.6.38.3-17.fc15.x86_64 selinux-policy-3.9.16-15.fc15.noarch
If I use systemd-25-1.fc15.x86_64, my computer will not turn off. I downgrade systemd: systemd-24-1.fc15.x86_64 systemd-gtk-24-1.fc15.x86_64 systemd-units-24-1.fc15.x86_64 My computer work correctly.
*** Bug 699257 has been marked as a duplicate of this bug. ***
Let's not conflate two issues here. the shutdown hang please let's track in 694646. Do you have SELinux enabled? enforcing mode?
Oops, I meant 699114, not 694646.
> Do you have SELinux enabled? enforcing mode? Yes. I sent message into #699114.
fixed in git.
*** Bug 700664 has been marked as a duplicate of this bug. ***
systemd-26-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/systemd-26-1.fc15
systemd-26-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.