Fedora 40 Installation No Longer Boots After Wireshark Installation

I’m going to take a break from the keyboard. I should be back in about 30 minutes or so.

I don’t think so. Most likey this will retain the error or let the upgrade fail.

You mentioned wireshark did create a group and you added your userid to this group.
does getent passwd and getent group produce any errors?
Check also id and groups for errors

1 Like

I still have a KDE f40 vm here. Starting up and try to reproduce…

Happy to report that upgrading to Fedora 42 solved the problem!

I’m still a bit worried to not understand what happened, but at least I’m not stuck anymore.

@glb thank you very much for your time, patience, and advice. I had a bad day at work, and then I had my boot problem. You, sir, helped me avoid going crazy.

To the others who took the time to answer my call for help, thank you too; it’s very much appreciated.

1 Like

FWIW, I’m a fan of making filesystem snapshots before I do anything too wild with my PC. Unfortunately, that is a bit tricky with Btrfs (I use ZFS).

Good to know, that goes in my Linux notes right away.

Suse has done a fantastic integration of btrfs snapshots with system updates. It’s also very easy to roll-back to a snapshot in grub.

could not reproduce with a fully updated f40 KDE vm.

2 Likes