On Tue, 2019-02-12 at 13:27 +0100, Ralf Mardorf via arch-general wrote: > I'll file a bug report against xlockmore later. Oops, it is already reported two times. https://bugs.archlinux.org/index.php?string=xlock&project=5&search_name=&type%5B%5D=&sev%5B%5D=&pri%5B%5D=&due%5B%5D=&reported%5B%5D=&cat%5B%5D=&status%5B%5D=open&percent%5B%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=&do=index https://bugs.archlinux.org/task/61704 https://bugs.archlinux.org/task/61715 No need to post my prewritten bug report: [xlockmore] needs a pam.d file for xlock After running xlock from command line, the screen can't be unlocked anymore. To solve the issue I run $ sudo cp -ai /etc/pam.d/cinnamon-screensaver /etc/pam.d/xlock see https://lists.archlinux.org/pipermail/arch-general/2019-February/046049.html
