Leap Login Issues

Referring to a. and b. that I’ve marked in your comment:

a. what does “at log” mean?

b. what does “in the command line” mean?
.
.
Check this. Log in at a command line (as root user), then execute the command:

cat /etc/passwd

Each line in the passwd (text) file is a unique user entry - there will be many entries. Here’s a sample user entry (truncated). The username is first entry on each line, followed by a colon char:

tom:x:1000:1000: …

Look for your username. Is it lower-case? All upper-case? Mixed case? It matters, because usernames are case-sensitive in Unix | Linux.

tom:
TOM:
tOM:
ToM:
… each of those is a unique and different username. Each user, at login, must use proper capitalization. Traditionally, Unix | Linux recommends all lower-case.

Now jot down the username. Then execute:

cat /etc/shadow

Look for your username. After it, there is a colon char. The next entry is your encrypted password. Is the first character in password an exclamation mark (!) ??

If a password field starts with an exclamation mark (!) , it means that the password is locked. Sample locked:

myuser:!$1$khkWa1Nz…

Sample not locked

myuser:$1$khkWa1Nz…

As there seem to be confusion on what the Username in fact is, look it up in /etc/passwd

Hi @aggie … I created three test users to provide a real world example

“tUSEr” password is locked.

# cat /etc/passwd | grep -i tuser
tuser:x:1002:100:tuser:/home/tuser:/bin/bash
tUSEr:x:1004:100:another test:/home/tUSEr:/bin/bash
TUSER:x:1003:100:test user:/home/TUSER:/bin/bash

# cat /etc/shadow | grep -i tuser
tuser:$6$AenCgRwJwg...RWU/F/:20119:0:99999:7:::
tUSEr:!$6$PmaAnzNIa...yp33vd1:20206:0:99999:7:::
TUSER:$6$9dGPjcs0Ac...rLjFD1:20206:0:99999:7:::
#

Does the user (which you cannot use for login) have a valid home directory?

Off topic!

You could expand that into

cat /etc/passwd | cat | grep -i tuser | cat

:rofl:

Alright so after being able to login at tty as root, I was from there able to login as my username. A quick peek back at sign in still won’t let me in, same issue happening.

But back at the login in tty it also says “-- : /home/” change directory failed: No such file or directory Logging in with home=“/”."

Looks like it doesn’t! Any chance it’s lurking around somewhere or is it lost?I’ve tried rolling back still not there.

As root, what is shown by the following?
ls -la /home
Also, check
df

As far as I know the openSUSE standard snapper configuration does not include the /home-area. So if anything changed in /home you might not be able to undo it by rolling back.

First of all do

cat /etc/passwd

The line which starts with the name of the not-working user should show the path of that users /home-directory as well. Beware that Linux is case-sensitive. So if you look for that /home-directory use the exact spelling.

If that directory exists make sure it is owned by the user and that the user has full access (rwx) to it.

cat /etc/passwd for the user shows :x:1000:100::/home/:/bin/bash

ls -la /home shows
Total 0
drwxr-xr-x 1 root root 0 Dec 30 13:09
drwxr-xr-x-1 root root 156 Dec 30 13:09

df shows lots of stuff, nothing I understand or know what to look for.

Also of note. While I was able to get into yast and create a new user and login, after powering off and back on, that user is gone, and the old user password that I changed has reverted back to the original.

You’re missing user home directories.

This user has /home/ assigned as her/his home directory!

How did you create that user and set that home directory?

Correct. Is it gone forever or hiding?

The user’s home directory doesn’t exist, so you’ll need to start over by creating a new primary user. Remove the existing user associated with UID 1000

userdel -r <username>

Add the user again

useradd -m <username>

then set a password for the user

passwd <username>

Follow the prompts given there. When you are next at the login screen, you should be able to login as that user.

1 Like