Since installing LL on this laptop, every time I open up Chrome after starting up, have to enter password. And what is a 'keyring' anyway?
Am not sure if this is related, but most times I close lid to suspend, either I can't wake it up again and have to use power button to turn off and then on again after which a reboot, or it does respond to a key to wake up, but then goes throug the reboot routine. And the booting up is by far the slowest have ever encountered with Linux. LL used to always boot very fast, but not this time.
(Am using Lenovo T530)
Leaving the text field empty should solve the 'issue'.
THanks.
I don't understand what the keyring business is and don't like the idea of leaving things password free when I don't understand. I did install seahorse but there are dozens of entries under logins (some going back to my own sites from years ago and haven't visited for a very long time) and don't understand what is going on, so don't want to touch it (general principle).
I'll try the fix for the suspend later - the link with video. The first one with general instructions for settings doesn't help. I have the laptop set to suspend (never hibernate). Sometimes it seems to work, most of the time either it reboots when I hit a key or I have to hold the power button down to turn it off then turn it on again because otherwise nothing happens, it just stays asleep.
Follow-up question: is there any way just to get rid if this Keyring business and just have a normal setup, i.e. you use a password or fingerprint to open up the session and then after that no more prompting unless it's a system-related access.
(05-12-2017, 04:18 PM)CaperAsh link Wrote:Follow-up question: is there any way just to get rid if this Keyring business and just have a normal setup, i.e. you use a password or fingerprint to open up the session and then after that no more prompting unless it's a system-related access.
From the link: I assumed this would remove.. If I recall I hit continue 2x and haven't been prompted... But I may have removed...
(08-09-2014, 03:05 AM)Jerry link Wrote: [ -> ]thera, make sure Chrome is closed first. Then open a terminal and do:
Code:
rm ~/.local/share/keyrings/*
Now open Chrome, if it asks you for your password, do not enter one choose Continue each time and ignore any warnings.
Well, that worked too well. Now all passwords are forgotten and any site I go to that used to have it stored I have to reset the password unless I can guess. That's what I meant about 'not understanding keyring'. I did google it but nowhere could read anything intelligible. I don't understand why this was happening only with this new installation though and no other.
Just for all who still have this issue, adjust the launcher/icon with:
--password-store=basic
This makes chrome of chromium use the default basic key shipped with it. The other trick was to uninstall gnome-keyring but it will keep getting reinstalled by updates so this is the best solution I have found. It would be better to have a startup script made and point the launcher/icon to it so updates to chrome or chromium will not change how it is launched. Here is a sample chromium script.
#!/bin/bash
chromium-browser --password-store=basic %U
Thank you. I just got a new (and last new one for many years hopefully) laptop and installed LL on it. Yesterday I installed a fingerprint recognition capability and I think this is occasionally messing up the login scripts because one time after a reboot it didn't recognise the swipe but went ahead and logged in, I didn't input a password manually which usually is prompted for if the fingerprint swipe doesn't pass muster. Then, when I opened Chrome, I got the keyring prompt. Before that, it never happened.
And cannot be sure, but I think this happened with the older laptop too (both are Thinkpads).
But if/when this happens again on the new machine, I'll be sure to try this suggestion.
Thank you very much.
To Supergamer: could you spell out a little bit more clearly what to do, i.e. the steps to implement your suggestion. I thought at first it was a password to input when prompted but now not so sure.
