Boot issue and log spam

Bazzite
1

Hi, I’ve switched to Bazzite recently and sometimes when I try to boot it just hangs at the loading screen with no end in sight. By pressing the reboot button on my PC I can force it to retry and that tends to work.

So I figured, why not try to check the logs in KJournald Browser and try to figure out the issue. However, it doesn’t appear that the failed boot shows up at all. But I noticed there’s a lot of log spam even with a successful boot. So I wanted to ask about it here and basically give the Bazzite developers, if they happen to read this, the feedback that the boot logs get a lot of errors out of the box in Bazzite.

08:50:45.980 UTC /usr/lib/tmpfiles.d/static-nodes-permissions.conf:12: Failed to resolve group ‘audio’: No such process
08:50:45.980 UTC /usr/lib/tmpfiles.d/static-nodes-permissions.conf:13: Failed to resolve group ‘audio’: No such process
08:50:45.980 UTC /usr/lib/tmpfiles.d/static-nodes-permissions.conf:14: Failed to resolve group ‘disk’: No such process
08:50:45.980 UTC /usr/lib/tmpfiles.d/static-nodes-permissions.conf:18: Failed to resolve group ‘kvm’: No such process
08:50:45.980 UTC /usr/lib/tmpfiles.d/static-nodes-permissions.conf:19: Failed to resolve group ‘kvm’: No such process
08:50:45.981 UTC /usr/lib/tmpfiles.d/static-nodes-permissions.conf:20: Failed to resolve group ‘kvm’: No such process
08:50:45.988 UTC systemd-tmpfiles-setup.service /usr/lib/tmpfiles.d/systemd.conf:11: Failed to resolve group ‘utmp’: No such process
08:50:45.988 UTC systemd-tmpfiles-setup.service /usr/lib/tmpfiles.d/var.conf:15: Failed to resolve group ‘utmp’: No such process
08:50:45.988 UTC systemd-tmpfiles-setup.service /usr/lib/tmpfiles.d/var.conf:16: Failed to resolve group ‘utmp’: No such process
08:50:45.988 UTC systemd-tmpfiles-setup.service /usr/lib/tmpfiles.d/var.conf:17: Failed to resolve group ‘utmp’: No such process
08:50:46.105 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:38 Unknown group ‘tty’, ignoring.
08:50:46.105 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:39 Unknown group ‘tty’, ignoring.
08:50:46.105 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:40 Unknown group ‘tty’, ignoring.
08:50:46.105 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:41 Unknown group ‘tty’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:44 Unknown group ‘kmem’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:46 Unknown group ‘input’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:49 Unknown group ‘video’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:50 Unknown group ‘video’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:51 Unknown group ‘video’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:52 Unknown group ‘video’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:53 Unknown group ‘video’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:54 Unknown group ‘video’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:56 Unknown group ‘render’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:57 Unknown group ‘render’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:58 Unknown group ‘render’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:60 Unknown group ‘sgx’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:61 Unknown group ‘sgx’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:67 Unknown group ‘audio’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:77 Unknown group ‘audio’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:78 Unknown group ‘audio’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:79 Unknown group ‘video’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:81 Unknown group ‘lp’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:82 Unknown group ‘lp’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:83 Unknown group ‘lp’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:84 Unknown group ‘lp’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:85 Unknown group ‘lp’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:86 Unknown group ‘lp’, ignoring.
08:50:46.106 UTC systemd-udevd.service /usr/lib/udev/rules.d/50-udev-default.rules:88 Unknown group ‘disk’, ignoring.
06:50:52.702 UTC systemd-udevd.service /usr/lib/udev/rules.d/99-thrustmaster-wheel-perms.rules:14 Invalid operator for DRIVER.
06:50:54.591 UTC /usr/bin/mount for / exited with exit status 32.
06:50:54.591 UTC init.scope Failed to start systemd-remount-fs.service - Remount Root and Kernel File Systems.
06:50:54.790 UTC systemd-tmpfiles-setup.service “/home” already exists and is not a directory.
06:50:54.790 UTC systemd-tmpfiles-setup.service “/srv” already exists and is not a directory.
06:50:54.794 UTC systemd-tmpfiles-setup.service “/root” already exists and is not a directory.
06:50:55.648 UTC bluetooth.service plugins/wake-policy.c:wake_policy_probe() Unable to load key file from /etc/bluetooth/wake-policy.conf: (No such file or directory)
06:50:55.648 UTC bluetooth.service profiles/audio/avctp.c:avctp_server_socket() setsockopt(L2CAP_OPTIONS): Invalid argument (22)
06:50:56.573 UTC systemd-logind.service Failed to open ‘/boot//loader/entries’: Remote address changed
06:50:59.787 UTC dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@0.service failed to retrieve rpm info for path ‘/etc/selinux/targeted/active/modules/100/bootupd’:
06:50:59.790 UTC setroubleshootd.service SELinux is preventing bootupctl from execute access on the file /usr/bin/ostree. For complete SELinux messages run: sealert -l 1f85c15a-65c9-45c6-8737-8705b5033a58
06:50:59.810 UTC setroubleshootd.service SELinux is preventing bootupctl from ‘read, open’ accesses on the file /usr/bin/ostree. For complete SELinux messages run: sealert -l ce6c09f2-b1c8-4450-ba7c-d5d6799f86a6
06:50:59.832 UTC setroubleshootd.service SELinux is preventing bootupctl from execute_no_trans access on the file /usr/bin/ostree. For complete SELinux messages run: sealert -l 4d005a91-cf84-459f-a18a-830074171f6a
06:50:59.850 UTC setroubleshootd.service SELinux is preventing ostree from map access on the file /usr/bin/ostree. For complete SELinux messages run: sealert -l 1a7cfd60-96fe-4972-afdd-5b957847465a
06:50:59.884 UTC setroubleshootd.service SELinux is preventing ostree from read access on the file /etc/passwd. For complete SELinux messages run: sealert -l 3d987a15-ce8e-473e-836f-9d76561b2a8e
06:50:59.902 UTC setroubleshootd.service SELinux is preventing ostree from open access on the file /etc/passwd. For complete SELinux messages run: sealert -l bac1c136-a799-4e3f-b8c1-8ed4464898a7
06:50:59.920 UTC setroubleshootd.service SELinux is preventing ostree from getattr access on the file /etc/passwd. For complete SELinux messages run: sealert -l 1bba8693-75e9-4fdc-abd8-cdb5534ab19b
06:50:59.939 UTC setroubleshootd.service SELinux is preventing ostree from using the dac_read_search capability. For complete SELinux messages run: sealert -l b95eafdd-214c-4de4-9d1b-96794f6a24c7
06:50:59.966 UTC setroubleshootd.service failed to retrieve rpm info for path ‘/sysroot/ostree/repo/objects’:
06:50:59.967 UTC setroubleshootd.service SELinux is preventing ostree from write access on the directory /sysroot/ostree/repo/objects. For complete SELinux messages run: sealert -l f74cd9b7-f809-40bf-90db-bf4f520f3b0d
06:50:59.994 UTC setroubleshootd.service failed to retrieve rpm info for path ‘/run/ostree-booted’:
06:50:59.996 UTC setroubleshootd.service SELinux is preventing ostree from getattr access on the file /run/ostree-booted. For complete SELinux messages run: sealert -l b677c7a4-5c7d-4933-bf8a-480288e5d23e
06:51:00.015 UTC setroubleshootd.service SELinux is preventing ostree from remount access on the filesystem . For complete SELinux messages run: sealert -l d67b0807-1703-49ad-840f-c7e541e7b71f
06:51:00.033 UTC setroubleshootd.service SELinux is preventing ostree from write access on the directory /sysroot/ostree/repo/objects. For complete SELinux messages run: sealert -l f74cd9b7-f809-40bf-90db-bf4f520f3b0d
06:51:01.615 UTC dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@0.service failed to retrieve rpm info for path ‘/etc/selinux/targeted/active/modules/100/tuned’:
06:51:01.616 UTC setroubleshootd.service SELinux is preventing tuned-ppd from write access on the file /etc/tuned/ppd_base_profile. For complete SELinux messages run: sealert -l 3105e11a-1773-40c3-bbd0-3a724c35f42d
06:51:04.775 UTC user@970.service Ignoring duplicate name ‘org.freedesktop.Akonadi.Control’ in service file ‘/usr/share//dbus-1/services/org.freedesktop.Akonadi.Control.service’
06:51:13.561 UTC user@1000.service Ignoring duplicate name ‘org.freedesktop.Akonadi.Control’ in service file ‘/usr/share//dbus-1/services/org.freedesktop.Akonadi.Control.service’
06:51:15.534 UTC bluetooth.service src/profile.c:ext_start_servers() L2CAP server failed for Message Notification: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
06:51:15.534 UTC bluetooth.service src/profile.c:ext_start_servers() L2CAP server failed for Message Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
06:51:15.534 UTC bluetooth.service src/profile.c:ext_start_servers() L2CAP server failed for Phone Book Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
06:51:15.534 UTC bluetooth.service src/profile.c:ext_start_servers() L2CAP server failed for File Transfer: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
06:51:15.534 UTC bluetooth.service src/profile.c:ext_start_servers() L2CAP server failed for Object Push: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
06:51:16.125 UTC user@1000.service busno=4, sleep-multiplier = 1,30. Testing for supported feature 0x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO]
06:51:23.405 UTC systemd-logind.service Failed to open ‘/boot//loader/entries’: Remote address changed
07:43:42.900 UTC init.scope Failed to start logrotate.service - Rotate log files.
07:43:45.443 UTC setroubleshootd.service failed to retrieve rpm info for path ‘/var/log/boot.log’:
07:43:46.041 UTC dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@1.service failed to retrieve rpm info for path ‘/etc/selinux/targeted/active/modules/100/logrotate’:
07:43:47.116 UTC setroubleshootd.service SELinux is preventing logrotate from getattr access on the file /var/log/boot.log. For complete SELinux messages run: sealert -l 6711e645-7ccc-4240-8f95-ad09fcf14cbc
07:43:48.187 UTC setroubleshootd.service SELinux is preventing logrotate from getattr access on the file /var/log/boot.log. For complete SELinux messages run: sealert -l 6711e645-7ccc-4240-8f95-ad09fcf14cbc

