pinentry-gnome3: (libgcrypt): Cannot allocate memory

Andreas Stieger andreas.stieger at gmx.de
Fri Jun 5 00:06:01 CEST 2015


Hello,

As I was packaging pinentry 0.9.3 with the new /usr/bin/pinentry-gnome3
I noticed the following:

$ /usr/bin/pinentry-gnome3
OK Your orders please
getpin
couldn't lock 16384 bytes of memory (libgcrypt): Cannot allocate memory
ERR 83886179 canceled

strace:

mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7efc75498000
mmap(NULL, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x7efc75494000
mlock(0x7efc75494000, 16384)            = -1 ENOMEM (Cannot allocate memory)
write(2, "couldn't lock 16384 bytes of mem"..., 72couldn't lock 16384
bytes of memory (libgcrypt): Cannot allocate memory

This is on a system with a fairly standard limit:
max locked memory       (kbytes, -l) 64

Where would we start looking to debug and look for a possible solution?
Do you think the gnome3 variant could receive a change to stay below a
64k lock limit?

openSUSE tracks this in:
https://bugzilla.opensuse.org/show_bug.cgi?id=933687

Andreas



More information about the Gnupg-devel mailing list