LXDE Forums

I installed LXQt on Fedora 27. On a 32-bit laptop, every time I login to LXQt, a window appears indicating that a keyring did not unlock and it prompts me for the password. I can either submit the password or click Cancel and either will make the box disappear.

Does anyone know how to remedy this, so I'm not prompted for the password at each login?

Thank you,

it's a security feature.

which password do you have to enter? normal user password or sth else?
you probably also enabled autologin?
chances are the box will go away when you disable autologin.

that said, there used to be a trick, to provide an empty password to the keyring when first prompted. not sure if it still works.

Normal user password.

As for enabling auto login, this began immediately at the first LXQt login after installation, so I can only guess that if it is enabled, it was done by default during the package installation.

I have two other desktop environments installed as well and neither prompts for the password the second time to unlock a keyring.

edward wrote:prompts for the password the second time to unlock a keyring.

that was the keyword i was looking for.
please try to identify which program is asking for the password. is it gnome-keyring, or maybe lxde have their own version?
and does it also say what it wants that password for? email client? chrom{e,ium} browser?

I don't know what program is prompting for the password to unlock the keyring, because the window appears a few seconds after the LXQt desktop first appears. I don't have to launch anything (e-mail, browser).

Lightdm is the desktop manager installed.

1. System boots up to Lightdm login screen.
2. Select LXQt and input password.
3. LXQt desktop loads in. A few seconds after the LXQt desktop appears, the window displays prompting for the password to unlock the keyring.

I found a solution.

I renamed the folder keyrings, located in home/<username>/.local/share/, to keyrings.old and rebooted.

The window/prompt to input the password to unlock the keyring has not appeared after this and it automatically created a new /home/<username>/.local/share/keyrings folder.

I'm guessing there was an issue with the files in the original keyrings folder.

edward wrote:I/m guessing there was an issue with the files in the original keyrings folder.

no.
i'll say it again: this is a feature, not something problematic.
it makes sense to secure sensitive stuff with passwords.
it makes sense to actually enter these passwords - either on-demand, or once during login.

nevertheless, i congratulate you for "fixing" it.