Yesterday I used my Fedora 40 laptop computer. Today, it asks for the LUKS password, as usual, and after that it freezes here (at least for 30 minutes and counting):
If I try any of the first 3 options, the behavior is the one described above. If I try the fourth option (the rescue one), it is the same but it freezes with a black screen instead of the Lenovo logo.
Edit 2
I am trying this. After hitting ctrl+x to reboot (step 2), it asks for the LUKS encryption password in a black terminal screen. After entering the password and pressing enter, it freezes. The cursor goes to a new line, still blinks, but that’s it, does not print anything else, I cannot write anything.
Looks like systemd is still trying to startup the system.
If you press ESC the splash screen should be replaced with the console output.
What is the last few lines on the screen showing?
Likely this stopped working after you update the kernel.
In which case try booting from the previous kernel.
Does the system now boot up?
This just happened to me again, the second time in 6 months… It freezes no matter what kernel I choose. Also, I am not aware of any update the last time I used the PC.
Is this a one off problem or a persistent failure to boot?
In grub edit the command to remove the rhgb and quiet options.
Do you see any messages after you enter the luks password?
If you get to the blank black screen again can you get to a login prompt by typing Ctrl-Alt-F3?
This is happening to me for the second time in 6 months. Last (when I originally posted) I had no time so I just put a new Fedora installation. Other than that, I use this system on a daily basis without a single issue. Until now, again.
Removing rhgb quiet options it asks for the LUKS password, and after that it freezes like this:
I have wait up to 30 minutes and it does not go further. The fan sounds like it is doing something.
With ctrl alt F3 I can go to another console but not login, it is blank, only with the cursor blinking in the top left position, no text, and I cannot type anything.
Edit
You were right, it was doing something. After long time it print this:
You need to change the default target that systemd runs to try and get logged in.
In grub edit the kernel command line and add systemd.unit=multi-user.target.
This should boot up and put up at a login prompt in a console.
The GUI will not attempt to start up.
It was actually an enforced password reset, which was somehow preventing the system to boot normally. With the option you said, it allowed me to boot without GUI, and it asked me to change my password. Then I reboot, now it works fine.
For future reference (I see myself here in 3 months):
In the GRUB menu, press “e” to edit the boot command.
Add systemd.unit=multi-user.target at the end of the boot command (the longest line, I thing 3rd or 4th line).
Press “Ctrl-x” to reboot using this configuration.
Forcing password changes is considered bad security practice these days.
There is no evidence that forcing a password change makes you more secure.
In fact it is the opersite as it tends to make people pick weaker passwords.