Opened 3 years ago
#20868 new defect
Automated login not working on Arch Linux guest of a Windows host
| Reported by: | MAnantharaman | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.1.32 |
| Keywords: | pam_vbox | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
I followed instructions in https://www.virtualbox.org/manual/ch09.html#autologon to be able to login automatically on my Arch Linux host under a Windows 10 host, providing credentials as explained for Windows guests (not described for Linux guests), which shows in syslog on the Linux guest as ...
pam_vbox_setcred called, iFlags=0x4 pam_vbox_setcred: argv[0] = debug
but pam_vbox is unable to subsequently retrieve the credentials leaving the following error in syslog:
pam_vbox: 6.1.32r149290, running on amd64 pam_vbox_init: runtime initialized pam_vbox_init: guest lib initialized pam_vbox_init: rhost=<none>, tty=:0, prompt=<none> her dbus-daemon[2156]: Successfully activated service 'org.a11y.atspi.Registry' her SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry pam_vbox_read_prop: read key "/VirtualBox/GuestAdd/PAM/CredsWait"="1" pam_vbox_read_prop: read key "/VirtualBox/GuestAdd/PAM/CredsWait" with rc=VINF_SUCCESS pam_vbox_read_prop: read key "/VirtualBox/GuestAdd/PAM/CredsWaitTimeout" with rc=VERR_NOT_FOUND pam_vbox_read_prop: read key "/VirtualBox/GuestAdd/PAM/CredsMsgWaiting" with rc=VERR_NOT_FOUND Showing message "Waiting for credentials ..." (type 4) pam_vbox_check_creds: could not query for credentials! rc=VERR_PERMISSION_DENIED. Aborting pam_vbox_authenticate: overall result rc=VERR_PERMISSION_DENIED
Note:
See TracTickets
for help on using tickets.

