Bug 231762 - security/gnome-keyring: couldn't lock 16384 bytes of memory (libgcrypt): Resource temporarily unavailable
Summary: security/gnome-keyring: couldn't lock 16384 bytes of memory (libgcrypt): Reso...
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-gnome (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-27 15:03 UTC by Mateusz Piotrowski
Modified: 2020-12-19 14:38 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (gnome)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mateusz Piotrowski freebsd_committer freebsd_triage 2018-09-27 15:03:17 UTC 
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
Comment 1 Ting-Wei Lan 2018-10-21 14:34:35 UTC 
(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.
Comment 2 Tobias C. Berner freebsd_committer freebsd_triage 2020-12-19 14:38:32 UTC 
Moin moin 

Please re-open if this is still an issue.


mfg Tobias