I checked to ensure the username and password are valid. I commented out Mac address, LDM_USERNAME, and LDM_PASSWORD. The thin client was then presented with a login screen. I logged in using the same credentials in lts.conf.
I then returned lts.conf to the auto-login configuration. Trying Auto-login again, I checked /var/log/auth.log. There were no entries in the auth.log. There were entries in daemon.log included below: daemon.log Nov 13 19:19:58 ltsp1 dhcpd: DHCPDISCOVER from 00:0f:20:28:75:8d via eth0 Nov 13 19:19:58 ltsp1 dhcpd: DHCPOFFER on 192.168.0.2 to 00:0f:20:28:75:8d via eth0 Nov 13 19:20:02 ltsp1 dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.254) from 00:0f:20:28:75:8d via eth0 Nov 13 19:20:02 ltsp1 dhcpd: DHCPACK on 192.168.0.2 to 00:0f:20:28:75:8d via eth0 Nov 13 19:20:02 ltsp1 in.tftpd[25548]: tftp: client does not accept options Nov 13 19:20:09 ltsp1 dhcpd: DHCPDISCOVER from 00:0f:20:28:75:8d via eth0 Nov 13 19:20:09 ltsp1 dhcpd: DHCPOFFER on 192.168.0.2 to 00:0f:20:28:75:8d via eth0 Nov 13 19:20:09 ltsp1 dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.254) from 00:0f:20:28:75:8d via eth0 Nov 13 19:20:09 ltsp1 dhcpd: DHCPACK on 192.168.0.2 to 00:0f:20:28:75:8d via eth0 Nov 13 19:20:10 ltsp1 dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.254) from 00:0f:20:28:75:8d via eth0 Nov 13 19:20:10 ltsp1 dhcpd: DHCPACK on 192.168.0.2 to 00:0f:20:28:75:8d via eth0 Nov 13 19:20:10 ltsp1 nbdrootd[25562]: connect from 192.168.0.2 (192.168.0.2) Nov 13 19:20:10 ltsp1 nbd_server[25563]: connect from 192.168.0.2, assigned file is /opt/ltsp/images/i386.img Nov 13 19:20:10 ltsp1 nbd_server[25563]: Size of exported file/device is 146518016 Nov 13 19:20:17 ltsp1 ldminfod[25565]: connect from 192.168.0.2 (192.168.0.2) ... The thin client remains hung up at this point. The thin client screen is black, with a 'X' (mouse cursor). The mouse cursor is response to movement of the mouse on the thin client. Anything else I should I do? -- autologin doesn't work https://bugs.launchpad.net/bugs/161794 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
