KVPM pam_unix(sudo:auth): auth could not identify password for user

[Dan Coffey]

Can't launch KVPM in Kubuntu 18.04 beta
App is installed and gives password screen then fails

Linux MadMax 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

[Seth Arnold (seth-arnold)]

Hi Dan, can you please describe what you're doing, what you expected to happen, and what happened? Messages from logfiles might also be helpful.

Thanks

[Dan Coffey (tech-netharmonix)]

Hi Seth,

Kubuntu 18.04

uname -a
Linux MadMax 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

I was starting KVPM and it would quit after the password request was
entered.
with this error:
5/1/18 12:43 PM    sudo    pam_unix(sudo:auth): conversation failed
5/1/18 12:43 PM    sudo    pam_unix(sudo:auth): auth could not identify
password for [dcoffey]

I've not had a issue with any other commands at this point.

After a few apt updates KVPM is starting up without error.
5/1/18 12:47 PM    sudo     dcoffey : TTY=pts/13 ; PWD=/home/dcoffey ;
USER=root ; COMMAND=/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu_stub -
5/1/18 12:47 PM    sudo    pam_unix(sudo:session): session opened for
user root by (uid=0)
5/1/18 12:47 PM    sudo    pam_unix(sudo:session): session closed for
user root
5/1/18 12:47 PM    sudo     dcoffey : TTY=pts/13 ; PWD=/home/dcoffey ;
USER=root ; COMMAND=/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu_stub -
5/1/18 12:47 PM    sudo    pam_unix(sudo:session): session opened for
user root by (uid=0)
5/1/18 12:47 PM    kernel     sdf:
5/1/18 12:47 PM    lvmetad    WARNING: Ignoring unsupported value for cmd.

But when I quit KVPM syslog has the same error:

5/1/18 12:47 PM    sudo    pam_unix(sudo:session): session closed for
user root
5/1/18 12:47 PM    sudo    pam_unix(sudo:auth): conversation failed
5/1/18 12:47 PM    sudo    pam_unix(sudo:auth): auth could not identify
password for [dcoffey]

Dan

On 04/30/2018 10:04 PM, Seth Arnold wrote:
> Hi Dan, can you please describe what you're doing, what you expected to
> happen, and what happened? Messages from logfiles might also be helpful.
>
> Thanks
>
> ** Changed in: sudo (Ubuntu)
> Status: New => Incomplete
>
> ** Information type changed from Private Security to Public Security
>

[Steve Langasek (vorlon)]

There have been no changes to the authentication stack from the side of pam and sudo. If kvpm is calling sudo, and failing to call it in a context that has a tty available such that the user is never able to enter a password, this is not a bug in either pam or sudo but in kvpm.