hello, everyone!

this is my first post here and also my first post on a foreign website.

i encounter a problem when using google-autenticator
it seems that it doesn't work with locking screen

if i log in the computer, a verification code will be asked for

once i logged in, and if the auto-locking mechanism was enabled, after awhile, the system was auto-locked, then i will never be able to log in again? no verification code was asked for, only password, but keying in password doesn't get system unlocked?

has anybody experienced the same problems before?

any helps or explanations will be greatly appreciated.

Welcome to LQ!

what system is it? Are you in a remote location?


Do you own the system? Or it is someone else?

This definitely sounds like a "Catch 22" problem that the system's owners need to address!

From (DISTANT!) memory I believe there was a way for systems that didn't prompt specifically for the authentication code, and I think the mechanism was to type the 6 digits of the authentication code as the first part of the password field.

No matter if there's a "way around it" or not, this issue is a show-stopper usability problem for users as it stands now. If the system's owners did think of it and did provide a way, they didn't convey that knowledge to their users!

sorry for my non-instant reply (i was blocked behind a great wall...)

my system is ubuntu 17.10 with kernel 4.13.0

i found that sddm or gdm or lightdm and locking screen
are different components and works differently.

now i have disabled my locking mechanism and 2FA authentication

linux PAM is complicated to master instantly...

sometimes even myself was locked out and was
unable to log in and had to revert to recovery mode.

thanks for all you guys response!