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

[Loïc Minier]

On Mon, Jan 28, 2008, Bill Wohler wrote:
> Thanks for the great feedback! If what you say is true, then this bug
> can probably be closed. However, it would be helpful to others to create
> README.Debian and add the following text to it:

 This is what I've put:
gnome-keyring warnings
----------------------

If you didn't install the libpam-gnome-keyring dependency, you should probably
comment the pam_gnome_keyring.so line in /etc/pam.d/gnome-screensaver or you
might see warnings similar to:

    gnome-screensaver-dialog: PAM unable to dlopen(/lib/security/pam_gnome_keyring.so)
    gnome-screensaver-dialog: PAM [error: /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory]
    gnome-screensaver-dialog: PAM adding faulty module: lib/security/pam_gnome_keyring.so

These can also be ignored.


> /~i ~BRecommends isn't doing the right thing for me. It's listing
> installed packages that don't even *have* Recommends dependencies. 

 Works for me, but you have to search for "~i ~BRecommends", without the
 "/".

> However, I wouldn't want the gcj stuff installed (I use Sun's Java 6),
> nor xserver-xorg-video-all (I only need a single driver), but most of
> the recommendations are fine. Do you know if these are going to be
> included in the "cleanup" you mention?

 I have no idea about these particular deps; perhaps they need to be
 changed into Recommends: preferred-debian-choice | compatible-choices;
 typically Debian can't pull Sun's Java, but can let it be an
 alternative; the same story probably goes for xserver-xorg-video-all |
 xserver-xorg-video-driver.

> I see that my aptitude has an Option to install recommended packages for
> newly installed packages, so it looks like we should be good going
> forward.

 It should already be turned on by default in aptitude (I hope).

   Cheers,
-- 
Loïc Minier