Bug ID | 933687 |
---|---|
Summary | pinentry-gnome3: (libgcrypt): Cannot allocate memory |
Classification | openSUSE |
Product | openSUSE Factory |
Version | 201505* |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Minor |
Priority | P5 - None |
Component | GNOME |
Assignee | bnc-team-gnome@forge.provo.novell.com |
Reporter | astieger@suse.com |
QA Contact | qa-bugs@suse.de |
CC | dmueller@suse.com, kstreitova@suse.com, puzel@suse.com, vcizek@suse.com |
Found By | --- |
Blocker | --- |
Just updating pinentry to 0.9.3 (SR#310364) which has a new /usr/bin/pinentry-gnome3 command. I noticed this: > $ /usr/bin/pinentry-gnome3 > OK Your orders please > getpin > couldn't lock 16384 bytes of memory (libgcrypt): Cannot allocate memory > ERR 83886179 canceled 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 ) = 72 So this is probably similar to bug 915931.