Bug#914541: [libpam-modules-bin] unix_chkpwd should be SUID instead of SGID, otherwise kscreen_locker does not work

Control: tag -1 + unreproducible ¡Hola Steve! Please whenever you reassign a bug CC the receiving maintainers so we get an useful mail about it, thanks. El 2019-01-23 a las 08:38 -0800, Steve Langasek escribió: Control: reassign -1 libkscreenlocker5 That said, the problem could also be

Bug#914541: [libpam-modules-bin] unix_chkpwd should be SUID instead of SGID, otherwise kscreen_locker does not work

Control: reassign -1 libkscreenlocker5 Hello, On Sat, Nov 24, 2018 at 04:48:31PM +0100, hg42 wrote: > I ran into that quite a while ago, but wasn't using a screen locker or KDE > since, so I forgot about it. Now, with KDE and mostly hibernating my system, > it came back. > unix_chkpwd is

Bug#914541: [libpam-modules-bin] unix_chkpwd should be SUID instead of SGID, otherwise kscreen_locker does not work

As a workaround, I created a file /etc/apt/apt.conf.d/99hg-fix-unix_chkpwd # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914541 DPkg::Post-Invoke { "/usr/bin/stat -c '%n %a %U %G' /sbin/unix\_chkpwd ; chmod 4755 /sbin/unix\_chkpwd ; /usr/bin/stat -c '%n %a %U %G' /sbin/unix\_chkpwd"; };

Bug#914541: [libpam-modules-bin] unix_chkpwd should be SUID instead of SGID, otherwise kscreen_locker does not work

Package: libpam-modules-bin Version: 1.1.8-3.8 Severity: important --- Please enter the report below this line. --- I ran into that quite a while ago, but wasn't using a screen locker or KDE since, so I forgot about it. Now, with KDE and mostly hibernating my system, it came back.