[mythtv-users] Xwindows authentication failure after playing a DVD

[Don Brett]

On 11/16/2019 2:54 PM, Don Brett wrote:
> This might be a bit off-topic; if so, please point me elsewhere.
>
> I have MythTV on Ubuntu-Mate, 18.04, which works quite well.  I copied 
> a family DVD onto Myth/video's and tried to play it; screen went 
> black, "Please wait...." was displayed, and it stopped there. I logged 
> in remotely and tried to kill x (sudo service lightdm stop).  The TV 
> screen went black and displayed "Started bpfilter" at the top left 
> corner.
>
> I'm not sure I recall all the steps, but I tried "sudo startx" 
> manually.  It partially started and gave this message:
>
> "You must be a member of the "mythtv" group before starting any mythtv 
> applications.  Would you like to automatically be added to the group?  
> (Note: sudo access required)"
>
> I answered "No" and it didn't work, so I pressed the reset button. 
> After reboot, x-windows tries to start and displays a password 
> dialogue box.  If I enter the correct password, it goes black for a 
> few seconds, then returns back to the same display and dialogue.  If I 
> enter an incorrect password, it gives an an "Invalid password..." 
> message and returns to the same dialogue.
>
> Not sure where to go from here, any suggestions?
>
> Don
>
> Extra information:
>
> don at johnny:~$ id mythtv
> uid=126(mythtv) gid=133(mythtv) 
> groups=133(mythtv),20(dialout),24(cdrom),27(sudo),29(audio),44(video),1000(don),1002(lirc)
> don at johnny:~$ groups mythtv
> mythtv : mythtv dialout cdrom sudo audio video don lirc
>
> don at johnny:~$ id don
> uid=1000(don) gid=1000(don) 
> groups=1000(don),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),118(lpadmin),128(sambashare),133(mythtv),1002(lirc)
> don at johnny:~$ groups don
> don : don adm cdrom sudo dip plugdev lpadmin sambashare mythtv lirc
>
>
> From /var/logs:
>
> lightdm.log has this at the end:
> ...
> [+366.97s] DEBUG: Continue authentication
> [+368.91s] DEBUG: Session pid=3387: Authentication complete with 
> return value 7: Authentication failure
> [+368.91s] DEBUG: Authenticate result for user don: Authentication 
> failure
> [+368.91s] DEBUG: Greeter start authentication for don
> [+368.91s] DEBUG: Session pid=3387: Sending SIGTERM
> [+368.91s] DEBUG: Session pid=3493: Started with service 'lightdm', 
> username 'don'
> [+368.91s] DEBUG: Session pid=3387: Exited with return value 1
> [+368.91s] DEBUG: Seat seat0: Session stopped
> [+368.92s] DEBUG: Session pid=3493: Got 1 message(s) from PAM
> [+368.92s] DEBUG: Prompt greeter with 1 message(s)
>
> auth.log has this at the end:
> ...
> Nov 16 14:21:30 johnny systemd-logind[956]: New session c7 of user 
> lightdm.
> Nov 16 14:23:34 johnny lightdm: pam_unix(lightdm:auth): authentication 
> failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=don
> Nov 16 14:23:34 johnny lightdm: pam_winbind(lightdm:auth): getting 
> password (0x00000388)
> Nov 16 14:23:34 johnny lightdm: pam_winbind(lightdm:auth): 
> pam_get_item returned a password
> Nov 16 14:23:34 johnny lightdm: pam_winbind(lightdm:auth): request 
> wbcLogonUser failed: WBC_ERR_AUTH_ERROR, PAM error: PAM_USER_UNKNOWN 
> (10), NTSTATUS: NT_STATUS_NO_SUCH_USER, Error message was: The sp
> Nov 16 14:23:36 johnny lightdm: PAM unable to dlopen(pam_kwallet.so): 
> /lib/security/pam_kwallet.so: cannot open shared object file: No such 
> file or directory
> Nov 16 14:23:36 johnny lightdm: PAM adding faulty module: pam_kwallet.so
> Nov 16 14:23:36 johnny lightdm: PAM unable to dlopen(pam_kwallet5.so): 
> /lib/security/pam_kwallet5.so: cannot open shared object file: No such 
> file or directory
> Nov 16 14:23:36 johnny lightdm: PAM adding faulty module: pam_kwallet5.so
> Nov 16 14:23:36 johnny lightdm: pam_succeed_if(lightdm:auth): 
> requirement "user ingroup nopasswdlogin" not met by user "don"
> Nov 16 14:25:24 johnny sudo:      don : TTY=pts/0 ; PWD=/home/don ; 
> USER=root ; COMMAND=/usr/bin/mc
> Nov 16 14:25:24 johnny sudo: pam_unix(sudo:session): session opened 
> for user root by don(uid=0)
>
Skip it, I searched for a couple of days and came up empty.  I rebuilt 
the box and have it back to normal, so all is well; except now I have to 
search for a boot drive backup scheme.

Don