Description of problem: After rebasing silverblue to fc31. I cannot boot system Version-Release number of selected component (if applicable): How reproducible: Rebase silverblue fedora 31 Steps to Reproduce: 1. Boot system 2. Logfile shows Sep 18 14:46:24 localhost.localdomain systemd[909]: systemd-logind.service: Failed to set up special execution directory in /var/lib: Permission denied Sep 18 14:46:24 localhost.localdomain systemd[909]: systemd-logind.service: Failed at step STATE_DIRECTORY spawning /sbin/modprobe: Permission denied Sep 18 14:46:24 localhost.localdomain systemd[911]: systemd-logind.service: Failed to set up special execution directory in /var/lib: Permission denied Sep 18 14:46:24 localhost.localdomain systemd[911]: systemd-logind.service: Failed at step STATE_DIRECTORY spawning /usr/lib/systemd/systemd-logind: Permission denied Sep 18 14:46:24 localhost.localdomain systemd[1]: systemd-logind.service: Main process exited, code=exited, status=238/STATE_DIRECTORY Sep 18 14:46:24 localhost.localdomain systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Sep 18 14:46:24 localhost.localdomain systemd[1]: Failed to start Login Service. 3. Actual results: Doesn't boot Expected results: Boots correctly Additional info:
Any updates? i would like to try fc31 silverblue.
Hi Martin, Could you please attach also output from audit logs? # ausearch -m AVC THanks, Lukas.
Created attachment 1618920 [details] Output of ausearch -m AVC Here it is
Appears that I have run into this updating my dell xps13 9370 from Silverblue 30 to 31.
ok I had some selinux denials on gssproxy default.sock and also on /var/lib/AccountService/users/gdm which I have resolved. I still have selinux denials reported in ausearch -m AVC for linger. I have run restorecon on all of this: /sysroot/ostree/deploy/fedora/var/lib/systemd/linger /sysroot/ostree/deploy/fedora/var/lib/systemd/linger/me /var/lib/systemd/linger /var/lib/systemd/linger/me I have removed 'me' from the linger directory. And I have run loginctl disable-linger. But I still have this in the ausearch log: (There are more pids behind, but all the denials are for modprobe and d-logind with name=linger. I still cannot boot into F31. time->Sat Oct 12 10:03:26 2019 type=AVC msg=audit(1570874606.540:103): avc: denied { read } for pid=919 comm="(modprobe)" name="linger" dev="dm-0" ino=2621453 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:systemd_logind_var_lib_t:s0 tclass=dir permissive=0 ---- time->Sat Oct 12 10:03:26 2019 type=AVC msg=audit(1570874606.543:104): avc: denied { read } for pid=920 comm="(d-logind)" name="linger" dev="dm-0" ino=2621453 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:systemd_logind_var_lib_t:s0 tclass=dir permissive=0 ---- time->Sat Oct 12 10:03:26 2019 type=AVC msg=audit(1570874606.551:108): avc: denied { read } for pid=923 comm="(modprobe)" name="linger" dev="dm-0" ino=2621453 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:systemd_logind_var_lib_t:s0 tclass=dir permissive=0 ---- time->Sat Oct 12 10:03:26 2019 type=AVC msg=audit(1570874606.553:109): avc: denied { read } for pid=924 comm="(d-logind)" name="linger" dev="dm-0" ino=2621453 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:systemd_logind_var_lib_t:s0 tclass=dir permissive=0 ---- time->Sat Oct 12 10:03:26 2019 type=AVC msg=audit(1570874606.561:113): avc: denied { read } for pid=927 comm="(modprobe)" name="linger" dev="dm-0" ino=2621453 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:systemd_logind_var_lib_t:s0 tclass=dir permissive=0 ---- time->Sat Oct 12 10:03:26 2019 type=AVC msg=audit(1570874606.564:114): avc: denied { read } for pid=928 comm="(d-logind)" name="linger" dev="dm-0" ino=2621453 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:systemd_logind_var_lib_t:s0 tclass=dir permissive=0
This can be closed. I reinstalled silverblue and i don't see this error anymore
I just rebased to F30 and back to F31 and this issue persists