[gentoo-user] Re: How to disable gnome-keyring support in chromium?

2016-01-07 Thread Grant Edwards 
On 2015-05-18, Mick  wrote:
> On Monday 18 May 2015 22:17:43 Manuel Schönlaub wrote:
>> Just upgrade to the - unstable - chrome 43. As Mike stated in an email
>> before, the unconditional dependency in libsecret was removed in the new
>> ebuilds. You still would have to disable  or keep disabled those two USE
>> flags explicitly of course.
>
> Glad this was fixed.  Thanks for letting us know.

Now it seems to be broken again.  The popup started showing up again
sometime in the past couple weeks.  I'm running Chromium
47.0.2526.106, and it seems to have the same bug that was supposedly
fixed in version 43.

Even when built with -gnome-keyring, it insists on trying to use a
gnome keyring.

-- 
Grant Edwards   grant.b.edwardsYow! Do you guys know we
  at   just passed thru a BLACK
  gmail.comHOLE in space?

[gentoo-user] Re: How to disable gnome-keyring support in chromium?

2016-01-07 Thread Grant Edwards 
On 2016-01-07, Grant Edwards  wrote:
> On 2015-05-18, Mick  wrote:
>> On Monday 18 May 2015 22:17:43 Manuel Schönlaub wrote:
>>> Just upgrade to the - unstable - chrome 43. As Mike stated in an email
>>> before, the unconditional dependency in libsecret was removed in the new
>>> ebuilds. You still would have to disable  or keep disabled those two USE
>>> flags explicitly of course.
>>
>> Glad this was fixed.  Thanks for letting us know.
>
> Now it seems to be broken again.  The popup started showing up again
> sometime in the past couple weeks.  I'm running Chromium
> 47.0.2526.106, and it seems to have the same bug that was supposedly
> fixed in version 43.
>
> Even when built with -gnome-keyring, it insists on trying to use a
> gnome keyring.

You used to be able to temporarily fix this problem by doing 

  sudo emerge -C gnome-keyring

But, that doesn't work any longer.  Now you have to get rid of the
gcrprompter utility.  :/

-- 
Grant Edwards   grant.b.edwardsYow! Those people look
  at   exactly like Donnie and
  gmail.comMarie Osmond!!

Re: [gentoo-user] Re: How to disable gnome-keyring support in chromium?

2015-05-18 Thread Mick 
On Monday 18 May 2015 22:17:43 Manuel Schönlaub wrote:
 Just upgrade to the - unstable - chrome 43. As Mike stated in an email
 before, the unconditional dependency in libsecret was removed in the new
 ebuilds. You still would have to disable  or keep disabled those two USE
 flags explicitly of course.

Glad this was fixed.  Thanks for letting us know.
 
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Re: How to disable gnome-keyring support in chromium?

2015-05-18 Thread Grant Edwards 
On 2015-05-18, Manuel Schönlaub manuel.schoenl...@gmail.com wrote:

 Hm, I can't really reproduce it here.

I forgot to menion I'm using chromium stable 42.0.2311.135.

 - Did you disable these USE flags on the CLI, for that package only or
   system wide?

It's not enabled anywhere (make.conf, packate.use, profile, etc),
however it is not disabled anywhere either.

 - Is the gnome-keyring directly pulled in by chromium?

No, I don't think so.  

From what I can tell from looking at ebuild files, Chromium
unconditionally requires libsecret, and libsecret unconditionally
requires gnome-keyring.

 - What does emerge --info say?

It doesn't mention gnome-keyring at all:

