From: thelma@sys-concept.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] google-chrome-103.0.5060 - choose password for new keyring
Date: Fri, 8 Jul 2022 10:20:12 -0600 [thread overview]
Message-ID: <20de78a3-ee38-35b0-2457-8fd0ab326e68@sys-concept.com> (raw)
In-Reply-To: <CAJjrzcVNc=o15yy-4a2Nhm=MM69pV_wOTcxOxH8SiVDKYpGHdA@mail.gmail.com>
Thelma
On 7/8/22 08:02, Arve Barsnes wrote:
> On Fri, 8 Jul 2022 at 15:34, Matt Connell <matt@connell.tech> 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 doesn't even try to check. Without --pretend
> it's perfectly happy to let you shoot yourself in the foot. What you
> actually need to get portage to tell you what requires the package in
> question is
> # emerge --pretend --depclean --verbose gnome-keyring
>
> Regards,
> Arve
OK I think I got to the bottom of this, it is caused by package upgrade:
[ebuild U ] app-crypt/gcr-3.41.0 [3.40.0] USE="gtk introspection vala -gtk-doc -systemd% -test"
All other packages are new and pull-in as a dependency:
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 pulled in by:
app-crypt/libsecret-0.20.5-r3 requires =virtual/secret-service-0, virtual/secret-service
grep app-crypt/libsecret upgrade_07-07-22.txt
[ebuild N ] app-crypt/libsecret-0.20.5-r3 USE="crypt introspection vala -gtk-doc -test -tpm" ABI_X86="(64) -32 (-x32)"
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.
So maybe it is better to leave it as it is, instead of fighting the system :-)
But it would be nice if there were some notes about it during emerge.
All of a sudden when starting chrome, a message box pops up "choose password for new keyring" (without any explanation) and all screen is frozen, only option is to enter a password or "cancel it".
Thelma
next prev parent reply other threads:[~2022-07-08 16:20 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
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 [this message]
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=20de78a3-ee38-35b0-2457-8fd0ab326e68@sys-concept.com \
--to=thelma@sys-concept.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