There were even more udev rule errors, but you get the gist. Anything I could do to trim down the log spam, or figure out the boot issue when it happens again?

2 Likes
2

The root cause is the system’s SELinux policy being too restrictive for ostree , the core technology of Silverblue, preventing it from working correctly during boot.

Here is the step-by-step process to create a local SELinux policy to fix this.

Step 1: Temporarily Switch to Permissive Mode

First, we need to allow the system to boot properly so we can apply a fix. Permissive mode tells SELinux to log errors but not actually block the problematic actions.

In a terminal, run:

sudo setenforce 0

Now reboot your computer. The system should now start up without failing, which confirms SELinux is the culprit.

Step 2: Generate and Install the Local Policy Fix

After rebooting into permissive mode, your system will have logged all the actions that it would have denied. We can use these logs to automatically generate a permanent fix.

Run these two commands, one after the other:

  1. Generate the policy module. This command reads the recent denial logs and creates a local fix module named my-ostree-fix .
sudo ausearch -m AVC -ts recent | audit2allow -M my-ostree-fix
  1. Install the module. This command loads the fix you just created into your system’s core SELinux policy.
sudo semodule -i my-ostree-fix.pp

Step 3: Final Steps: Enable Enforcing Mode and Verify the Fix

Now that the fix is installed, it’s time to return your system to its most secure state and confirm that every part of the solution worked.

  1. Re-enable Enforcing mode:
sudo setenforce 1
  1. Reboot your system:
reboot
  1. Run the final verification checks. After the system reboots, run these commands in the terminal:
  • Check that SELinux is enforcing:
getenforce

The expected output is Enforcing .

  • Check that the custom module is loaded:
sudo semodule -l | grep my-ostree-fix

The expected output should be the name of your module, my-ostree-fix .

  • Check for any new SELinux denials:
sudo ausearch -m AVC -ts recent

The expected output is <no matches> .

If all three commands give the expected output, you have successfully resolved the SELinux boot failures. Your system is now stable and secure.

Not 100% sure about this, but I think that this was bugging my sleep/wake cycle. Suspend now works as well for me.

3

The permissions error on boot.log can be fixed with this command:

sudo restorecon -v /var/log/boot.log

I would be careful of any AI generated solutions, and be sure
you understand what they are going to do.

1 Like
4

Hey thanks for the additional info. I did try sudo fixfiles -F onboot, but it didn’t solve the issue for me sadly. I’m new to this, hope I didn’t do something wrong in the post Ive made above.

1 Like
5

No, that’s cool.
It was just a heads up.

1 Like