Bug#457549: gnome-screensaver: Wants non-existing pam_gnome_keyring.so

[Bill Wohler]

Josselin Mouette <joss at debian.org> wrote:

> On sam, 2008-01-26 at 18:07 -0800, Bill Wohler wrote:
> > Package: gnome-screensaver
> > Version: 2.20.0-2
> > Severity: normal
> > 
> > I'm getting the same thing:
> > 
> >     Jan 26 14:59:56 olgas gnome-screensaver-dialog: PAM unable to dlopen(/lib/security/pam_gnome_keyring.so)
> >     Jan 26 14:59:56 olgas gnome-screensaver-dialog: PAM [error: /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory]
> >     Jan 26 14:59:56 olgas gnome-screensaver-dialog: PAM adding faulty module: /lib/security/pam_gnome_keyring.so
> > 
> > Unlocking the locked screen works fine, so I'd either fix the problem
> > it's reporting, or not treat it as an error and remove the message.
> 
> > Versions of packages gnome-screensaver recommends:
> > pn  libpam-gnome-keyring          <none>     (no description available)
> 
> This is because this package is missing. Still, the problem is
> absolutely harmless, and you are merely missing the pam_gnome_keyring
> functionality.

In that case, gnome-screensaver should either depend on this package, or
it should not make the call in the first place if this package is
missing, thereby avoiding the error message. In other words, if
something is "completely harmless", there should be no error message in
the log in the first place.

Either way, it's still a bug.

I pretended that this package depends on libpam-gnome-keyring and
installed it. I am now seeing:

  Jan 27 10:08:53 olgas gnome-screensaver-dialog: gkr-pam: created 'login' keyring

which can be safely added to logcheck's filters.

Thanks for pointing out the recommended package.

-- 
Bill Wohler <wohler at newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD