Am Montag, den 26.09.2011, 00:17 -0700 schrieb Steve Langasek: > On Mon, Sep 26, 2011 at 09:01:13AM +0200, Paul Menzel wrote: > > affects 642952 libpam-gnome-keyring > > thanks > > > Am Sonntag, den 25.09.2011, 14:55 -0700 schrieb Russ Allbery: > > > […] > > > > This, among other things, will cause a FTBFS for all PAM modules on > > > platforms where shared module code has to be built PIC. See the > > > build logs for libpam-krb5, for example. > > > After upgrading to 1.1.3-3 and rebooting Evolution could not get any > > passwords from GNOME Keyring with the following error messages. > > > Gkr-Message: received an invalid, unencryptable, or non-utf8 secret > > Gkr-Message: call to daemon returned an invalid response: > > (null).(null)() > > Gkr-Message: received an invalid, unencryptable, or non-utf8 secret > > Gkr-Message: call to daemon returned an invalid response: > > (null).(null)() > > > (evolution:3945): e-data-server-ui-WARNING **: Unable to find > > password(s) in keyring (Keyring reports: Fehler bei der Kommunikation mit > > dem GNOME-Schlüsselbunddienst) > > > Upgrading to 1.1.3-4, restarting GNOME Keyring daemon > > (`gnome-keyring-daemon --replace`) and then Evolution fixes the problem. > > No, that's not related to this bug. This bug only concerned the placement > of .so files in the traditional vs. multiarch library path; that only > impacts build-time linking software against libpam, it has no affect on the > system at runtime.
Can you think of a reason why this broke with 1.1.3-3 and was fixed by 1.1.3-4? Thanks, Paul
signature.asc
Description: This is a digitally signed message part
