gyatpear

> please provide relevant logs, otherwise not actionable. I think logs could not tell much more. Here I paste some: ``` Sep 03 03:10:24 arch-on-mac sshd-session[718]: pam_systemd_home(sshd:auth): New sd-bus connection...

I have just discovered that every SSH login will make exactly one bad auth and good auth. It is just weird.

I found this issue is related to #17300 , while the unencrypted homedir get unlocked somehow with the plaintext password for logging in SSH. On my machine, the first failure...

OK. Then let me ask some questions further: 1. Will this "intended" behavior change in the future for smooth log in? Like if there is no encryption, just mount the...

Here I tried to create a user and do some tests: ``` homectl create --storage=subvolume --shell=/bin/zsh foobar ``` ### Output when user inactive #### userdbctl user foobar ``` User name:...

> the login should always be "smooth". You just should enter two different codepaths: either we can already unlock everything via PAM (i.e. in the non-ssh case), and your login...

> Seems no critical differences. Oh no I found `useFallback` is true when it is inactive. Is this means the stub shell `homectl` (a.k.a. `systemd-home-fallback-shell`) is doing wrong?

> > When a user logs in via SSH from inactive, zsh is invoked as `sh`: > > I prepped a fix for that in #34345. Can you give that...

> Ah! Interesting. Then I guess that fix indeed should fix your issue. Can you check? I pull the latest code and compiled, it worked for me. thx

After re-built the docker, as well as doing the same `clone-configure-make` on my host machine, many many times, I found the problem. It is because the date of `$(srcdir)/src/lexer.c` is...