Here’s the problem I’m facing. It doesn’t happen always, and I’ve noticed that typing my password slowly helps to avoid it (maybe some race condition?).
Anyway:
I reach SDDM on a fresh boot, I type my password and hit enter, everything turns black and no KDE splash screen appears.
Eventually I’m dropped into a TTY login prompt (or, when it takes longer, I just go there myself with Ctrl Alt Fsomething).
Again, it doesn’t happen always, but it tends to happen when I type my password somewhat quickly (it’s short and easy to type, so it happens most of the time). Typing it slowly seems to produce successful graphic logins almost every time.
I collected journalctl -b logs for:
- failed login with my user
- failed login with a test user created ad-hoc
- successful login with my user (after entering the password slowly)
Logs are here:
I focused on the sddm-helper part of the log files. In the files with “andrea” in the name (my user), refer to L2320+ (failed log) and L2369+ (successful log).
In the failed attempt, shortly after session opened for user andrea(uid=1000) by andrea(uid=0), there’s pam_unix(sddm:session): session closed for user andrea (i.e. I’m kicked out), which doesn’t happen in the successful case, of course.
The point is, I have no idea what leads to this. I see pretty much the same things being done in between, although with a slightly different order.
For example this user service I created appears immediately in the failed login case, but a while later in the successful attempt:
Jul 17 23:24:40 andromeda ssh-agent[1833]: SSH_AUTH_SOCK=/run/user/1000/ssh-agent.socket; export SSH_AUTH_SOCK;
Jul 17 23:24:40 andromeda ssh-agent[1833]: echo Agent pid 1833;
Any ideas/help?
Thanks 
