A
A
Alexander Zharchenko2019-10-24 13:34:07
linux
Alexander Zharchenko, 2019-10-24 13:34:07

How to restore Linux Mint user login in graphical mode?

Freshly installed Linux Mint won't let you log in to a newly created user :)
Tobish was originally a user admin2 , after which a user was created from under him through the console . When you try to enter the user user - a dark screen lights up with a cursor on it and then everything returns to the window with the list of users.
If you create users with other logins, then the same thing happens. Nothing is created in the /home/user folder . Through time and she herself is not created. The user is present in /etc/passwd .
Through Ctrl + Shift + F1 from the window with the list of users, the console works normally and the user walks normally in it.
Tobish question, rather, is how to pull the contents into the /home/user folder . This will possibly resolve the issue.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
V
Vitaly Karasik, 2019-10-24
@exxxcitation1

Correct answer: The user's home directory was owned by root, which prevented the user from logging into XWindow.
chown -R user.user /home/user
solved the problem (period and colon are interchangeable in this command).
Details:
Why did this happen? Apparently the home directory was manually created by root. For some reason in Ubuntu and forks useradd doesn't create a directory by default, you have to add '-m':
useradd -m newuser
Why did it interfere with login? Because with graphical login, the system wants to create different files in the home directory (security cookies, configuration, ...). If this fails due to lack of write permissions, the login is unsuccessful.
About users and rights -downloads.naulinux.ru/pub/NauLinux/desktop/52/i386...

R
Ronald McDonald, 2019-10-24
@Zoominger

The user is present in /etc/passwd.

Does he have a home directory? Created? Rights granted? If created through useradd, then, in theory, everything should be.

Z
Zenko, 2019-10-24
@Zenko

To get started, look at the xorg logs: /var/log/Xorg.0.log
Most likely the problem is in ~/xsessionrc, it starts xorg and a shell. If you edited xsessionsrc in windows, it's better to run through dos2unix or through sed, replace the Windows carriage return with Linux. In any case, dig into this file. The problem is most likely there.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question