p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so

Status changed to 'Confirmed' because the bug affects multiple users.

$ dpkg-query -W -f '${Conffiles}\n' gnome-keyring
 /etc/pkcs11/modules/gnome-keyring.module 18338a3e1e347ea0b25f3bc2182e95a6
 /etc/xdg/autostart/gnome-keyring-ssh.desktop d0633706edab7dcf53b813d1fa27bfa5
 /etc/xdg/autostart/gnome-keyring-gpg.desktop 526e256b3ced265836f32ade9881adad
 /etc/xdg/autostart/gnome-keyring-pkcs11.desktop 64bc5cf28b393d3ac666cf8a5471e951
 /etc/xdg/autostart/gnome-keyring-secrets.desktop ba4b9d132b504a05e16290d86f0c3a96
 /etc/pkcs11/modules/gnome-keyring-module 18338a3e1e347ea0b25f3bc2182e95a6 obsolete

gnome-keyring-module was renamed to gnome-keyring.module, but the old file stays around because it’s a conffile. We need calls to dpkg-maintscript-helper rm_conffile in the maintainer scripts.
http://wiki.debian.org/DpkgConffileHandling

Alternatively, we could not rename it at all. Not sure why someone felt this needed to be renamed.

This leaves conffile cruft around on user's systems and spews warning messages all over; we should get this fixed for 12.10.

As per post #3 comments, i've simply removed the old name:

sudo rm /etc/pkcs11/modules/gnome-keyring-module

and now the error is gone (does not see bad effects/trouble by doing that)

I can confirm that after removing the file as mentioned in post #6, the error goes away and the system is working fine.

See http://git.gnome.org/browse/gnome-keyring/commit/?id=840517c4b7eafedb77d2aac62aa6c73a0241517f

Ahh, this could be a result of upstream taking my "well-known name" idea from Ubuntu and mangling it further to only allow .module. Makes some sense, I suppose, and certainly fixes the same bug I was fixing with our local patch, just in a different way.

Explains the rename, at any rate.

Web (formerly known as epiphany) has lost all stored passwords.

This error always occurs before commiting changes in svn.

Hey Robert, could you fix that with the next update? Having a .maintscript (check gnome-screensaver for an example) doing a a rm_conffile of the old name should do it

This is still unfixed, and causes errors in some tools I use.

The warning occurs whenever a command line tool of CUPS is used. After

sudo rm /etc/pkcs11/modules/gnome-keyring-module

it disappears. Thank you for the tip.

svn up
Updating '.':
p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so

Warnin is gone after deleting /etc/pkcs11/modules/gnome-keyring-module. Thanks.

Is this warning I get about gnome- keyring the same bug or is something else the matter here?
I have renamed /etc/pkcs11/............ to gnome-keyring.module.
All the latest updates installed.
~$ libreoffice
Fontconfig warning: "/usr/lib/libreoffice/share/fonts/truetype/fc_local.conf", line 13: Having multiple <family> in <alias> isn't supported and may not works as expected
WARNING: gnome-keyring:: couldn't connect to: /home/johan/.cache/keyring-FRzd97/pkcs11: No such file or directory

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1038577

This bug was fixed in the package gnome-keyring - 3.6.0-0ubuntu1

---------------
gnome-keyring (3.6.0-0ubuntu1) quantal; urgency=low

  * debian/gnome-keyring.maintscript:
    - Remove renamed config file /etc/pkcs11/modules/gnome-keyring-module
      (LP: #1038577)

  [ Matthew Fischer ]
  * New upstream release (LP: #1056543)
 -- Robert Ancell <email address hidden> Wed, 26 Sep 2012 16:35:45 +1200