Comment 7 for bug 1723826
Revision history for this message
| Cefn (6-launchpad-net-cefn-com) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I found a workaround for my case, which I encountered yet again in Bionic :(
Running the following command
keyctl link @u @s
...made the session keyring and the user keyring be linked. My interpretation is that one part of the routine tries to first put the key into the session keyring and then tries to use the user keyring to unlock it, which of course doesn't work. Surely this must be an easy fix to put in to the routine?