| 1 |
On 7/7/22 21:50, Dale wrote: |
| 2 |
> thelma@×××××××××××.com wrote: |
| 3 |
>> On 7/7/22 21:28, Dale wrote: |
| 4 |
>>> thelma@×××××××××××.com wrote: |
| 5 |
>>>> On 7/7/22 20:23, Dale wrote: |
| 6 |
>>>>> thelma@×××××××××××.com wrote: |
| 7 |
>>>>>> After update to new chrome browser "google-chrome-103.0.5060" |
| 8 |
>>>>>> A popup shows up: |
| 9 |
>>>>>> |
| 10 |
>>>>>> "choose password for new keyring" |
| 11 |
>>>>>> |
| 12 |
>>>>>> No explanation what is it, how to change it etc. Is it needed? |
| 13 |
>>>>>> |
| 14 |
>>>>>> Was it discuss before? |
| 15 |
>>>>>> |
| 16 |
>>>>> |
| 17 |
>>>>> |
| 18 |
>>>>> I don't use Chrome but google found this. |
| 19 |
>>>>> |
| 20 |
>>>>> https://forums.linuxmint.com/viewtopic.php?t=312289 |
| 21 |
>>>>> |
| 22 |
>>>>> This may help too. |
| 23 |
>>>>> |
| 24 |
>>>>> https://superuser.com/questions/890150/completely-stop-gnome-keyring-popups |
| 25 |
>>>>> |
| 26 |
>>>>> |
| 27 |
>>>>> |
| 28 |
>>>>> Does one of those help? They seem to address the problem in slightly |
| 29 |
>>>>> different ways. |
| 30 |
>>>>> |
| 31 |
>>>>> Dale |
| 32 |
>>>>> |
| 33 |
>>>>> :-) :-) |
| 34 |
>>>> |
| 35 |
>>>> Thanks, there is a lot of information how to by-pass it but very |
| 36 |
>>>> little explanation which application request it or why is it there. |
| 37 |
>>>> |
| 38 |
>>>> |
| 39 |
>>> |
| 40 |
>>> |
| 41 |
>>> One thing I read makes it sound like it is for a built in password |
| 42 |
>>> remembering tool. I know Firefox and Seamonkey has the same but I |
| 43 |
>>> disable those since I use BitWarden anyway. One would think there would |
| 44 |
>>> be a setting in preferences to just disable all that. I suspect few use |
| 45 |
>>> them given the popularity of LastPass, BitWarden and other tools that |
| 46 |
>>> are much more secure and portable. Maybe looking for a password tool |
| 47 |
>>> setting would help. I tried Chrome ages ago, didn't like it at all. |
| 48 |
>>> That was several years ago so I'm clueless on it now. Just thought |
| 49 |
>>> those suggestions might help. |
| 50 |
>>> |
| 51 |
>>> Dale |
| 52 |
>>> |
| 53 |
>>> :-) :-) |
| 54 |
>> |
| 55 |
>> Starting chrome with "--password-store=basic" solved the problem. |
| 56 |
>> |
| 57 |
>> |
| 58 |
>> |
| 59 |
> |
| 60 |
> |
| 61 |
> You found a solution that works. That's great. Now you can get back to |
| 62 |
> doing more important things. ;-) |
| 63 |
> |
| 64 |
> Dale |
| 65 |
> |
| 66 |
> :-) :-) |
| 67 |
|
| 68 |
By upgrading one of my system, I've just noticed this behaviour is enforced (I think) by new package that was pulled by emerge: |
| 69 |
[ebuild N ] gnome-base/gnome-keyring-42.1 USE="pam ssh-agent (-selinux) -systemd -test" |
| 70 |
Upgrading just "chrome" did not ask me for any keyring password. |
| 71 |
|
| 72 |
I don't use gnome, I use XFCE but I guess one of the package pull this as a dependency. |
Archives