...on a few different machines, so it ain’t a coincidence.
It doesn’t K-P as it launches KDM, only as you log in.
Plus the Plymouth startup thingy is often quite reluctant to stop playing splash-screen.
If you Ctrl-Alt-F* & log in to a text console, you can kill KDM, then “/usr/bin/startx /usr/bin/startkde” on some (not all) machines to get a running KDE session.
Owe... kay. From a console:
sudo su -
cd /usr/bin
mv kdm kdm.removed
vi /etc/rc.local
12ji
/bin/plymouth --quit
sudo su - username /usr/bin/startx /usr/bin/startkde
sleep 5[Esc]:w![Enter]ZZ
It helps to delete the “nosplash” & “” keywords from the GRUB command you’re booting, add “plymouth:debug” then re-run grub-install, all of which gets Plymouth to settle down a bit more, plus slightly reduces the odds of being left with an always-K-P video card.
Yes, that logs you in (no password) as exactly one user, but for many workstations, that’s more than adequate.
It doesn’t K-P as it launches KDM, only as you log in.
Plus the Plymouth startup thingy is often quite reluctant to stop playing splash-screen.
If you Ctrl-Alt-F* & log in to a text console, you can kill KDM, then “/usr/bin/startx /usr/bin/startkde” on some (not all) machines to get a running KDE session.
Owe... kay. From a console:
sudo su -
cd /usr/bin
mv kdm kdm.removed
vi /etc/rc.local
12ji
/bin/plymouth --quit
sudo su - username /usr/bin/startx /usr/bin/startkde
sleep 5[Esc]:w![Enter]ZZ
It helps to delete the “nosplash” & “” keywords from the GRUB command you’re booting, add “plymouth:debug” then re-run grub-install, all of which gets Plymouth to settle down a bit more, plus slightly reduces the odds of being left with an always-K-P video card.
Yes, that logs you in (no password) as exactly one user, but for many workstations, that’s more than adequate.
Comments