I noticed this behaviour after this two events: some days ago I shared a directory with samba. Everything went fine, except that having two networks I just couldn't see the shared directory in another windows machine, but that is another problem.
Today I installed a new printer and connected to 127.0.0.1:631 (cups), and after that I could not sudo, so rebooted the computer. After reboot I couldn't login, so I restarted in recovery mode and then I realized that three files in /var/lib/samba had changed this day, so I renamed them and voilá, I could login again.
The three files that were changed today were:
/var/lib/share_info.tdb
/var/lib/secrets.tdb
/var/lib/passwd.tdb
After login in successfully I checked /var/lib/samba and sectrets.tdb and passdb.tdb were recreated and the md5sum is different from the old ones. Share_info.tdb was not recreated, and seeing the date it seems that registry.tdb and ntprinters.tdb were touched or recreated again.
This bug is nasty because you just can't login, and if that happens to someone without another computer to check the solution then is hard to fix it.
I noticed this behaviour after this two events: some days ago I shared a directory with samba. Everything went fine, except that having two networks I just couldn't see the shared directory in another windows machine, but that is another problem.
Today I installed a new printer and connected to 127.0.0.1:631 (cups), and after that I could not sudo, so rebooted the computer. After reboot I couldn't login, so I restarted in recovery mode and then I realized that three files in /var/lib/samba had changed this day, so I renamed them and voilá, I could login again.
The three files that were changed today were: share_info. tdb secrets. tdb
/var/lib/
/var/lib/
/var/lib/passwd.tdb
After login in successfully I checked /var/lib/samba and sectrets.tdb and passdb.tdb were recreated and the md5sum is different from the old ones. Share_info.tdb was not recreated, and seeing the date it seems that registry.tdb and ntprinters.tdb were touched or recreated again.
This bug is nasty because you just can't login, and if that happens to someone without another computer to check the solution then is hard to fix it.