Portage 2.2.18 (python 2.7.9-final-0, default/linux/amd64/13.0, gcc-4.8.4, 
glibc-2.20-r2, 3.18.11-gentoo x86_64)
=
System uname: 
Linux-3.18.11-gentoo-x86_64-Intel-R-_Core-TM-_i5-3570K_CPU_@_3.40GHz-with-gentoo-2.2
KiB Mem: 8064448 total,   1368024 free
KiB Swap:5885112 total,   5879556 free
Timestamp of repository gentoo: Mon, 18 May 2015 16:30:01 +
sh bash 4.2_p53
ld GNU ld (Gentoo 2.24 p1.4) 2.24
app-shells/bash:  4.2_p53::gentoo
dev-java/java-config: 2.2.0::gentoo
dev-lang/perl:5.20.2::gentoo
dev-lang/python:  2.7.9-r1::gentoo, 3.3.5-r1::gentoo, 3.4.1::gentoo
dev-util/cmake:   2.8.12.2-r1::gentoo
dev-util/pkgconfig:   0.28-r2::gentoo
sys-apps/baselayout:  2.2::gentoo
sys-apps/openrc:  0.13.11::gentoo
sys-apps/sandbox: 2.6-r1::gentoo
sys-devel/autoconf:   2.13::gentoo, 2.69::gentoo
sys-devel/automake:   1.11.6-r1::gentoo, 1.13.4::gentoo
sys-devel/binutils:   2.24-r3::gentoo
sys-devel/gcc:4.3.6-r1::gentoo, 4.5.4::gentoo, 4.6.4::gentoo, 
4.8.4::gentoo
sys-devel/gcc-config: 1.7.3::gentoo
sys-devel/libtool:2.4.6::gentoo
sys-devel/make:   4.1-r1::gentoo
sys-kernel/linux-headers: 3.18::gentoo (virtual/os-headers)
sys-libs/glibc:   2.20-r2::gentoo
Repositories:

gentoo
location: /usr/portage
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000

ACCEPT_KEYWORDS=amd64
ACCEPT_LICENSE=* -@EULA
CBUILD=x86_64-pc-linux-gnu
CFLAGS=-march=native -O2 -pipe
CHOST=x86_64-pc-linux-gnu
CONFIG_PROTECT=/etc /usr/lib64/libreoffice/program/sofficerc 
/usr/share/gnupg/qualified.txt /var/lib/hsqldb
CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/dconf /etc/env.d 
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release 
/etc/php/apache2-php5.5/ext-active/ /etc/php/cgi-php5.5/ext-active/ 
/etc/php/cli-php5.5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d 
/etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d 
/etc/texmf/updmap.d /etc/texmf/web2c
CXXFLAGS=-march=native -O2 -pipe
DISTDIR=/usr/portage/distfiles
FCFLAGS=-O2 -pipe
FEATURES=assume-digests binpkg-logs config-protect-if-modified distlocks 
ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs 
protect-owned sandbox sfperms splitdebug strict unknown-features-warn 
unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync
FFLAGS=-O2 -pipe
GENTOO_MIRRORS=http://gentoo.cites.uiuc.edu/pub/gentoo/ 
http://gentoo.cs.uni.edu/ http://lug.mtu.edu/gentoo/;
LANG=en_US.utf8
LDFLAGS=-Wl,-O1 -Wl,--as-needed
MAKEOPTS=-j2
PKGDIR=/usr/portage/packages
PORTAGE_CONFIGROOT=/
PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times 
--omit-dir-times --compress --force --whole-file --delete --stats 
--human-readable --timeout=180 --exclude=/distfiles --exclude=/local 
--exclude=/packages
PORTAGE_TMPDIR=/var/tmp
USE=X a52 aac acl aes alsa amd64 avx berkdb bzip2 cdr cli cracklib crypt cups 
cxx dri dvd flac fortran gdbm gkt2 gtk iconv imap ipv6 jpeg mmx mmxext modules 
mozbranding mp3 multilib ncurses nls nptl nsplugin ogg openmp pam pcre pdf png 
popcnt readline samba session sse sse2 sse3 sse4_1 sse4_2 ssl ssse3 svg tcpd 
tiff tk unicode v4l vorbis xv zlib ABI_X86=64 ALSA_CARDS=ali5451 als4000 
atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 
fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx 
via82xx-modem ymfpci APACHE2_MODULES=authn_core authz_core socache_shmcb 
unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default 
authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner 
authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache 
env expires ext_filter file_cache filter headers include info log_config logio 
mem_cache mime mime_magic negotiation rewrite setenvif speling status uni
 que_id userdir usertrack vhost_alias CALLIGRA_FEATURES=kexi words flow plan 
