Summary: | security/gnome-keyring: couldn't lock 16384 bytes of memory (libgcrypt): Resource temporarily unavailable | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Mateusz Piotrowski <0mp> |
Component: | Individual Port(s) | Assignee: | freebsd-gnome (Nobody) <gnome> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Only Me | CC: | lantw44, tcberner |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(gnome) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
(In reply to Mateusz Piotrowski from comment #0) The error message came from a call to mlock, and mlock(2) man page says: [EAGAIN] Locking the indicated range would exceed the system limit for locked memory. Moin moin Please re-open if this is still an issue. mfg Tobias |
Whenever I use GNOME Keyring with Subversion I get the following error message: > couldn't lock 16384 bytes of memory (libgcrypt): Resource temporarily unavailable It does not prevent Subversion from using GNOME Keyring (everything works fine). Details: - FreeBSD 12.0-ALPHA6 r338797 amd64 - gnome-keyring-3.18.3_5 - subversion-gnome-keyring-1.10.2_4