public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] google-chrome-103.0.5060 - choose password for new keyring
Date: Thu, 7 Jul 2022 21:23:15 -0500	[thread overview]
Message-ID: <da6a87f5-f457-c160-c238-8c57c21cd12e@gmail.com> (raw)
In-Reply-To: <f2b40e88-b5d0-9960-e990-041086293a84@sys-concept.com>

thelma@sys-concept.com wrote:
> After update to new chrome browser "google-chrome-103.0.5060"
> A popup shows up:
>
> "choose password for new keyring"
>
> No explanation what is it, how to change it etc.  Is it needed?
>
> Was it discuss before?
>


I don't use Chrome but google found this.

https://forums.linuxmint.com/viewtopic.php?t=312289

This may help too.

https://superuser.com/questions/890150/completely-stop-gnome-keyring-popups

Does one of those help?  They seem to address the problem in slightly
different ways. 

Dale

:-)  :-) 


  reply	other threads:[~2022-07-08  2:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08  2:11 [gentoo-user] google-chrome-103.0.5060 - choose password for new keyring thelma
2022-07-08  2:23 ` Dale [this message]
2022-07-08  3:20   ` thelma
2022-07-08  3:28     ` Dale
2022-07-08  3:43       ` thelma
2022-07-08  3:50         ` Dale
2022-07-08  5:13           ` thelma
2022-07-08  6:44             ` Dale
2022-07-09 17:12               ` Wols Lists
2022-07-09 18:06                 ` [gentoo-user] " Martin Vaeth
2022-07-09 21:34                 ` [gentoo-user] " Neil Bothwick
2022-07-08  9:01             ` Dr Rainer Woitok
2022-07-08  9:48               ` John Covici
2022-07-08 13:34                 ` Matt Connell
2022-07-08 14:02                   ` Arve Barsnes
2022-07-08 16:20                     ` thelma
2022-07-08 17:12                       ` Neil Bothwick
2022-07-08 17:26                         ` thelma
2022-07-08 18:07                           ` Matt Connell
2022-07-09 17:02                       ` Dr Rainer Woitok
2022-07-08 14:02                   ` Matt Connell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=da6a87f5-f457-c160-c238-8c57c21cd12e@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox