[arch-general] xflock4 and pambase
Hi, I'm uncertain, if I should file a bug report or if it's up to the user. After running xflock4 I can't unlock the screen anymore. I suspect that this is related to the pambase update. I noticed that e.g. cinnamon-screensaver provides a pam.d file, but the package xfce4-session, which provides xflock4 doesn't. $ pacman -Qo /usr/bin/xflock4 /usr/bin/xflock4 is owned by xfce4-session 4.12.1-11 $ pacman -Ql xfce4-session | grep pam.d $ pacman -Ql cinnamon-screensaver | grep pam.d cinnamon-screensaver /etc/pam.d/ cinnamon-screensaver /etc/pam.d/cinnamon-screensaver Should I fix it myself or is a bug report within reason? Regards, Ralf
Op ma 11 feb. 2019 19:14 schreef Ralf Mardorf via arch-general < arch-general@archlinux.org:
Hi,
I'm uncertain, if I should file a bug report or if it's up to the user.
After running xflock4 I can't unlock the screen anymore. I suspect that this is related to the pambase update. [...]
Should I fix it myself or is a bug report within reason?
Give it a try first; if it works with a correct pam file in place: it's a packaging bug. OTOH, it could be a bug in your config, in that case a bug report is probably unnecessary. Mvg, Guus Snijders
Hi, if I try to unlock the screen after running xflock4 by an fbpanel menu entry or from command line, validation of the password fails. The language settings are en_US.utf8 The keyboard layout is German. However, the keyboard layout seems not to be related to the issue. On Tue, 2019-02-12 at 07:22 +0100, Guus Snijders via arch-general wrote:
Op ma 11 feb. 2019 19:14 schreef Ralf Mardorf:
After running xflock4 I can't unlock the screen anymore. I suspect that this is related to the pambase update. [...]
Should I fix it myself or is a bug report within reason?
Give it a try first; if it works with a correct pam file in place: it's a packaging bug. OTOH, it could be a bug in your config, in that case a bug report is probably unnecessary.
I successfully used xflock4 for years. It stopped working this year. It is/was not used with Xfce4. I'm running the openbox window manager without a desktop environment. After skimming /usr/share/doc/Linux-PAM/index.html I first tested: $ cat /etc/pam.d/xflock4 #%PAM-1.0 auth include system-auth account include system-auth password include system-auth session include system-auth Since I'm using lightdm, which optional depends on accountsservice, which is required by cinnamon-screensaver, I then tested a copy from the cinnamon-screensaver's config: $ cat /etc/pam.d/xflock4 #%PAM-1.0 auth include system-auth auth optional pam_gnome_keyring.so account include system-auth password include system-auth session include system-auth Both don't solve the issue, but they might be completyl wrong ;). FWIW I never run cinnamon-screensaver or another screensaver, depending on the work I'm doing, I enable screen blanking without locking the screen, or never let the screen take a rest at all. I used xflock4 on demand. For the moment I migrated to slock, which does work without an issue, but unfortunately doesn't provide a clock, one of the features xflock4 does provide. Now I wonder which of my configs might have become buggy, that xflock4 stopped working properly. Regards, Ralf
I just noticed this: $ pacman -Qi xfce4-session | grep -A 4 Optional\ Deps | tail -2 xlockmore: for locking screen with xflock4 [installed] slock: for locking screen with xflock4 [installed] It's indeed xlock, that is and should be used by xflock4, furthermore xlock suffers from the validation failure, too. Btw. I noticed it because I run something posted by Ralph Corderoy [1]. $ pactree -ld1 -r pam | sed 1d | xargs -rtn1 pkgfile -l |& egrep $'\t''/etc/pam\.d/.|^pkgfile' | tail -1 pkgfile -l xlockmore So I tested $ sudo cp -ai /etc/pam.d/cinnamon-screensaver /etc/pam.d/xlock and this actually solved the issue for xlock, as well as for xflock4 :). I'll file a bug report against xlockmore later. Regards, Ralf [1] On Mon, 11 Feb 2019 16:32:24 +0000, Ralph Corderoy wrote:
pactree -ld1 -r pam | sed 1d | xargs -rtn1 pkgfile -l |& egrep $'\t''/etc/pam\.d/.|^pkgfile'
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
participants (2)
-
Guus Snijders
-
Ralf Mardorf