From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 81FF5138CD0 for ; Mon, 18 May 2015 19:57:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 508D2E0929; Mon, 18 May 2015 19:57:01 +0000 (UTC) Received: from mail-ig0-f176.google.com (mail-ig0-f176.google.com [209.85.213.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4034DE090B for ; Mon, 18 May 2015 19:57:00 +0000 (UTC) Received: by igbpi8 with SMTP id pi8so58140639igb.1 for ; Mon, 18 May 2015 12:56:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=lkYhSdci+n7BsqAErPLXwombB/LMHgKxq8rMIxbUOgw=; b=ifzW++eLOvO90aree29Ep+VtJdOi/vywLvBp75gSDfd4lzue9gBirJagD4tCYudXX+ c79zix2aQvzcBr+SCuLV4BU602zTP8N+B/XvSTMowx7FxsVE1/+xWe5ngGYjhAVjfJr8 9Erj09aW+Eei3GvCmvcOfgF19rMbF5cH40hXQVwjfqrCGF3gq2uTsWOAx5+u2jHmWwKr zvA0TxjnjXLPgvpkR0jUvTUPmJvYenz327d0EgsX6cswyxFgg2M/JWfaKH6hwuofhZOQ EOVlVbqVo9qC8J0eJdNXCT4jZdhhC5GdfffHVXI8RQ6D7ErZ4mastrVCbrGr5q0muOFM mHWA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.43.39.208 with SMTP id tn16mr35995904icb.27.1431979019593; Mon, 18 May 2015 12:56:59 -0700 (PDT) Received: by 10.107.51.66 with HTTP; Mon, 18 May 2015 12:56:59 -0700 (PDT) In-Reply-To: References: Date: Mon, 18 May 2015 21:56:59 +0200 Message-ID: Subject: Re: [gentoo-user] How to disable gnome-keyring support in chromium? From: =?UTF-8?Q?Manuel_Sch=C3=B6nlaub?= To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=bcaec51a842ac9ed89051660981c X-Archives-Salt: 452f9ac7-5954-440f-8937-273eb8ab5fa9 X-Archives-Hash: 5a93dd91f4255441a04e8b76f9e42ee6 --bcaec51a842ac9ed89051660981c Content-Type: text/plain; charset=UTF-8 Hm, I can't really reproduce it here. - Did you disable these USE flags on the CLI, for that package only or system wide? - What does emerge --info say? - Is the gnome-keyring directly pulled in by chromium? 2015-05-18 20:41 GMT+02:00 Grant Edwards : > I'm building chromium with USE flags set to -gnome -gnome-keyring, but > it's still pulling in libsecret and gnome-keyring and nagging me about > a password for the keyring every time it starts. > > I've found that simply doing an "emerge -C gnome-keyring" fixes the > the problem temporarily, but then next time I do an "emerge -u" it > wants to install gnome-keyring again. > > -- > Grant Edwards grant.b.edwards Yow! Am I elected yet? > at > gmail.com > > > --bcaec51a842ac9ed89051660981c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hm, I can't really reproduce it here.
- = Did you disable these USE flags on the CLI, for that package only or system= wide?
- What does emerge --info say?
- Is the gnome-keyr= ing directly pulled in by chromium?




2015-05-18 20= :41 GMT+02:00 Grant Edwards <grant.b.edwards@gmail.com>:
I'm building chromium with USE f= lags set to -gnome -gnome-keyring, but
it's still pulling in libsecret and gnome-keyring and nagging me about<= br> a password for the keyring every time it starts.

I've found that simply doing an "emerge -C gnome-keyring" fix= es the
the problem temporarily, but then next time I do an "emerge -u" i= t
wants to install gnome-keyring again.

--
Grant Edwards=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0grant.b= .edwards=C2=A0 =C2=A0 =C2=A0 =C2=A0 Yow! Am I elected yet?
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 at
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 gmail.com



--bcaec51a842ac9ed89051660981c--