commit e5d445e9321a6f4d2b89e33139f1b136ecc06ef7 Author: Matthias Clasen Date: 2015-03-17 3.15.92 NEWS | 5 +++++ configure.ac | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) commit 36785e07d5b49c6cbe2a412fc1e77e1782eaa28c Author: Samir Ribic Date: 2015-03-13 Updated Bosnian translation po/bs.po | 634 ++++++++++++++++++++++++++++++++++----------------------------- 1 file changed, 340 insertions(+), 294 deletions(-) commit 06422ea18cebfd6d4d554d01445eafb3d140d6b8 Author: Christophe Fergeau Date: 2015-03-06 Revert "ssh-agent: Fix leak in search_keys_like_attributes()" This reverts commit d177a8b5353f3156ab504f39c20753d6786e5e4d. This breaks the ssh agent as this causes it to fail to remember unlocked keys, and to always ask for a key passphrase when attempting an ssh connection. From https://bugzilla.gnome.org/show_bug.cgi?id=744280 : « ssh foo.example.com is always asking to unlock the corresponding key while before this commit this works fine. gkd-ssh-agent-ops.c:op_sign_request has: result = unlock_and_sign (session, key, mech, hash, n_hash, &n_result, &error); g_object_unref (session); g_object_unref (key); After the leak fix mentioned above, unreffing 'key' causes the last reference to be released, so it's destroyed, and this locks the just unlocked key. Removing the g_object_unref() avoids this issue, but readds a leak. I assume 'key' should be added somewhere so that it's kept alive, but I'm not really sure where/how » daemon/ssh-agent/gkd-ssh-agent-ops.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) commit a942c8f458e337d90101e6a81654478fda6ccfa9 Author: Clement Lefebvre Date: 2015-03-05 pam: Make sure to never block SIGCHLD Blocking this signal prevented MDM logins, as the slave couldn't notice the death of the greeter) Signed-off-by: Stef Walter * Use goto and a single return path https://bugzilla.gnome.org/show_bug.cgi?id=745673 pam/gkr-pam-client.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)