Live bootale asks for a username and password

1. Did you setup any users in the chroot environment?

2. Did you change the "always ask for password" setting while customizing in chroot.

3. Linux Mint must have a default user. Out of curiosity, does that default user ID and default password work? (For example, I know Ubuntu uses "ubuntu" as the live session user, and the default password is blank. (If so, see 4a or 5d below) ).

4. Are you able to switch to a terminal TTY and login with the default user id and password?
4a. If you can login into a non-graphical shell running the Live session (using the default user id and default password), you might be able to use `journalctl -f` to see what the errors are.

5. Sometimes, during login, if gnome-shell crashes, it puts you back into the login screen. No matter how may times you enter the (correct) password, you are always taken back to the GDM screen. You may be experiencing this in your Live session. There are many causes. (Search for "login loop" on the internet for ideas on how to fix this).
5a. One cause might be the user's home directory is messed up (user is missing an .Xauthority file or there is a problem with the user's .bashrc file).
5b. Another cause I've experienced is not having a custom gnome-shell theme correctly setup. During login, gnome-shell crashes, but you don't see any errors, and the GDM screen simply reappears.
5c. Sometimes, mis-configured Nvidia drivers cause this problem.
5d. If you are able to SSH from another computer into the running Live session (using the default user id and default password), you might be able to use `journalctl -f` to see what the errors are.

6. Finally, a very basic question: are you sure you are booting into the ISO and not the currently installed OS on the computer?

I just experienced this yesterday when I edited a gschema *.xml configuration file in /usr/share/glib-2.0/schemas.
My edit had an error, and GDM kept bringing me back to the login screen.

I was able to fix it by logging onto another TTY (CRTL-ALT-F2) and fixing the error using the nano command-line text editor.
Then I switched back to GDM ((CRTL-ALT-F1) and was able to log in.

The lesson is, if there is any kind of error in any file needed to boot successfully into the desktop, you are taken back to the login screen.

Therefore, look into any configuration changes you have made and see if there are any mistakes, typos, etc.

Cubic PPA (cubic-wizard)
Thanks for answering.
when I get .iso at the first , every things are correct but create another .iso and bootable it , ask for a username and password ( I don't install Os yet ).
I logined onto another TTY but ask for a username and password.

This question was expired because it remained in the 'Open' state without activity for the last 15 days.