sheets stage tables krita karbon braindump author CAMERAS=ptp2 
COLLECTD_PLUGINS=df interface irq load memory rrdtool swap syslog 
CPU_FLAGS_X86=aes avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3 
ELIBC=glibc GPSD_PROTOCOLS=ashtech aivdm earthmate evermore fv18 garmin

Re: [gentoo-user] Re: How to disable gnome-keyring support in chromium?

2015-05-18 Thread Mike Gilbert 
On Mon, May 18, 2015 at 4:30 PM, Grant Edwards
grant.b.edwa...@gmail.com wrote:
 On 2015-05-18, Manuel Schönlaub manuel.schoenl...@gmail.com wrote:

 Hm, I can't really reproduce it here.

 I forgot to menion I'm using chromium stable 42.0.2311.135.


Upgrade to chromium-43; the ebuild has been adjusted to not require libsecret.

See bug 538224.

https://bugs.gentoo.org/show_bug.cgi?id=538224

Re: [gentoo-user] Re: How to disable gnome-keyring support in chromium?

2015-05-18 Thread Manuel Schönlaub 
The unstable version (43) has had its  dependency on libsecret removed.

Furthermore the package's standard USE flags include gnome and
gnome-keyring. You would disable them explicitly in order not to have
libgnome-keyring (and gconf) installed again.
Am 18.05.2015 22:32 schrieb Grant Edwards grant.b.edwa...@gmail.com:

 On 2015-05-18, Manuel Schönlaub manuel.schoenl...@gmail.com wrote:

  Hm, I can't really reproduce it here.

 I forgot to menion I'm using chromium stable 42.0.2311.135.

  - Did you disable these USE flags on the CLI, for that package only or
