I just managed to get custom wallpaper plugins working and updated the ArchWiki. 
2 Likes
OK, the consensus here is that I have a Plymouth configuration issue… Thanks to all for the feedback
I’m guessing that my next step would be to investigate what is in my /etc/plymouth/plymouthd.conf?
My install is quite old now so some odd setting that I picked up certainly sounds believable. I’ve already spent way more time thinking about this minor cosmetic issue than I wanted to so if nothing jumps out at me in the config, I’ll just uninstall Plymouth and move on, no big deal, but wish me luck 
Since plymouth seems to have been my issue with PLM since the beginning, I gave up and uninstalled the plymouth packages, updated my /etc/kernel/cmdline and ran sudo reinstall-kernels. Problem solved!
5 Likes
dracut: there is allegedly a third-party module called dracut-bootsplash, though I am not familiar
mkinitcpio: natively supports building a static bootsplash directly into your initramfs via a flag in your config file
You have options if you absolutely have to have a bootsplash, though mkinitcpio does not support animated boot splash and I cannot speak on how dracut handles it. At the very least worth looking into. Godspeed. 
1 Like
Thanks for reaching out and welcome to our community!
EOS defaults to dracut and systemd-boot when installing, also no bootsplash by default, wall of text comes standard
I installed plymouth ages ago and it worked great until my migration from sddm to PLM, but after much research and tinkering, I couldn’t figure it out, but no worries. Most folks around here surely enjoy seeing the text scroll by, so who am I to argue, so all good
I have a recent GNOME install on which plymouth is working (GDM of course) but the Dell logo is teeny tiny and I’m not happy with the way it looks so I’ll probably uninstall plymouth there too, just as well…
The irony around this is that bootsplashes can show you the bootlogs if you usually just press Esc. I think for some, the first inkling of an issue, or something awry, will be in that boot log that scrolls by. It might be something as simple as a network node not being connected, or a drive or hardware fault. Plymouth and similar plugins stemmed from a time when boot loading took much longer, SSDs and NVME’s have a lot to answer for 
1 Like
Why the need for hiding of boot logs behind a splash image or boot image? Is it for pure ascetic reasons? Or is there something else at play over here?
1 Like
When I used to do, it was because I thought it looked better. I don’t bother these days as I like the wall of text. It looks more geeky 
4 Likes
I’m with you…it doesn’t really matter to me, though a change of pace every now and then :0
1 Like
Considering creating a “Desktop_Test” account to try out different desktops without touching the configuration of my main account (learned multiple desktops on one account can be a bad idea). So, given that Plasma Login Manager is just a fork of SDDM, should I expect I can load another desktop from it or is the baked in Plasma integration going to mess that up somehow?
I think you can from what I’ve read (I was asking myself the same question just the other day) but haven’t tried it out yet.
Just be aware that you will pull in other packages for each DE so you will end up with multiple terminals etc So maybe if possible try them in a VM first
1 Like
VM might be the better way at that.
2 Likes
Yer than you can decide what you want to go with and figure out your setup without having to worry about messing anything up
Having being following this conversation about Plasma-Login-Manager keenly. Still have a few doubts?
Firstly can Plasma-login-manager run rootless or like SDDM it is a display manager that runs as root?
Secondly can Plasma Login Manager launch the display server, i.e. X or Wayland, rootless? SDDM has this capability.
It’s a forked version of SDDM, it can do anything up to the fork that SDDM can do. And since SDDM is essentially dead…you do the math.
I mean, it’s possible they took out features…but why would they?
1 Like
For those who want to disable blur from plasma-login-manager:
sudo perl -pi -e ‘s/BlurScreenBridge/NoBlurScreenBrdg/g’ /usr/lib/plasma-login-greeter
reboot
Ich hatte gerade das Problem das Plasma Login Manager mir nur noch den Cursor zeigte. Auch nach mehreren Versuchen änderte sich daran nichts.
Vorher funktionierte das einwandfrei.
Bin jetzt auf sddm zurück und da lief alles einwandfrei.
Jemand eine Idee woran das liegen könnte?
- remove older plasmalogin:
sudo rm /etc/plasmalogin.conf
sudo rm -r /usr/share/plasmalogin
sudo rm -r /var/lib/plasmalogin
rm ~/.local/share/plasmalogin
- install plasma_login-manager:
sudo pacman -S plasma-login-manager
- disable sddm:
sudo systemctl disable sddm
- enable plasma-login:
sudo systemctl enable plasmalogin
5.remove sddm:
sudo pacman -R sddm-kcm sddm
reboot
Now everything should be OK. I don’t think it would be too much of an effort if you posted in English.
Oh. Sorry. I was in a hurry earlier.
Thank you so much, that worked.
I’m not sure if this has been said. But plasma login manager does not respond after waking up from sleep if you have kde wallet active at the moment. Theoretically you shall unlock it with a dialog, but first you have to login. You can’t login because you can’t unlock the wallet.
The solution is restart the machine and disable kde wallet, or , don’t call the login manager after sleep.