Bug#771555: gnome-keyring Iceweasel plugin cannot be disabled

Alexander Bessman alexander.bessman at gmail.com
Sun Nov 30 17:22:08 UTC 2014


Package: gnome-keyring
Version: 3.14.0-1+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

After updating to GNOME 3.14, Iceweasel keeps asking to create a keyring named
"mozilla" and won't take no for an answer. This behaviour is presumably caused
by the GNOME keyring integration browser plugin. This plugin cannot be
disabled; its status remains as "GNOME Keyring integration will be disabled
after you restart Iceweasel" even after the entire system has been restarted!
This renders Iceweasel unusable in conjunction with GNOME.

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-keyring depends on:
ii  dbus-x11                                     1.8.12-1
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gcr                                          3.14.0-2
ii  libc6                                        2.19-13
ii  libcap-ng0                                   0.7.4-2
ii  libcap2-bin                                  1:2.24-6
ii  libdbus-1-3                                  1.8.12-1
ii  libgck-1-0                                   3.14.0-2
ii  libgcr-base-3-1                              3.14.0-2
ii  libgcrypt20                                  1.6.2-4
ii  libglib2.0-0                                 2.42.1-1
ii  p11-kit                                      0.20.7-1

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring  3.14.0-1+b1

gnome-keyring suggests no packages.

-- no debconf information




More information about the pkg-gnome-maintainers mailing list