From this version, kbd contains `vlock` command (previously, provided by separated package, app-misc/vlock). Currently, the ebuild installs `vlock` binary if `pam` USE flag is enabled, but not PAM config for `vlock`. For this reason, `vlock` command does not work. I wrote the patch for this issue. https://github.com/gentoo/gentoo/pull/12480 In my test, the patch fixes the problem. Could you check & merge this? Reproducible: Always Steps to Reproduce: 1. emerge '>=kbd-2.1.0' with `pam` USE flag enabled 2. run `vlock` command Actual Results: I can not unlock the terminal and get error messages repeatedly. Expected Results: The terminal is locked and show password prompt. When I enter my password, the terminal is unlocked.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=20d156c15dd4deaf4976c21eda27eb3fc4e63a5e commit 20d156c15dd4deaf4976c21eda27eb3fc4e63a5e Author: Takeshi Ito <85nrdzgv@gmail.com> AuthorDate: 2019-07-20 07:16:50 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2019-07-26 08:26:09 +0000 sys-apps/kbd: fix pam config to be created for vlock Added pam eclass and create pam config file when `pam` flag is enabled. `vlock` command needs it to work correctly. Package-Manager: Portage-2.3.69, Repoman-2.3.16 Closes: https://bugs.gentoo.org/690746 Signed-off-by: Takeshi Ito <85nrdzgv@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/12480 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> sys-apps/kbd/kbd-2.1.0.ebuild | 3 +++ 1 file changed, 3 insertions(+)
