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
When investigating an issue that only occurs on ostree-based images we noticed that logging in as admin, logging out, then logging in as a non-privileged user ("scruffy") is enough to trigger the issue, which is caused by a pending sudo operation. Removing the "admin" login part and the problem disappears.
My theory is that the login page is somehow changing its local storage behaviour of remember the "should be root" flag for the case where we are using the -ws container to connect to the host via ssh.
When investigating an issue that only occurs on ostree-based images we noticed that logging in as admin, logging out, then logging in as a non-privileged user ("scruffy") is enough to trigger the issue, which is caused by a pending sudo operation. Removing the "admin" login part and the problem disappears.
My theory is that the login page is somehow changing its local storage behaviour of remember the "should be root" flag for the case where we are using the -ws container to connect to the host via ssh.
cc @jelly
The text was updated successfully, but these errors were encountered: