https://bugs.kde.org/show_bug.cgi?id=429348
Eli Schwartz <eschwa...@archlinux.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eschwa...@archlinux.org
--- Comment #6 from Eli Schwartz <eschwa...@archlinux.org> ---
It's correctly reported against KDE.
> This is caused by using the pam_deny module which Arch now used by default.
> You'll want to talk to the Arch packagers about it.
This is a fundamentally invalid argument; calling it a distro bug if KDE
produces invalid results when PAM contains an active pam_deny module that
rejected the authentication attempt, is missing all the points.
Unless the implication is that no one in their right mind would ever use a core
module distributed by the Linux-PAM project, it's KDE's job to handle the case
where the sysadmin is using it.
Pointing fingers at pam_deny is at best a workaround for people whose buggy KDE
setups are currently causing usability issues. The correct response is
therefore "this is a bug in KDE, but until a fix is available you may wish to
disable pam_deny from your current PAM stack".
As Patrick pointed out, the problem will just as well manifest on other
distros.
--
You are receiving this mail because:
You are watching all bug changes.
