screenlocker cannot unlock, requiring use of TTY to escape.

[Maxwelldoug]

Issue Description

An undefined error occurs when attempting to unlock a locked screen in the current image as provided by #23 (I acknowledge I am jumping the gun a bit as it hasn't even been merged but I expect it will be and want to log this while my research into it is still fresh in mind.)

Switching to TTY4, logging in as the same user as the session, and running loginctl unlock-session 3 bypasses this behavior and causes an unlock when you return to TTY2, so this issue is somewhere in Plasma/screenlocker.

Steps to Reproduce

Wait for Screen Lock
Attempt to login
unknown error
loginctl in a tty works

On what version of Vanilla OS this happens?

Unreleased

Additional Information

On second thought, This also occurs to the empty black screen on the current mainline image but I see no reason you would stay in that for long enough for it to autolock.

[Maxwelldoug]

This is the only bug that I have put in that persistently refuses to be solved. However, the reason is not technical - I have a solution - but rather ideological.

I fundementally resist disabling the shadow behaviour, but the only way to get the screen locker to work is to add the user it runs under to the shadow group. Add the user. To the shadow group.

[Maxwelldoug]

we could set kscreenlocker_greet as setuid root but that's almost as bad.

[Maxwelldoug]

No, hold on, unix_chkpwd should still work if the user to be authenticated is the same user calling it. Something's up here.

[Maxwelldoug]

Please disregard my last 3 comments - setuid was missing from unix_chkpwd for some reason. I am currently testing if this is sufficient to fix kscreenlocker.

[Maxwelldoug]

Solved in Maxwelldoug/kattleya-image:dev

[Maxwelldoug]

This is fixed by #27