On Sonday, 28. September 2014, 21:47:43 Yves-Alexis Perez wrote: > On dim., 2014-09-28 at 10:28 +0200, Patrick Häcker wrote: > > So change the lines > > > > > auth optional pam_gnome_keyring.so > > > session optional pam_gnome_keyring.so auto_start > > > > into > > > > > -auth optional pam_gnome_keyring.so > > > -session optional pam_gnome_keyring.so auto_start > > > > in file /etc/pam.d/lightdm to tell PAM to ignore pam_gnome_keyring.so if > > it is missing. > > > > I didn't create a patch file, as the fix is straightforward, although I > > can do that if necessary. > > Let's do that and see how it goes.
How is the word "that" meant in the above sentence? Do you mean to use the proposed solution or do you mean I should create a patch? > The log error is generally useful for people which are actually > expecting this to work and looking at the log to check why it doesn't, > but we can try and always revert back later. I agree. The log error is useful for those who expect the module to be available and useless for those who expect the module to be missing. A falsely missing module should be very rare, but finding the root of the problem will be time consuming without the warning. The false warning is common, but does only little harm (obfuscate and unsettle). Both solutions are not perfect. As written, the ideal solution would probably depend on the installed packages and some .d-directories. Nevertheless, I think this heads into the right direction. Kind regards Patrick
signature.asc
Description: This is a digitally signed message part.