Chrome asks for password/keyring every time

[supergamer]

Create a text file (For this script I would call it Chromium_Start) somewhere on the system, you can place this anywhere but putting it into the /usr/scripts/ folder requires sudo on thunar to either copy or create the script. Now copy this code

Code:

#!/bin/bash

chromium-browser --password-store=basic %U

and put it into the text file and save. Make sure you make the the file you created executable and copy/move the new script to where you want to save it. Now go to your icon on your desktop or taskbar and right click on it and select properties then select edit. You should be able to see the command where you can adjust it and it should be, for chromium, chromium-browser %U. Just hit the browse and point it to the new script you created. If you put it in the /usr/scripts/ and named it Chromium_Start then it should look like /usr/script/Chromium_Start on where the command is. My personal script is

Code:

#!/bin/bash


bleachbit -c chromium.*

firejail chromium-browser --incognito --password-store=basic %U

I prefer to seperate the commands, you could use && or ; but this seems to work fine.

[CaperAsh]

Thank you. I disabled the fingerprint utilities and now no problems. But I will try this later. First time around unable to make executable file, which reminds me have been having problems with permissions in 2nd HD on the computer. It's only Day 2 after installation. Also, have poor skills with niggly areas like this. Thanks again.

[supergamer]

I am uploading a simple script that should start either chromium or google chrome when ran. If you have both installed it will open both though so you might want to adjust the script. Save the file. right click on it and go to permissions and make sure the check to make executable is checked. Move the file to wherever you want and point the right click on your browser icon you normally use and go to properties and point the command to this script. You can check to make sure this script works by opening a terminal in the folder you have this saved and typing:

Code:

./Browser_Start

This is what the code looks like:

Code:

#!/bin/bash

google-chrome --password-store=basic %U

chromium-browser --password-store=basic %U

Just rename the file by taking the .txt extension off of it.

Hopefully this makes things easier if you want to try.

[CaperAsh]

Thank you again! Since last entry I went into fstab to get my HD to open properly (system is on an SSD). It seems to have resolved many of the permissions issues which changing a few designations in Disks program hadn't resolved.


Whether this made a difference or not to what I tried earlier, I think what I did wrong first time around was to save the file as .txt and then when going into Properties couldn't select the 'make file executable' box.


Just ignorance on my part about saving the file without an extension.


I adjusted the text to just open Chrome (I prefer it because Chromium has difficulties playing certain types of flash content on sites I often visit, otherwise wouldn't bother) and it is great.


Thanks again.


(Now if I try to reinstall fingerprint stuff and have this problem again with Chrome, I should be okay. I don't need the fingerprint thing but since the computer has one I wanted to set it up. Seems better without it. One less thing to complexify/screw up!)


Resolved!

[supergamer]

I cannot comment on you not having issues with reinstalling things but this script takes the update to out of the question. It basically separates the startup of the browser from the the default chromium/google-chrome.desktop in the /usr/share/applications. So anytime you update chromium/google-chrome you would not have to readjust the launcher to what you did before to stop the gnome-keyring issue. I hope this fixes the issue. This also fixes the issue with bleachbit cleaning chromium/google-chrome by forcing it to use the default keyring and shutting down completely if you use that program.