LUKs login behaving odd | Plymouth + SimpleDRM

LUKs login behaving a little odd after update from Fedora 41 KDE to version 42. The name of the drive is shown below the login field where it wasn’t before and sometimes the screen flickers when I’m typing in my password. Luckily the function of my computer isn’t affected. It’s more an issue of fit and finish on a great distro. I’m not sure how to report this to team if they want to look into it. I’ve seen some other users with LUKs login issues. See attached images for issue and specs.

1 Like

Welcome to Fedora @brostoevsky22

Flickering might be the gpu driver while booting. This you might be able to change with a boot parameter.

The name of the disk seams to be new. You might be able to change how it looks like while giving the SSD a Label/Name.

I do not know what you use on KDE. On Gnome I use Gparted to check and change such things. It was just an observation of mine that, I guess the label, is blank on a default installation and then the UUID is appearing on disk names in the file manager.

1 Like

this also happened to me after upgrading to 42 on Gnome machine other than that everything else is normal

1 Like

The described behavior happens on my two AMD Ryzen laptops (Framework Laptop 16 (KDE) and ThinkPad T14 Gen 2 AMD (GNOME)), one with Fedora Workstation 42 and Fedora KDE Plasma Desktop, but does not happen on my ThinkPad T14 Gen 3 with an Intel CPU (KDE).

It seems I’m not the only one. This could be an AMD related issue. It’s not really a big deal, but I imagine that it’ll be fixed in the next update or two. Stuff seems to get fixed quickly around here.

1 Like

Thanks! After bouncing around the Ubuntu based universe (since 2020) I ended up over here on a whim and I quite like it. There was a lot of talk about Fedora KDE being top tier and they weren’t wrong.

2 Likes
2 Likes

I’m having a similar issue, on a non-AMD system. Fastfetch output below. The issue is that at startup the LUKS unlock screen prints a vertical line of garbage white dots (which looks a bit like some sort of distorted text) over the password entry screen. The screen does still work and I’m able to log in, but it looks kind of weird. I have set a kernel parameter plymouth.use-simpledrm=0 in order to go back to the old display manager system; that didn’t help. If I use the simpledrm, the screen at first displays without the weird line of text but rotated -90 degrees for a moment, before the screen rotates to a correct orientation and the weird line of white dots appears. I will try to take a picture of the login screen to give you a sense of what this looks like and update/add to the post accordingly.

Edit: here’s what the LUKS screen looks like now.


I am having the same issue. My system did not have the “please enter passphrase” text before updating, but it does now. No changes to Plymouth’s configuration remedied the issue.

To test, I performed clean installs of both Fedora Workstation 41 and 42 on a blank machine with an AMD Ryzen 7040 and integrated graphics. If the issue was strictly due to the changes with Plymouth, following the instructions in Changes/PlymouthUseSimpledrm - Fedora Project Wiki should reverse the behavior. Here are my results.



(Note: As a new user, I am limited to three embedded images, but the behavior of Fedora 42 [as seen in the third photo] is the same with a standard install as it is when SimpleDRM and hiDPI settings are changed to mimic Fedora 41. You’ll have to take my word on that.)

It appears that these changes with Plymouth are unrelated to those mentioned in the article. I have been unable to identify a cause, but considering that the updated splash screen is also accompanied by flickering and lag only in Fedora 42, and that the text is generally aesthetically unpleasant, I hope this can be fixed.

I will take a wild guess that it has something to do with the default bgrt Plymouth theme, considering that between F41 and F42, the Fedora logo’s position is significantly lowered, among the aforementioned issues. Maybe there were undocumented changes or an update?

1 Like

To anyone looking for a fix for this issue, @odi-3 has a solution here: