Re: MX-18 RC1 Feedback
Posted: Tue Dec 18, 2018 8:55 am
I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)
Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/
On first opening with Google Chrome, I am always asked for the keyring password.Eadwine Rose wrote: Tue Dec 18, 2018 8:55 am I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)
When you log-in the first time with your normal username and password, during the log-in process a new login-keyring is (shall be) generated automatically by "libpam-gnomekeyring", if not already existing. As protecting password used for this keyring the user's password is used. After login this keyring is automatically unlocked. You can check this by doing the following:j2mcgreg wrote: Mon Dec 17, 2018 10:24 pm I'm getting this in Chrome "Enter password to unlock your login keyring", which would be fine except there was no initial prompt to set up a password.
Code: Select all
rm ~/.local/share/keyrings/*
Not here.. *shrug*richb wrote: Tue Dec 18, 2018 9:05 amOn first opening with Google Chrome, I am always asked for the keyring password.Eadwine Rose wrote: Tue Dec 18, 2018 8:55 am I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)
B/c you used an empty password for the keyring, I assume. (Which we shall not advocate to the user, but instead use (and fix if not working) a more secure solution)Eadwine Rose wrote: Tue Dec 18, 2018 8:55 am I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)
Immediately after the reinstall, chromium worked fine with no appearance of the key ring prompt. However, it did reappear after these two packages:j2mcgreg wrote: Mon Dec 17, 2018 11:24 pm dolphin_oracle wrote:
It wouldn't accept it. In any event, I reinstalled RC1 and chose Chromium instead of Chrome and declined Google's offer to sync all my devices. I want to see if the problem recurs.it should be just your user password.
Code: Select all
ecryptfs-utils (111-4), and, libecryptfs1 (111-4)
Would enabling "Secret Storage Service GNOME-keyring" in autostart, as mentioned in the prvious post solve password prompt issue.j2mcgreg wrote: Tue Dec 18, 2018 10:16 amImmediately after the reinstall, chromium worked fine with no appearance of the key ring prompt. However, it did reappear after these two packages:j2mcgreg wrote: Mon Dec 17, 2018 11:24 pm dolphin_oracle wrote:
It wouldn't accept it. In any event, I reinstalled RC1 and chose Chromium instead of Chrome and declined Google's offer to sync all my devices. I want to see if the problem recurs.it should be just your user password.
were installed after an update. So far, the prompt is accepting my normal password.Code: Select all
ecryptfs-utils (111-4), and, libecryptfs1 (111-4)
The options are default, enable, disable with default as installed choice.Migrate passwords to "Login Data"
Performs a one-off irreversible migration of passwords from the gnome-keyring or kwallet into the profile directory. – Linux