Description of problem: With mate-keyring-1.5.1-1 the keyring framwork doesn't read any user login informations which are stored in ~/.config/mate/keyrings after login. In result you're everytime to be forced to enter a password if you use a ssh keyring for example. The reason for this issue is your wrong spec file. %configure \ --disable-static \ --with-gtk=2.0 \ --disable-schemas-compile \ --enable-gcov \ --libexecdir=/usr/libexec \ --with-pam-dir=%{_sysconfdir}/pam.d \ --with-root-certs=%{_sysconfdir}/pki/tls/certs Why do you thing that %{_sysconfdir}/pam.d is the right directory for pam_mate_keyring.so? You're are the only one who installed a lib in this dierectory. The right place is /usr/lib64/security or /lib64/security. If you you don't know what you doing let the spec file in state like it was from Leigh Scott, take a look at gnome-keyring spec file or use fedora packager guidelines. https://fedoraproject.org/wiki/Packaging:Guidelines#Filesystem_Layout
Wolfgang, we all are here to improve MATE, I hope. Please be more respectful on bug reports.
Stefano, installing a lib in %{_sysconfdir}/pam.d is nothing what deserves respect.
Wolfgang, there's an old saying "If you can't say anything nice, don't say anything at all". Reporting this bug and it's consequences is OK and encouraged, of course... But, questioning someone's motives or competency (that's my impression, even if it may not be your intention), is certainly *not* OK. Please be mindful of the sometimes subtle difference. I'll take care of fixing this bug.
Breakage occurred in commit 709ecf467c0938797eeb86010e360b3a8c94bd07 "Add patch to build for f19 which include various bugfix commits from upstream, minor specfile tweaks" Again, please be mindful to make commits smaller and more self contained. this was so big, it was difficult to follow all the changes and notice. Dan, I see 1.6.0 already in master/ branch, is your intention to push that down to f18 too soon, or should I backport this fix separately to 1.5.1 in f18 branch? (answer here, or poke me on irc)
In that spirit, I failed to follow my own advice, and lumped a whole bunch of stuff into a single commit, %changelog * Fri Apr 12 2013 Rex Dieter <rdieter> - 1.6.0-2 - %%build: revert back to --with-pam-dir=/%%{_lib}/security/ (#951456) - %%build: drop --enable-gcov (developer-only option, not needed here) - %%files: track abi (lib sonames) closer - drop unused patches - -pam: drop extra %%doc stuff (included already in Required base pkg) - -devel: drop explicit Requires: libmatekeyring-devel - use %%caps(cap_ipc_lock=ep) .../mate-keyring-daemon (see also #668831)
Rex, I am glad to have caught your attention ;) Could you pls also fix https://bugzilla.redhat.com/show_bug.cgi?id=896130 , to get the whole mate keyring framework working with lightdm?
mate-keyring-1.6.0-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mate-keyring-1.6.0-2.fc19
mate-keyring-1.5.1-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mate-keyring-1.5.1-2.fc18
mate-keyring-1.5.1-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mate-keyring-1.5.1-2.fc17
Package mate-keyring-1.6.0-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mate-keyring-1.6.0-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5650/mate-keyring-1.6.0-2.fc19 then log in and leave karma (feedback).
mate-keyring-1.6.0-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
mate-keyring-1.5.1-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
mate-keyring-1.5.1-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.