system wide?

 It's not enabled anywhere (make.conf, packate.use, profile, etc),
 however it is not disabled anywhere either.

  - Is the gnome-keyring directly pulled in by chromium?

 No, I don't think so.

 From what I can tell from looking at ebuild files, Chromium
 unconditionally requires libsecret, and libsecret unconditionally
 requires gnome-keyring.

  - What does emerge --info say?

 It doesn't mention gnome-keyring at all:

 Portage 2.2.18 (python 2.7.9-final-0, default/linux/amd64/13.0, gcc-4.8.4,
 glibc-2.20-r2, 3.18.11-gentoo x86_64)
 =
 System uname: Linux-3.18.11-gentoo-x86_64-Intel-R-_Core-TM-_i5-3570K_CPU_@
 _3.40GHz-with-gentoo-2.2
 KiB Mem: 8064448 total,   1368024 free
 KiB Swap:5885112 total,   5879556 free
 Timestamp of repository gentoo: Mon, 18 May 2015 16:30:01 +
 sh bash 4.2_p53
 ld GNU ld (Gentoo 2.24 p1.4) 2.24
 app-shells/bash:  4.2_p53::gentoo
 dev-java/java-config: 2.2.0::gentoo
 dev-lang/perl:5.20.2::gentoo
 dev-lang/python:  2.7.9-r1::gentoo, 3.3.5-r1::gentoo, 3.4.1::gentoo
 dev-util/cmake:   2.8.12.2-r1::gentoo
 dev-util/pkgconfig:   0.28-r2::gentoo
 sys-apps/baselayout:  2.2::gentoo
 sys-apps/openrc:  0.13.11::gentoo
 sys-apps/sandbox: 2.6-r1::gentoo
 sys-devel/autoconf:   2.13::gentoo, 2.69::gentoo
 sys-devel/automake:   1.11.6-r1::gentoo, 1.13.4::gentoo
 sys-devel/binutils:   2.24-r3::gentoo
 sys-devel/gcc:4.3.6-r1::gentoo, 4.5.4::gentoo, 4.6.4::gentoo,
 4.8.4::gentoo
 sys-devel/gcc-config: 1.7.3::gentoo
 sys-devel/libtool:2.4.6::gentoo
 sys-devel/make:   4.1-r1::gentoo
 sys-kernel/linux-headers: 3.18::gentoo (virtual/os-headers)
 sys-libs/glibc:   2.20-r2::gentoo
 Repositories:

 gentoo
 location: /usr/portage
 sync-type: rsync
 sync-uri: rsync://rsync.gentoo.org/gentoo-portage
 priority: -1000

 ACCEPT_KEYWORDS=amd64
 ACCEPT_LICENSE=* -@EULA
 CBUILD=x86_64-pc-linux-gnu
 CFLAGS=-march=native -O2 -pipe
 CHOST=x86_64-pc-linux-gnu
 CONFIG_PROTECT=/etc /usr/lib64/libreoffice/program/sofficerc
 /usr/share/gnupg/qualified.txt /var/lib/hsqldb
 CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/dconf /etc/env.d
 /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release
 /etc/php/apache2-php5.5/ext-active/ /etc/php/cgi-php5.5/ext-active/
 /etc/php/cli-php5.5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d
 /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d
 /etc/texmf/updmap.d /etc/texmf/web2c
 CXXFLAGS=-march=native -O2 -pipe
 DISTDIR=/usr/portage/distfiles
 FCFLAGS=-O2 -pipe
 FEATURES=assume-digests binpkg-logs config-protect-if-modified distlocks
 ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs
 protect-owned sandbox sfperms splitdebug strict unknown-features-warn
 unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync
 FFLAGS=-O2 -pipe
 GENTOO_MIRRORS=http://gentoo.cites.uiuc.edu/pub/gentoo/
 http://gentoo.cs.uni.edu/ http://lug.mtu.edu/gentoo/;
 LANG=en_US.utf8
 LDFLAGS=-Wl,-O1 -Wl,--as-needed
 MAKEOPTS=-j2
 PKGDIR=/usr/portage/packages
 PORTAGE_CONFIGROOT=/
 PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times
 --omit-dir-times --compress --force --whole-file --delete --stats
 --human-readable --timeout=180 --exclude=/distfiles --exclude=/local
 --exclude=/packages
 PORTAGE_TMPDIR=/var/tmp
 USE=X a52 aac acl aes alsa amd64 avx berkdb bzip2 cdr cli cracklib crypt
 cups cxx dri dvd flac fortran gdbm gkt2 gtk iconv imap ipv6 jpeg mmx mmxext
 modules mozbranding mp3 multilib ncurses nls nptl nsplugin ogg openmp pam
 pcre pdf png popcnt readline samba session sse sse2 sse3 sse4_1 sse4_2 ssl
 ssse3 svg tcpd tiff tk unicode v4l vorbis xv zlib ABI_X86=64
 ALSA_CARDS=ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci
 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m
 maestro3 trident usb-audio via82xx via82xx-modem ymfpci
 APACHE2_MODULES=authn_core authz_core socache_shmcb unixd actions alias
 auth_basic authn_alias authn_anon authn_dbm authn_default authn_file
 authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user
 autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env
 expires ext_filter file_cache filter headers include info log_config logio
 mem_cache mime mime_magic negotiation

Re: [gentoo-user] Re: How to disable gnome-keyring support in chromium?

2015-05-18 Thread Mick 
On Monday 18 May 2015 21:30:51 Grant Edwards wrote:
 On 2015-05-18, Manuel Schönlaub manuel.schoenl...@gmail.com wrote:
  Hm, I can't really reproduce it here.
 
 I forgot to menion I'm using chromium stable 42.0.2311.135.

Same here.

  - Did you disable these USE flags on the CLI, for that package only or
  
system wide?
 
 It's not enabled anywhere (make.conf, packate.use, profile, etc),
 however it is not disabled anywhere either.

Almost same here.  I have USE=-gnome in make.conf and gnome-keyring is also 
disabled globally (I guess due to my profile):

$ euse -i gnome-keyring
global use flags (searching: gnome-keyring)

[-  ] gnome-keyring - Enable support for storing passwords via gnome-
keyring

local use flags (searching: gnome-keyring)

