Systemd -- maybe?

During boot a lot of systemd services start up. Odd, new behavior for me is that firewalld and ModemManager services now time out instead of completing. And, oddly, the gnome console program “ptyxis” also doesn’t execute successfully. I’ve investigated the firewalld issue as far as I knew how to take it, which was to my snip below.

Here’s what’s odd… If I just log in and then do nothing but wait a really long time… >10min… then ptyxis will work fine. systemctl start firewalld executes fine. systemctl start ModemManager starts fine.

Any guesses? I feel like I’m not finding any true leads on this in the journalctl logs. What else do I need to do to track this down?

systemd[1]: Starting firewalld.service - firewalld - dynamic firewall daemon…
firewalld[7137]: ERROR: ‘python-nftables’ failed: internal:0:0-0: Error: Could not process rule: Operation not permitted

JSON blob:
{“nftables”: [{“metainfo”: {“json_schema_version”: 1}}, {“add”: {“table”: {“family”: “inet”, “name”: “firewalld”, “flags”: [“owner”, “persist”]}}}, {“delete”: {“table”: {“family”: “inet”, “name”: “firewalld”
}}}, {“add”: {“table”: {“family”: “inet”, “name”: “firewalld”, “flags”: [“owner”, “persist”]}}}]}

I am wondering if you have a hardware issue.

Check dmesg output for any hardware errors, especially disk errors.
Also unplug usb devices and see if the system boots up cleanly.

Do you see anything?

Do you have firewalld AND nftables? Looks like a conflict here?

Try this:

sudo dnf distro-sync --refresh --allowerasing
sudo fixfiles -F onboot; sudo reboot

If the issue persists, post the output:

sudo dnf check
sudo rpm -V -a

I think Barry is right. Numerous issues related to a disk.