You have to enable this feature in Privacy settings. You can get there by going into Chrome settings:
Enable saving passwords
Click the Chrome menu icon (the three dots on the top right).
Click Settings
Click Show advance settings (new the bottom of the page)
(Under Privacy - Passwords and fo...
At me it is all configured had already been. If click All cockies and site data cookies there, so it does not delete cookies when closing Google Chrome
@Novah The cookies isn't your issue. I put the steps referring to cookies because of your reference to it in the comments. You issue should be resolved by following the steps for passwords in the answer. Did those steps work?
@Novah In the password section, click Manage Passwords then checkmark Auto Sign-in. Also in the manage password section, scroll to the bottom and make sure Never Saved isn't set for the site you're having problems with.
@Novah I appended a section to the answer for bringing Chrome back to it's default settings. Can you tell me if that resolves the password saving issue? Also, can you mention if this happens on all sites or certain sites.
@Novah I was asking if chrome created a new ~/.config/google-chrome directory after you moved the old one. Also were you sure to have been out of chrome when you renamed the directory?
Where you sure chrome wasn't running?
By the way, if it appears it's taking me a long time to respond, I might not know that you have typed. You can use the @L.D.James as the first in the message line to ensure I get an audible notification.
@L.D.James I completely deleted Google Chrome from the system (sudo apt-get --purge remove google-chrome-stable, and then delete the directory). Then I install it again
The important thing was to have the profile removed... which removing or renaming ~/.config/google-chrome would have done. I believe it's clear now, that a new ~/.config/google-chrome was created. I would like to mention that I was trying to be exact because I'm trying to reproduce the steps on a computer in my shop.
I'm researching the details. Will advise you when I see something else to check. It might take a while.
@Novah First I'll mention that I understand if it takes a long time to respond. I don't expect for you to be at the console ad all times. Just as I'll be doing other things in between research.
I'm looking at an example where the problem was with the Google sync settings. Do you have your Chrome set to sync with Google?
@L.D.James I have synchronization has been configured, but you have every time you start Ubuntu sign-in the Google account in Google Chrome to sync that worked
1) Disconnect your Google link Settings -> People -> Select each entry and remove (After they are all removed you'll have a default one called Person 1 or Person 2)
2) Now go to this site: http://2.chromium-test1.appspot.com/testing/psl-matching/login -> you can use something like testuser/testpass for login and password.
3) Save the password... don't logout... close the broswer.
4) Open the browser again to the site. See if it's remembered.
Okay so it appears the default outside Google works. So the next step is to check what is happening with Google. There are two things that might matter. First use Chrome's Signin option: Settings -> Signin
@Novah Backup your keyring the same way you backed up your Google settings before. The keyring is in ~/.local/share/keyrings
Move the most recent entry to the filename with a *.bak extension.
Then logout. The system will prompt you for passwords for everything you use. It'll also prompt you for the Google webpage passwords. Hopefully this is the key.
If it's not, you can restore the key you backed up and have all your other passwords (for other items) back.
Let me know if you have any questions with the steps. I tested it. I had to lookup my password for various sites to get back in.
@L.D.James I repeated the steps and when starting Google chrome has been prompted to create a password for the keyrings. output ls -lta: итого 28 drwx------ 2 novah novah 4096 Сен 9 20:20 . -rw------- 1 novah novah 15883 Сен 9 20:20 Связка_ключей_по_умолчанию.keyring -rw-rw-r-- 1 novah novah 49 Сен 9 20:18 default drwx------ 33 novah novah 4096 Сен 9 20:17 ..
@L.D.James I renamed and launched Google Chrome, and he has been prompted to create a password for the keyrings and create new file Связка_ключей_по_умолчанию.keyring
That was a different direction. It might work. You can see if it's working now. If not, I'll give you the steps that I did. I'll wait while you check and see if the issue is resolved.
@L.D.James I performed these steps: 1) I sign-in on the test site 2) Close Google Chrome 3) Lock keyrings 4) Launch Google Chrome 5) Enter password 6) and the need to re-login
@L.D.James If you have more no idea how to solve this problem then probably dick with that Google Chrome. I go to the Opera, it is partially better in a partially worse but a good browser. Probably the only way to solve this problem is to reinstall Ubuntu))
@Novah Excuse the time inbetween responding. I was out of the shop.
I didn't think of asking you to try a different browser. Does this problem happen with other browsers?
I understand if you decide to give up. If it works with a different browser, you could revisit the Chrome problem in a more leisure manner. I'm sure you're frustrated, but I would explore for a long time to try to figure out the culprit.
When you get a chance, check Opera, Firefox, and Chromium.
For Google Chrome:
Deleting ~/.config/google-chrome (where ~ is your home directory) should be sufficient. Why don't you try it and see? (Of course, this will delete all your bookmarks too.)
If that's not sufficient, you may want to also remove Google Chrome from the Terminal using the sudo apt...
I've searched the net for such information and found different command lines, like these ones:
sudo apt-get remove application
sudo apt-get remove application*
sudo apt-get remove --purge application
sudo apt-get remove --purge application*
sudo apt-get purge application
sudo apt-get purge app...
@DavidCole-GrammarPolice I completely delete the directory ~/.config/google-chrome Google Chrome from the system (sudo apt-get --purge remove google-chrome-stable, and then delete the directory). Then I install it again
Yes. The latest... The Chrome install automatically updates with their releases.
While I know you have it covered, I was checking to verify your install method... just a detail trying to see what is different about your environment that's causing the problem.
@DavidCole-GrammarPolice He appears to have done everything short of reinstalling Ubuntu.
@Novah I understand you've been going over this for a long time. I don't mind hours between messages, again the @username will notify me. When you get a chance, try setting up a new account on your computer. Then see if Chrome works on that account. If it does that can provide something smoother than a complete Ubuntu reinstall.
Also, if that works, you can move your /home/yourID to /home/yourID.old, then make a new directory for /home/yourID. Then log in and systematically pull your data from the /home/yourID.old. This is something I have done a few times over the years.
I can resend those steps in a numbered list.
I also have a second account on my system to test the difference between something I'm having a problem with and a different loginID.
4) If it works, from that account go to "/home" a) Rename "/home/account1" to "/home/account1.str" b) Make a new home directory for account1: "sudo mkdir /home/account1" c) "sudo chown -R account1:account1 /home/account1
5) Log in as account1 (your regular account will be totally clean).
6) Test and see if the problem is removed
7) Systematically grap your files from "/home/account1.str"
@L.D.James Google Chrome is working properly and does not require a password from the keychain, but if I block Keychain, there is this problem with authorization
It appears that your other account, uid 1000, has the folder locked. Try rebooting the computer and be careful not to login using account1... only account2.
@andrzej1_1 The the problem happen with Chromium and Firefox?
Yes. I was trying to give you the option of fixing your original account. That could work also. You'd just have to get used to a new login name.
The problem is probably that something was being mounted automatically on bootup by your account1. If you as conformable working with it the way it is, cool.
Just pop in a question here and there if you get stuck fixing the new account.
Discussion between Novah and L. D. James
Discussion between Novah and L. D. James