Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Rebooting into F40 SilverBlue hang because of systemd-resolved unless selinux is disabled #578

Open
hfiguiere opened this issue Jun 25, 2024 · 8 comments
Open

Rebooting into F40 SilverBlue hang because of systemd-resolved unless selinux is disabled #578

hfiguiere opened this issue Jun 25, 2024 · 8 comments
Labels
bug Something isn't working f40 Related to Fedora 40

Comments

@hfiguiere
Copy link

hfiguiere commented Jun 25, 2024 •
edited
Loading

Describe the bug
I finally applied the bootloadeer failure workaround (#543) to reboot from SB F39 into F40.
The version deployed is

It hangs in the reboot because it can't start systemd-resolved.

If I reboot with selinux=0 added to the boot line. It does boot to the end.
If I reboot with enforce=0 it doesn't. Albeit with enforce=0 autorelabel=1 it did relabel but this didn't solve the issue.

To Reproduce
Please describe the steps needed to reproduce the bug:

  1. Reboot in the F40 deployment
  2. ..

Expected behavior

It boots to the session login and I can login.

Observed

The boot hangs. Pressing ESC show that is hang because it can't start systemd-resolved.

Screenshots

It would be unreadable since it's all written so small (not a SB specific problem, but has been like that since 2017)

OS version:

State: idle
BootedDeployment:
● fedora:fedora/40/x86_64/silverblue
                  Version: 40.20240625.0 (2024-06-25T01:33:01Z)
               BaseCommit: 70a39bcfe2318f754f4ee7736a7c5b7b9ff5f09fa5bf0763e2107d649e96bf4d
             GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
          LayeredPackages: bcc-tools direnv emacs fish flatpak-builder gdb git git-delta google-noto-sans-gurmukhi-fonts gpsbabel
                           libasan moby-engine ninja-build strace svn sysprof thunderbird unbound valgrind vl-gothic-fonts
                           wireguard-tools zsh

The F39 deployment works.

Additional context

From journalctl -r: (entries in reverse order)

Jun 25 12:37:19 rocinante (sd-exec-[761]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Jun 25 12:37:19 rocinante (sd-exec-[761]: /usr/lib/systemd/system-generators/systemd-rc-local-generator failed with exit status 1.
Jun 25 12:37:19 rocinante (sd-exec-[761]: /usr/lib/systemd/system-generators/systemd-cryptsetup-generator failed with exit status 1.
Jun 25 12:37:19 rocinante (sd-exec-[761]: /usr/lib/systemd/system-generators/systemd-getty-generator failed with exit status 1.
Jun 25 12:37:19 rocinante (sd-exec-[761]: /usr/lib/systemd/system-generators/systemd-debug-generator failed with exit status 1.
Jun 25 12:37:19 rocinante (sd-exec-[761]: /usr/lib/systemd/system-generators/zram-generator failed with exit status 1.
Jun 25 12:37:19 rocinante (sd-exec-[761]: /usr/lib/systemd/system-generators/systemd-sysv-generator failed with exit status 1.
Jun 25 12:37:19 rocinante (direxec)[786]: Failed to execute /usr/lib/systemd/system-generators/zram-generator: Permission denied
Jun 25 12:37:19 rocinante kernel: audit: type=1400 audit(1719333439.223:14): avc:  denied  { execute } for  pid=786 comm="(direxec)" n>
Jun 25 12:37:19 rocinante (sd-exec-[761]: /usr/lib/systemd/system-generators/systemd-bless-boot-generator failed with exit status 1.
Jun 25 12:37:19 rocinante (direxec)[783]: Failed to execute /usr/lib/systemd/system-generators/systemd-sysv-generator: Permission deni>
Jun 25 12:37:19 rocinante kernel: audit: type=1400 audit(1719333439.222:13): avc:  denied  { execute } for  pid=783 comm="(direxec)" n>
Jun 25 12:37:19 rocinante (direxec)[775]: Failed to execute /usr/lib/systemd/system-generators/systemd-rc-local-generator: Permission >
Jun 25 12:37:19 rocinante kernel: audit: type=1400 audit(1719333439.213:12): avc:  denied  { execute } for  pid=775 comm="(direxec)" n>
Jun 25 12:37:19 rocinante (direxec)[771]: Failed to execute /usr/lib/systemd/system-generators/systemd-getty-generator: Permission den>
Jun 25 12:37:19 rocinante kernel: audit: type=1400 audit(1719333439.210:11): avc:  denied  { execute } for  pid=771 comm="(direxec)" n>
Jun 25 12:37:19 rocinante (direxec)[770]: Failed to execute /usr/lib/systemd/system-generators/systemd-fstab-generator: Permission den>
Jun 25 12:37:19 rocinante kernel: audit: type=1400 audit(1719333439.209:10): avc:  denied  { execute } for  pid=770 comm="(direxec)" n>
Jun 25 12:37:19 rocinante (direxec)[769]: Failed to execute /usr/lib/systemd/system-generators/systemd-debug-generator: Permission den>
Jun 25 12:37:19 rocinante kernel: audit: type=1400 audit(1719333439.204:9): avc:  denied  { execute } for  pid=769 comm="(direxec)" na>
Jun 25 12:37:19 rocinante (direxec)[768]: Failed to execute /usr/lib/systemd/system-generators/systemd-cryptsetup-generator: Permissio>
Jun 25 12:37:19 rocinante kernel: audit: type=1400 audit(1719333439.203:8): avc:  denied  { execute } for  pid=768 comm="(direxec)" na>
Jun 25 12:37:19 rocinante kernel: audit: type=1400 audit(1719333439.202:7): avc:  denied  { execute } for  pid=767 comm="(direxec)" na>
Jun 25 12:37:19 rocinante (direxec)[767]: Failed to execute /usr/lib/systemd/system-generators/systemd-bless-boot-generator: Permissio>
Jun 25 12:37:19 rocinante kernel: SELinux:  Context system_u:object_r:systemd_zram_generator_exec_t:s0 is not valid (left unmapped).
Jun 25 12:37:19 rocinante kernel: SELinux:  Context system_u:object_r:systemd_sysv_generator_exec_t:s0 is not valid (left unmapped).
Jun 25 12:37:19 rocinante kernel: SELinux:  Context system_u:object_r:systemd_rc_local_generator_exec_t:s0 is not valid (left unmapped>
Jun 25 12:37:19 rocinante kernel: SELinux:  Context system_u:object_r:systemd_getty_generator_exec_t:s0 is not valid (left unmapped).
Jun 25 12:37:19 rocinante kernel: SELinux:  Context system_u:object_r:systemd_fstab_generator_exec_t:s0 is not valid (left unmapped).
Jun 25 12:37:19 rocinante kernel: SELinux:  Context system_u:object_r:systemd_debug_generator_exec_t:s0 is not valid (left unmapped).
Jun 25 12:37:19 rocinante kernel: SELinux:  Context system_u:object_r:systemd_cryptsetup_generator_exec_t:s0 is not valid (left unmapp>
Jun 25 12:37:19 rocinante kernel: SELinux:  Context system_u:object_r:systemd_bless_boot_generator_exec_t:s0 is not valid (left unmapp>

and then

Jun 25 12:37:25 rocinante systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 2.
Jun 25 12:37:25 rocinante audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='uni>
Jun 25 12:37:25 rocinante systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Jun 25 12:37:25 rocinante systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Jun 25 12:37:25 rocinante systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Jun 25 12:37:25 rocinante systemd-resolved[1033]: Failed to start manager: Permission denied
Jun 25 12:37:25 rocinante audit[1033]: AVC avc:  denied  { create } for  pid=1033 comm="systemd-resolve" name="io.systemd.Resolve" sco>
Jun 25 12:37:25 rocinante systemd-resolved[1033]: Failed to bind to varlink socket: Permission denied
Jun 25 12:37:25 rocinante systemd-resolved[1033]: Using system hostname 'rocinante'.
Jun 25 12:37:25 rocinante systemd-resolved[1033]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr>
Jun 25 12:37:25 rocinante systemd-resolved[1033]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jun 25 12:37:25 rocinante systemd-resolved[1033]: Positive Trust Anchors:
Jun 25 12:37:25 rocinante kernel: ath10k_pci 0000:3a:00.0: htt-ver 3.87 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Jun 25 12:37:25 rocinante systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
Jun 25 12:37:25 rocinante audit: BPF prog-id=44 op=UNLOAD
Jun 25 12:37:25 rocinante audit: BPF prog-id=45 op=LOAD
Jun 25 12:37:25 rocinante systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 1.
Jun 25 12:37:25 rocinante audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='uni>
Jun 25 12:37:25 rocinante systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Jun 25 12:37:25 rocinante systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Jun 25 12:37:25 rocinante systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Jun 25 12:37:25 rocinante systemd-resolved[990]: Failed to start manager: Permission denied
Jun 25 12:37:25 rocinante systemd-resolved[990]: Failed to bind to varlink socket: Permission denied
Jun 25 12:37:25 rocinante audit: PROCTITLE proctitle="/usr/lib/systemd/systemd-resolved"
Jun 25 12:37:25 rocinante audit: PATH item=1 name="/run/systemd/resolve/io.systemd.Resolve" nametype=CREATE cap_fp=0 cap_fi=0 cap_fe=0>
Jun 25 12:37:25 rocinante audit: PATH item=0 name="/run/systemd/resolve/" inode=1629 dev=00:1b mode=040755 ouid=990 ogid=989 rdev=00:0>
Jun 25 12:37:25 rocinante audit: CWD cwd="/"
Jun 25 12:37:25 rocinante audit: SOCKADDR saddr=01002F72756E2F73797374656D642F7265736F6C76652F696F2E73797374656D642E5265736F6C766500
Jun 25 12:37:25 rocinante audit[990]: SYSCALL arch=c000003e syscall=49 success=no exit=-13 a0=15 a1=7fff98ff2b80 a2=2a a3=5621d914b330>
Jun 25 12:37:25 rocinante audit[990]: AVC avc:  denied  { create } for  pid=990 comm="systemd-resolve" name="io.systemd.Resolve" scont>
Jun 25 12:37:25 rocinante systemd-resolved[990]: Using system hostname 'rocinante'.
Jun 25 12:37:25 rocinante systemd-resolved[990]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.>
Jun 25 12:37:25 rocinante systemd-resolved[990]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jun 25 12:37:25 rocinante systemd-resolved[990]: Positive Trust Anchors:

and

Jun 25 12:37:32 rocinante systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
Jun 25 12:37:32 rocinante systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Jun 25 12:37:32 rocinante systemd[1]: systemd-resolved.service: Start request repeated too quickly.

If you need more specific log, please ask.
@hfiguiere hfiguiere added the bug Something isn't working label Jun 25, 2024
@travier
Copy link
Member

travier commented Jun 26, 2024

You can try resetting your SELinux policy to the default one with the instructions from: https://docs.fedoraproject.org/en-US/fedora-silverblue/troubleshooting/#_selinux_problems

@travier travier added the f40 Related to Fedora 40 label Jun 26, 2024
@hfiguiere
Copy link
Author

Yes they were difference, and I did reset as instructed. I get a different boot failure unless I boot with selinux=0.

This time, I get dbus-broker to also fail (systemd-resolved seem to still fail but no hang the whole boot) :

Jun 26 10:12:42 rocinante systemd[1]: NetworkManager.service: Job NetworkManager.service/start failed with result 'dependency'.
Jun 26 10:12:42 rocinante systemd[1]: NetworkManager-wait-online.service: Job NetworkManager-wait-online.service/start failed with res>
Jun 26 10:12:42 rocinante systemd[1]: Dependency failed for NetworkManager-wait-online.service - Network Manager Wait Online.
Jun 26 10:12:42 rocinante systemd[1]: Dependency failed for NetworkManager.service - Network Manager.
Jun 26 10:12:42 rocinante systemd[1]: Failed to start dbus-broker.service - D-Bus System Message Bus.
Jun 26 10:12:42 rocinante systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
Jun 26 10:12:42 rocinante systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 10:12:42 rocinante dbus-broker-launch[1066]: Exiting due to fatal error: -131
Jun 26 10:12:42 rocinante dbus-broker-launch[1066]:       main @ ../src/launch/main.c +178
Jun 26 10:12:42 rocinante dbus-broker-launch[1066]: ERROR run @ ../src/launch/main.c +152: Return code 1
Jun 26 10:12:42 rocinante dbus-broker-launch[1066]: Access denied in /etc/selinux/targeted/contexts/dbus_contexts +1: /etc/selinux/tar>
Jun 26 10:12:42 rocinante audit[1066]: AVC avc:  denied  { open } for  pid=1066 comm="dbus-broker-lau" path="/etc/selinux/targeted/con>

And then a cascading failure of other services include systemd-logind gdm.service, etc.

In the end the last message on screen is about plymouth service stopping. and it hang there.

@hfiguiere
Copy link
Author

And I checked there was no selinux policy difference anymore

@hfiguiere
Copy link
Author

also the question is WTF changed the selinux policy. I never touch that.

@travier
Copy link
Member

travier commented Jun 27, 2024

There was an issue a while ago that made it local change even if you hadn't touched it. This should not matter as it gets updated automatically now but just in case.

@travier
Copy link
Member

travier commented Jun 27, 2024

I wonder if autorelabel=1 interacts well with ostree. I have not tried it. Can you list here the labels of the binaries that fail to start? ls -alZ /sur/bin/..

@hfiguiere
Copy link
Author 

-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                       106784 Dec 31  1969 systemd
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        36720 Dec 31  1969 systemd-backlight
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        20280 Dec 31  1969 systemd-battery-check
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        24384 Dec 31  1969 systemd-binfmt
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        32848 Dec 31  1969 systemd-bless-boot
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        16160 Dec 31  1969 systemd-boot-check-no-failures
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        24336 Dec 31  1969 systemd-bsod
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        16096 Dec 31  1969 systemd-cgroups-agent
-rwxr-xr-x. 2 root root system_u:object_r:systemd_coredump_exec_t:s0            98736 Dec 31  1969 systemd-coredump
lrwxrwxrwx. 2 root root system_u:object_r:lib_t:s0                                 28 May  5 17:13 systemd-cryptsetup -> ../../bin/systemd-cryptsetup
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                       160672 Dec 31  1969 systemd-executor
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        45088 Dec 31  1969 systemd-export
-rwxr-xr-x. 2 root root system_u:object_r:fsadm_exec_t:s0                       32584 Dec 31  1969 systemd-fsck
-rwxr-xr-x. 2 root root system_u:object_r:fsadm_exec_t:s0                       28424 Dec 31  1969 systemd-growfs
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        28688 Dec 31  1969 systemd-hibernate-resume
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                       236192 Dec 31  1969 systemd-homed
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                       239272 Dec 31  1969 systemd-homework
-rwxr-xr-x. 2 root root system_u:object_r:systemd_hostnamed_exec_t:s0           57808 Dec 31  1969 systemd-hostnamed
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        61616 Dec 31  1969 systemd-import
-rwxr-xr-x. 2 root root system_u:object_r:systemd_importd_exec_t:s0             49288 Dec 31  1969 systemd-importd
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        32616 Dec 31  1969 systemd-import-fs
-rwxr-xr-x. 2 root root system_u:object_r:systemd_initctl_exec_t:s0             24376 Dec 31  1969 systemd-initctl
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        24576 Dec 31  1969 systemd-integritysetup
-rwxr-xr-x. 2 root root system_u:object_r:syslogd_exec_t:s0                    209184 Dec 31  1969 systemd-journald
-rwxr-xr-x. 2 root root system_u:object_r:systemd_localed_exec_t:s0             57576 Dec 31  1969 systemd-localed
-rwxr-xr-x. 2 root root system_u:object_r:systemd_logind_exec_t:s0             299344 Dec 31  1969 systemd-logind
-rwxr-xr-x. 2 root root system_u:object_r:systemd_machined_exec_t:s0           140928 Dec 31  1969 systemd-machined
-rwxr-xr-x. 2 root root system_u:object_r:fsadm_exec_t:s0                       16112 Dec 31  1969 systemd-makefs
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        53688 Dec 31  1969 systemd-measure
-rwxr-xr-x. 2 root root system_u:object_r:systemd_modules_load_exec_t:s0        24592 Dec 31  1969 systemd-modules-load
-rwxr-xr-x. 2 root root system_u:object_r:systemd_networkd_exec_t:s0          1770712 Dec 31  1969 systemd-networkd
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        41144 Dec 31  1969 systemd-networkd-wait-online
-rwxr-xr-x. 2 root root system_u:object_r:systemd_network_generator_exec_t:s0   45208 Dec 31  1969 systemd-network-generator
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        65920 Dec 31  1969 systemd-oomd
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        28744 Dec 31  1969 systemd-pcrextend
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                       161176 Dec 31  1969 systemd-pcrlock
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                       123992 Dec 31  1969 systemd-portabled
-rwxr-xr-x. 2 root root system_u:object_r:systemd_pstore_exec_t:s0              24472 Dec 31  1969 systemd-pstore
-rwxr-xr-x. 2 root root system_u:object_r:systemd_importd_exec_t:s0            115696 Dec 31  1969 systemd-pull
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        15952 Dec 31  1969 systemd-quotacheck
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        28448 Dec 31  1969 systemd-random-seed
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        24360 Dec 31  1969 systemd-remount-fs
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        16144 Dec 31  1969 systemd-reply-password
-rwxr-xr-x. 2 root root system_u:object_r:systemd_resolved_exec_t:s0           597968 Dec 31  1969 systemd-resolved
-rwxr-xr-x. 2 root root system_u:object_r:systemd_rfkill_exec_t:s0              28496 Dec 31  1969 systemd-rfkill
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        65608 Dec 31  1969 systemd-shutdown
-rwxr-xr-x. 2 root root system_u:object_r:systemd_sleep_exec_t:s0               53280 Dec 31  1969 systemd-sleep
-rwxr-xr-x. 2 root root system_u:object_r:systemd_socket_proxyd_exec_t:s0       32744 Dec 31  1969 systemd-socket-proxyd
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        57696 Dec 31  1969 systemd-storagetm
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        20280 Dec 31  1969 systemd-sulogin-shell
-rwxr-xr-x. 2 root root system_u:object_r:systemd_sysctl_exec_t:s0              32792 Dec 31  1969 systemd-sysctl
lrwxrwxrwx. 3 root root system_u:object_r:lib_t:s0                                 41 Apr 24  2023 systemd-sysroot-fstab-check -> system-generators/systemd-fstab-generator
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                       140576 Dec 31  1969 systemd-sysupdate
-rwxr-xr-x. 2 root root system_u:object_r:systemd_timedated_exec_t:s0           49256 Dec 31  1969 systemd-timedated
-rwxr-xr-x. 2 root root system_u:object_r:systemd_timedated_exec_t:s0           69968 Dec 31  1969 systemd-timesyncd
-rwxr-xr-x. 2 root root system_u:object_r:systemd_timedated_exec_t:s0           24376 Dec 31  1969 systemd-time-wait-sync
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        28688 Dec 31  1969 systemd-tpm2-setup
lrwxrwxrwx. 3 root root system_u:object_r:lib_t:s0                                 17 Sep 15  2021 systemd-udevd -> ../../bin/udevadm
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        16136 Dec 31  1969 systemd-update-done
-rwxr-xr-x. 3 root root system_u:object_r:init_exec_t:s0                         3853 Dec 31  1969 systemd-update-helper
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        24448 Dec 31  1969 systemd-update-utmp
-rwxr-xr-x. 2 root root system_u:object_r:systemd_userdbd_exec_t:s0             28544 Dec 31  1969 systemd-userdbd
-rwxr-xr-x. 2 root root system_u:object_r:systemd_logind_exec_t:s0              24376 Dec 31  1969 systemd-user-runtime-dir
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        15920 Dec 31  1969 systemd-user-sessions
-rwxr-xr-x. 2 root root system_u:object_r:systemd_userdbd_exec_t:s0             32704 Dec 31  1969 systemd-userwork
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        32600 Dec 31  1969 systemd-vconsole-setup
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        32952 Dec 31  1969 systemd-veritysetup
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        24344 Dec 31  1969 systemd-volatile-root
-rwxr-xr-x. 2 root root system_u:object_r:init_exec_t:s0                        16160 Dec 31  1969 systemd-xdg-autostart-condition

-rwxr-xr-x. 2 root root system_u:object_r:dbusd_exec_t:s0 228632 Dec 31  1969 /usr/bin/dbus-broker
-rwxr-xr-x. 2 root root system_u:object_r:dbusd_exec_t:s0 132384 Dec 31  1969 /usr/bin/dbus-broker-launch

@hfiguiere
Copy link
Author

Did reboot into F40 with enforce=0 autorelabel=1 and upon reboot as it, one more time, failed to stop at grub, it magically worked.

Checked I'm running F40, and I checked that selinux was enabled and enforcing.

As to why I ended up in that situation I don't know, but there surely should be an easier way to get out of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working f40 Related to Fedora 40
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hfiguiere @travier