1 |
On 2016-01-07, Grant Edwards <grant.b.edwards@×××××.com> wrote: |
2 |
> On 2015-05-18, Mick <michaelkintzios@×××××.com> wrote: |
3 |
>> On Monday 18 May 2015 22:17:43 Manuel Schönlaub wrote: |
4 |
>>> Just upgrade to the - unstable - chrome 43. As Mike stated in an email |
5 |
>>> before, the unconditional dependency in libsecret was removed in the new |
6 |
>>> ebuilds. You still would have to disable or keep disabled those two USE |
7 |
>>> flags explicitly of course. |
8 |
>> |
9 |
>> Glad this was fixed. Thanks for letting us know. |
10 |
> |
11 |
> Now it seems to be broken again. The popup started showing up again |
12 |
> sometime in the past couple weeks. I'm running Chromium |
13 |
> 47.0.2526.106, and it seems to have the same bug that was supposedly |
14 |
> fixed in version 43. |
15 |
> |
16 |
> Even when built with -gnome-keyring, it insists on trying to use a |
17 |
> gnome keyring. |
18 |
|
19 |
You used to be able to temporarily fix this problem by doing |
20 |
|
21 |
sudo emerge -C gnome-keyring |
22 |
|
23 |
But, that doesn't work any longer. Now you have to get rid of the |
24 |
gcrprompter utility. :/ |
25 |
|
26 |
-- |
27 |
Grant Edwards grant.b.edwards Yow! Those people look |
28 |
at exactly like Donnie and |
29 |
gmail.com Marie Osmond!! |