Ok, this problem is reproducible:
Done with a Virtualbox VM, but most likely applies to physical installs too...
- Boot SliTaz-4.0.iso
- Choose "SliTaz Live" from LiveCD boot menu
- Open SliTaz Panel as root and do an install to hdd using default users/passwds
- Shutdown after successful installation
- Remove LiveCD
- boot into the new install and login as tux (no passwd)
- Open SliTaz Panel as root
- Select Settings Menu -> Users
- Add new user Nicolas with no passwd
- Delete user tux
- Select Boot Menu to edit slim.conf
- Set default_user to Nicolas
- Save slim.conf
- Close SliTaz Panel
- Logout (Close X session) and Nicolas will appear to be default user at login screen.
- Logging in and out repeatedly still has Nicolas as default user until the next reboot... when tux rises from the dead.
- Reinstate Nicolas as default_user in slim.conf and it will hold across sessions, until next reboot, when tux is back again.
Tux now has a slightly different numerical user id of 1000:100 (like LiveCD user), instead of 1000:1000 (like with hdd install).
Maybe this user id is handled differently in /etc/init.d/bootopts.sh?
There are probably other sequences which produce this scenario, like using your own user id instead of tux during installation, then adding tux manually (or he invites himself back on his own).
Not sure of what the flow-on effects might be (groups and permissions, etc), but a clean installation is probably a good option.