I have been migrating from SLED 15 to F32. I have /home on a RAID1 set and can see it from F32. Got the F32 install done and have applied updates to it. And I pulled in KUser.
So still with root, I defined my ID (as it was with SLED 15) and told the system do not create a /home directory (so it saw and used my old /home/uid). So far so good.
Dolphin (?) I selected my directory and set it all to be owned by my id and “users” (which was true of SLED 15).
And I set my password and then logged out of root.
So the logon screen comes up (and since I did a KDE install, I’m assuming a KDM manager) with my userid, and so I put in the password. It rejected it. Ok, must of fat fingered that so back to root, slam the password and back to user…
So put in the password and it accepts it. 10 minutes later I still have a mouse pointer, some disk activity of some kind and I do not have a KDE environment.
Could someone point me in the right direction? What could I have mangled that F32 can see /home using the raid1, mount shows it mounted to /home, etc. But when I attempt to long on the userid, I do not get into a KDE environment (actually I just have a black screen with a mouse and you can’t type on/or in it, and I can’t get to a text console either).
I know enough to be dangerous. I think I’ve proven this a few times now.