You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the "Online Accounts" phase of the first-logon onboarding, a user can select a Google account, but if they have a security token such as a YubiKey set up in their Google account as a 2FA, the login process hangs after the user inputs their password.
This is exceedingly bad and I have suggestions on how to handle it:
Fix the login process or remove Google accounts from the list of options since you clearly have no intent of fully supporting them.
Give the user some kind of notice that logging in with a security token is not possible.
Simply having the process hang is a bad experience and makes Linux newbies go "oh, good thing I chose dual boot."
If one right-clicks the window and reloads, after a few attempts the 2FA page will load. However, the security key is not recognized because it seems the built-in Gnautilis browser does not have access to HID devices.
Secondarily, not properly supporting 2FA in 2025 is unacceptable. This is likely due to use of an excessively old version of the signon-ui library.
The text was updated successfully, but these errors were encountered:
During the "Online Accounts" phase of the first-logon onboarding, a user can select a Google account, but if they have a security token such as a YubiKey set up in their Google account as a 2FA, the login process hangs after the user inputs their password.
This is exceedingly bad and I have suggestions on how to handle it:
Simply having the process hang is a bad experience and makes Linux newbies go "oh, good thing I chose dual boot."
If one right-clicks the window and reloads, after a few attempts the 2FA page will load. However, the security key is not recognized because it seems the built-in Gnautilis browser does not have access to HID devices.
Secondarily, not properly supporting 2FA in 2025 is unacceptable. This is likely due to use of an excessively old version of the signon-ui library.
The text was updated successfully, but these errors were encountered: