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?
--
Thelma
the...@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
On 7/7/22 20:23, Dale wrote:
the...@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
the...@sys-concept.com wrote:
> On 7/7/22 20:23, Dale wrote:
>> the...@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?
>>>
On 7/7/22 21:28, Dale wrote:
the...@sys-concept.com wrote:
On 7/7/22 20:23, Dale wrote:
the...@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 need
the...@sys-concept.com wrote:
> On 7/7/22 21:28, Dale wrote:
>> the...@sys-concept.com wrote:
>>> On 7/7/22 20:23, Dale wrote:
the...@sys-concept.com wrote:
> After update to new chrome browser "google-chrome-103.0.5060"
> A popup shows up:
>
> "choose password for new keyring"
On 7/7/22 21:50, Dale wrote:
the...@sys-concept.com wrote:
On 7/7/22 21:28, Dale wrote:
the...@sys-concept.com wrote:
On 7/7/22 20:23, Dale wrote:
the...@sys-concept.com wrote:
After update to new chrome browser "google-chrome-103.0.5060"
A popup shows up:
"choose password for new keyring"
the...@sys-concept.com wrote:
> On 7/7/22 21:50, Dale wrote:
>>
>>
>> You found a solution that works. That's great. Now you can get back to
>> doing more important things. ;-)
>>
>> Dale
>>
>> :-) :-)
>
> By upgrading one of my system, I've just noticed this behaviour is
> enforced (I think) b
Thelma,
On Thursday, 2022-07-07 23:13:47 -0600, the...@sys-concept.com wrote:
> ...
> By upgrading one of my system, I've just noticed this behaviour is enforced
> (I think) by new package that was pulled by emerge:
> [ebuild N] gnome-base/gnome-keyring-42.1 USE="pam ssh-agent (-selinux)
On Fri, 08 Jul 2022 05:01:17 -0400,
Dr Rainer Woitok wrote:
>
> Thelma,
>
> On Thursday, 2022-07-07 23:13:47 -0600, the...@sys-concept.com wrote:
>
> > ...
> > By upgrading one of my system, I've just noticed this behaviour is enforced
> > (I think) by new package that was pulled by emerge:
> >
> > > By upgrading one of my system, I've just noticed this behaviour is
> > > enforced (I think) by new package that was pulled by emerge:
> > > [ebuild N ] gnome-base/gnome-keyring-42.1 USE="pam ssh-agent
> > > (-selinux) -systemd -test"
> > > I don't use gnome, I use XFCE but I guess one
On Fri, 8 Jul 2022 at 15:34, Matt Connell wrote:
> > Should not this instruction say emerge --pretend --depclean rather
> > than --unmerge ?
>
> Since its pretended, the result is the same, ultimately.
>
Actually, none of them gives you any info about why a package is
installed, and --unmerge do
On Fri, 2022-07-08 at 09:34 -0400, Matt Connell wrote:
> > Should not this instruction say emerge --pretend --depclean rather
> > than --unmerge ?
>
> Since its pretended, the result is the same, ultimately.
I take this back. You're correct. depclean should show you what
packages depend on $pa
Thelma
On 7/8/22 08:02, Arve Barsnes wrote:
On Fri, 8 Jul 2022 at 15:34, Matt Connell wrote:
Should not this instruction say emerge --pretend --depclean rather
than --unmerge ?
Since its pretended, the result is the same, ultimately.
Actually, none of them gives you any info about why
On Fri, 8 Jul 2022 10:20:12 -0600, the...@sys-concept.com wrote:
> gnome-base/gnome-keyring-42.1 pulled in by:
> virtual/secret-service-0 requires gnome-base/gnome-keyring
>
> grep secret-service upgrade_07-07-22.txt
> [ebuild N] virtual/secret-service-0
>
> virtual/secret-service-0 pu
On 7/8/22 11:12, Neil Bothwick wrote:
On Fri, 8 Jul 2022 10:20:12 -0600, the...@sys-concept.com wrote:
gnome-base/gnome-keyring-42.1 pulled in by:
virtual/secret-service-0 requires gnome-base/gnome-keyring
grep secret-service upgrade_07-07-22.txt
[ebuild N] virtual/secret-service-0
On Fri, 2022-07-08 at 11:26 -0600, the...@sys-concept.com wrote:
> - if I enter password for the keyring, how to change it in the future.
The aforementioned seahorse will allow you to manage this. I'm certain
there's a CLI way to access it.
> - do I need to keep that password, will I be ask to u
Thelma,
On Friday, 2022-07-08 10:20:12 -0600, you wrote:
> ...
> app-crypt/libsecret-0.20.5-r3 pulled in by:
> app-crypt/gcr-3.41.0 requires >=app-crypt/libsecret-0.20
>
> And "app-crypt/gcr" was an upgrade.
This does not happen with the stable version 3.40.0 of "app-crypt/gcr",
only with
On 08/07/2022 07:44, Dale wrote:
the...@sys-concept.com wrote:
On 7/7/22 21:50, Dale wrote:
You found a solution that works. That's great. Now you can get back to
doing more important things. ;-)
Dale
:-) :-)
By upgrading one of my system, I've just noticed this behaviour is
enforced
On Sat, 9 Jul 2022 18:12:51 +0100, Wols Lists wrote:
> > Could disabling a USE flag remove that dependency? It may not be
> > google-chrome itself but something else it depends on. Using the
> > --tree option may help here. Masking the keyring package may force
> > emerge to shine some light on
20 matches
Mail list logo