[-  ] gnome-keyring
sys-auth/pambase: Enable pam_gnome_keyring module on system login 
stack. This enables proper Gnome Keyring access to logins, whether 
they are done with the login shell, a Desktop Manager or a remote 
login systems such as SSH.
[-  ] 20101024-r2 [gentoo]
[-  ] 20120417-r3 [gentoo]
[-  ] 20140313 [gentoo]
[-  ] 20150213 [gentoo]



  - Is the gnome-keyring directly pulled in by chromium?
 
 No, I don't think so.
 
 From what I can tell from looking at ebuild files, Chromium
 unconditionally requires libsecret, and libsecret unconditionally
 requires gnome-keyring.
 
  - What does emerge --info say?
 
 It doesn't mention gnome-keyring at all:
 
 Portage 2.2.18 (python 2.7.9-final-0, default/linux/amd64/13.0, gcc-4.8.4,
 glibc-2.20-r2, 3.18.11-gentoo x86_64)
 =
 System uname:
 Linux-3.18.11-gentoo-x86_64-Intel-R-_Core-TM-_i5-3570K_CPU_@_3.40GHz-with-
 gentoo-2.2 KiB Mem: 8064448 total,   1368024 free
 KiB Swap:5885112 total,   5879556 free
 Timestamp of repository gentoo: Mon, 18 May 2015 16:30:01 +
 sh bash 4.2_p53
 ld GNU ld (Gentoo 2.24 p1.4) 2.24
 app-shells/bash:  4.2_p53::gentoo
 dev-java/java-config: 2.2.0::gentoo
 dev-lang/perl:5.20.2::gentoo
 dev-lang/python:  2.7.9-r1::gentoo, 3.3.5-r1::gentoo, 3.4.1::gentoo
 dev-util/cmake:   2.8.12.2-r1::gentoo
 dev-util/pkgconfig:   0.28-r2::gentoo
 sys-apps/baselayout:  2.2::gentoo
 sys-apps/openrc:  0.13.11::gentoo
 sys-apps/sandbox: 2.6-r1::gentoo
 sys-devel/autoconf:   2.13::gentoo, 2.69::gentoo
 sys-devel/automake:   1.11.6-r1::gentoo, 1.13.4::gentoo
 sys-devel/binutils:   2.24-r3::gentoo
 sys-devel/gcc:4.3.6-r1::gentoo, 4.5.4::gentoo, 4.6.4::gentoo,
 4.8.4::gentoo sys-devel/gcc-config: 1.7.3::gentoo
 sys-devel/libtool:2.4.6::gentoo
 sys-devel/make:   4.1-r1::gentoo
 sys-kernel/linux-headers: 3.18::gentoo (virtual/os-headers)
 sys-libs/glibc:   2.20-r2::gentoo
 Repositories:
 
 gentoo
 location: /usr/portage
 sync-type: rsync
 sync-uri: rsync://rsync.gentoo.org/gentoo-portage
 priority: -1000
 
 ACCEPT_KEYWORDS=amd64
 ACCEPT_LICENSE=* -@EULA
 CBUILD=x86_64-pc-linux-gnu
 CFLAGS=-march=native -O2 -pipe
 CHOST=x86_64-pc-linux-gnu
 CONFIG_PROTECT=/etc /usr/lib64/libreoffice/program/sofficerc
 /usr/share/gnupg/qualified.txt /var/lib/hsqldb
 CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/dconf /etc/env.d
 /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release
 /etc/php/apache2-php5.5/ext-active/ /etc/php/cgi-php5.5/ext-active/
 /etc/php/cli-php5.5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d
 /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d
 /etc/texmf/updmap.d /etc/texmf/web2c CXXFLAGS=-march=native -O2 -pipe
 DISTDIR=/usr/portage/distfiles
 FCFLAGS=-O2 -pipe
 FEATURES=assume-digests binpkg-logs config-protect-if-modified distlocks
 ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs
 protect-owned sandbox sfperms splitdebug strict unknown-features-warn
 unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync
 FFLAGS=-O2 -pipe
 GENTOO_MIRRORS=http://gentoo.cites.uiuc.edu/pub/gentoo/
 http://gentoo.cs.uni.edu/ http://lug.mtu.edu/gentoo/; LANG=en_US.utf8
 LDFLAGS=-Wl,-O1 -Wl,--as-needed
 MAKEOPTS=-j2
 PKGDIR=/usr/portage/packages
 PORTAGE_CONFIGROOT=/
 PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times
 --omit-dir-times --compress --force --whole-file --delete --stats
 --human-readable --timeout=180 --exclude=/distfiles --exclude=/local
 --exclude=/packages PORTAGE_TMPDIR=/var/tmp
 USE=X a52 aac acl aes alsa amd64 avx berkdb bzip2 cdr cli cracklib crypt
 cups cxx dri dvd flac fortran gdbm gkt2 gtk iconv imap ipv6 jpeg mmx
 mmxext modules mozbranding mp3 multilib ncurses nls nptl nsplugin ogg
 openmp pam pcre pdf png popcnt readline samba session sse sse2 sse3 sse4_1
 sse4_2 ssl ssse3 svg tcpd tiff tk unicode v4l vorbis xv zlib ABI_X86=64

