The machine has running well (usually one shutdown/boot cycle per day) but this morning when it boots it can only reach command line login prompt, it seems it has almost reached the desktop as the mouse cursor flashed for a second then I’m thrown back to the cmd line login prompt.
Machine info: TW, Plasma 5 wayland, OS updated 2-3 days ago,
Nothing unusual in
journalctl -b -p err
, just a few benign errors that have been there for months.
2. Tried several snapshots even back to a few days ago before the last OS update, same boot result.
3. Tried recovery mode, same boot result.
4. Don’t remember doing anything particular to the machine during the last normal boot. If anything, yesterday I had this "The screen locker is broken and unlocking is impossible, use
loginctl unlock-session 5
,…Ctrl+D, Ctrl+Alt+F2 to get back" message. I followed the message but it failed at a certain step so I had to “Ctrl+Alt+Del” to reboot, but it boot fine, and that’s the last normal session.
5. I use autologin for my account.
My guess is that some config/settings in my home folder is causing the issue, but I have no idea where to start to solve this.
Had you previously booted OK on kernel 5.19.1, then dup’d to include 5.19.2 yesterday?
If you login as a virgin test user, is all good?
If you try an X11 session instead of Wayland, is it OK?
If you try an IceWM session, is it OK?
If while logged out of X, you delete the content of ~/.cache/, does it help when trying to login to your usual session?
Does removing amdgpu-pro drivers help?
Most, but not all, of KDE/Plasma’s settings files in ~/.config/ are obvious who they belong to. You could try selective deleting there while not logged into Plasma. Various settings will be lost according to whatever you delete.