While the title overall explains this, to go slightly more in-depth, the expectation is the device to be overall unlocked and usable on boot due to auto-login, with changing some settings or opening specific applications requiring a password to do so. However, when the device is booted the keyring is not unlocked which seems to be required to open either of the two primary applications used (Web browser - Vivaldi, email tool - Proton Mail).
More recently, this has further bugged wherein before an application is even opened keyring unlock is prompted, and a new white screen prompting it AGAIN is also opened, with both seemingly requiring fulfillment BEFORE the device can open applications.
This renders auto-login useless, thus the bug report as the native problem reporting application does not allow creation of a bug report from there.
and changes the user password. When there is only 1 user, said user (to my knowledge) usually runs with only perms of a “user” but by using their password can elevate to admin (via sudo). By this process, my understanding is changing the user password would then change the password to elevate to admin to the same thing - which would leave admin unprotected entirely if removed.
Is system password for sudo simply something truly tied to the system without a UI element to change (locked on install), or is there a screen I’m missing to uncheck making the password for sole user be the same as for system to then safely remove user password without removing admin password?
Is there another way to change the keyring password (preferably with gui)? The application seems to be from an unverified dev which is a tad strange.
Surely Gnome has a native way to manage a “keyring” if it introduces such, otherwise there is little point in including it.
I make a point to ALWAYS use gui when attempting for basic user functionality - this does give a good starting point for me to make a few needed issue/bug reports though, thanks!
While this tool is a solution, since auto-login does not actually auto-login the user without a blank keyring this leads to a feature request for auto-login to “blank” keyring password when enabled and set to user password when re-enabled.
It also paves the way for issue reports (from more in-depth research) on the multiple authentication required prompts as the white seemingly outdated prompts seem to result from having at least 1 online account signed into - meaning they are trying to call an outdated version of this screen at the same time the modern version is already called.