Re: [gentoo-user] Re: How to disable gnome-keyring support in chromium?

2015-05-18 Thread Manuel Schönlaub 
Just upgrade to the - unstable - chrome 43. As Mike stated in an email
before, the unconditional dependency in libsecret was removed in the new
ebuilds. You still would have to disable  or keep disabled those two USE
flags explicitly of course.
Am 18.05.2015 23:01 schrieb Mick michaelkintz...@gmail.com:

 On Monday 18 May 2015 21:30:51 Grant Edwards wrote:
  On 2015-05-18, Manuel Schönlaub manuel.schoenl...@gmail.com wrote:
   Hm, I can't really reproduce it here.
 
  I forgot to menion I'm using chromium stable 42.0.2311.135.

 Same here.

   - Did you disable these USE flags on the CLI, for that package only or
  
 system wide?
 
  It's not enabled anywhere (make.conf, packate.use, profile, etc),
  however it is not disabled anywhere either.

 Almost same here.  I have USE=-gnome in make.conf and gnome-keyring is
 also
 disabled globally (I guess due to my profile):

 $ euse -i gnome-keyring
 global use flags (searching: gnome-keyring)
 
 [-  ] gnome-keyring - Enable support for storing passwords via gnome-
 keyring

 local use flags (searching: gnome-keyring)
 
 [-  ] gnome-keyring
 sys-auth/pambase: Enable pam_gnome_keyring module on system login
 stack. This enables proper Gnome Keyring access to logins, whether
 they are done with the login shell, a Desktop Manager or a remote
 login systems such as SSH.
 [-  ] 20101024-r2 [gentoo]
 [-  ] 20120417-r3 [gentoo]
 [-  ] 20140313 [gentoo]
 [-  ] 20150213 [gentoo]



   - Is the gnome-keyring directly pulled in by chromium?
 
  No, I don't think so.
 
  From what I can tell from looking at ebuild files, Chromium
  unconditionally requires libsecret, and libsecret unconditionally
  requires gnome-keyring.
 
   - What does emerge --info say?
 
  It doesn't mention gnome-keyring at all:
 
  Portage 2.2.18 (python 2.7.9-final-0, default/linux/amd64/13.0,
 gcc-4.8.4,
  glibc-2.20-r2, 3.18.11-gentoo x86_64)
  =
  System uname:
  Linux-3.18.11-gentoo-x86_64-Intel-R-_Core-TM-_i5-3570K_CPU_@
 _3.40GHz-with-
  gentoo-2.2 KiB Mem: 8064448 total,   1368024 free
  KiB Swap:5885112 total,   5879556 free
  Timestamp of repository gentoo: Mon, 18 May 2015 16:30:01 +
  sh bash 4.2_p53
  ld GNU ld (Gentoo 2.24 p1.4) 2.24
  app-shells/bash:  4.2_p53::gentoo
  dev-java/java-config: 2.2.0::gentoo
  dev-lang/perl:5.20.2::gentoo
  dev-lang/python:  2.7.9-r1::gentoo, 3.3.5-r1::gentoo,
 3.4.1::gentoo
  dev-util/cmake:   2.8.12.2-r1::gentoo
  dev-util/pkgconfig:   0.28-r2::gentoo
  sys-apps/baselayout:  2.2::gentoo
  sys-apps/openrc:  0.13.11::gentoo
  sys-apps/sandbox: 2.6-r1::gentoo
  sys-devel/autoconf:   2.13::gentoo, 2.69::gentoo
  sys-devel/automake:   1.11.6-r1::gentoo, 1.13.4::gentoo
  sys-devel/binutils:   2.24-r3::gentoo
  sys-devel/gcc:4.3.6-r1::gentoo, 4.5.4::gentoo, 4.6.4::gentoo,
  4.8.4::gentoo sys-devel/gcc-config: 1.7.3::gentoo
  sys-devel/libtool:2.4.6::gentoo
  sys-devel/make:   4.1-r1::gentoo
  sys-kernel/linux-headers: 3.18::gentoo (virtual/os-headers)
  sys-libs/glibc:   2.20-r2::gentoo
  Repositories:
 
  gentoo
  location: /usr/portage
  sync-type: rsync
  sync-uri: rsync://rsync.gentoo.org/gentoo-portage
  priority: -1000
 
  ACCEPT_KEYWORDS=amd64
  ACCEPT_LICENSE=* -@EULA
  CBUILD=x86_64-pc-linux-gnu
  CFLAGS=-march=native -O2 -pipe
  CHOST=x86_64-pc-linux-gnu
  CONFIG_PROTECT=/etc /usr/lib64/libreoffice/program/sofficerc
  /usr/share/gnupg/qualified.txt /var/lib/hsqldb
  CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/dconf /etc/env.d
  /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release
  /etc/php/apache2-php5.5/ext-active/ /etc/php/cgi-php5.5/ext-active/
  /etc/php/cli-php5.5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d
  /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d
  /etc/texmf/updmap.d /etc/texmf/web2c CXXFLAGS=-march=native -O2 -pipe
  DISTDIR=/usr/portage/distfiles
  FCFLAGS=-O2 -pipe
  FEATURES=assume-digests binpkg-logs config-protect-if-modified distlocks
  ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs
  protect-owned sandbox sfperms splitdebug strict unknown-features-warn
  unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync
  FFLAGS=-O2 -pipe
  GENTOO_MIRRORS=http://gentoo.cites.uiuc.edu/pub/gentoo/
  http://gentoo.cs.uni.edu/ http://lug.mtu.edu/gentoo/; LANG=en_US.utf8
  LDFLAGS=-Wl,-O1 -Wl,--as-needed
  MAKEOPTS=-j2
  PKGDIR=/usr/portage/packages
  PORTAGE_CONFIGROOT=/
  PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times
  --omit-dir-times --compress --force --whole-file --delete --stats
  --human-readable --timeout=180 --exclude=/distfiles --exclude=/local
  --exclude=/packages

[gentoo-user] Re: How to disable gnome-keyring support in chromium?

2015-05-18 Thread Grant Edwards 
On 2015-05-18, Mike Gilbert flop...@gentoo.org wrote:
 On Mon, May 18, 2015 at 4:30 PM, Grant Edwards
grant.b.edwa...@gmail.com wrote:
 On 2015-05-18, Manuel Schönlaub manuel.schoenl...@gmail.com wrote:

 Hm, I can't really reproduce it here.

 I forgot to menion I'm using chromium stable 42.0.2311.135.


 Upgrade to chromium-43; the ebuild has been adjusted to not require libsecret.

 See bug 538224.

 https://bugs.gentoo.org/show_bug.cgi?id=538224

Yep. Should've checked bugzilla.

Thanks.

-- 
Grant Edwards   grant.b.edwardsYow! Look DEEP into the
  at   OPENINGS!!  Do you see any
  gmail.comELVES or EDSELS ... or a
   HIGHBALL?? ...