Ubuntu 20.04 user not listed to login

Question

I recently upgraded to Ubuntu 20.04 and today, after turning on my computer, by default, Ubuntu showed that welcome screen where you create your user and whatever. I thought my OS crashed because it did not show the login screen.

So I created a new user, and noted that all my applications were already installed in this distro, so I clicked on logout, and to login again, my real user was not listed, but if I click on "Not listed?" and type my credentials, I can log in normally into my current user.

Pretty weird.

This is my Settings > User page, this user on the print is the one I created, but the one that's my real user which I am logged in rn, it's not here aswell.

Have anyone faced this issue before?

Edit1 - my /etc/passwd

root:x:0:0:root:/root:/usr/bin/zsh
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
irc:x:39:39:ircd:/var/run/ircd:/usr/sbin/nologin
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologin
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
systemd-network:x:100:102:systemd Network Management,,,:/run/systemd:/usr/sbin/nologin
systemd-resolve:x:101:103:systemd Resolver,,,:/run/systemd:/usr/sbin/nologin
systemd-timesync:x:102:104:systemd Time Synchronization,,,:/run/systemd:/usr/sbin/nologin
messagebus:x:103:106::/nonexistent:/usr/sbin/nologin
syslog:x:104:110::/home/syslog:/usr/sbin/nologin
_apt:x:105:65534::/nonexistent:/usr/sbin/nologin
tss:x:106:111:TPM software stack,,,:/var/lib/tpm:/bin/false
uuidd:x:107:114::/run/uuidd:/usr/sbin/nologin
tcpdump:x:108:115::/nonexistent:/usr/sbin/nologin
avahi-autoipd:x:109:116:Avahi autoip daemon,,,:/var/lib/avahi-autoipd:/usr/sbin/nologin
usbmux:x:110:46:usbmux daemon,,,:/var/lib/usbmux:/usr/sbin/nologin
rtkit:x:111:117:RealtimeKit,,,:/proc:/usr/sbin/nologin
dnsmasq:x:112:65534:dnsmasq,,,:/var/lib/misc:/usr/sbin/nologin
cups-pk-helper:x:113:120:user for cups-pk-helper service,,,:/home/cups-pk-helper:/usr/sbin/nologin
speech-dispatcher:x:114:29:Speech Dispatcher,,,:/run/speech-dispatcher:/bin/false
avahi:x:115:121:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/usr/sbin/nologin
kernoops:x:116:65534:Kernel Oops Tracking Daemon,,,:/:/usr/sbin/nologin
saned:x:117:123::/var/lib/saned:/usr/sbin/nologin
nm-openvpn:x:118:124:NetworkManager OpenVPN,,,:/var/lib/openvpn/chroot:/usr/sbin/nologin
hplip:x:119:7:HPLIP system user,,,:/run/hplip:/bin/false
whoopsie:x:120:125::/nonexistent:/bin/false
colord:x:121:126:colord colour management daemon,,,:/var/lib/colord:/usr/sbin/nologin
geoclue:x:122:127::/var/lib/geoclue:/usr/sbin/nologin
pulse:x:123:128:PulseAudio daemon,,,:/var/run/pulse:/usr/sbin/nologin
gnome-initial-setup:x:124:65534::/run/gnome-initial-setup/:/bin/false
gdm:x:125:130:Gnome Display Manager:/var/lib/gdm3:/bin/false
jvbs:x:1000:1000:João Vitor,,,:/home/jvbs:/usr/bin/zsh
nvidia-persistenced:x:126:133:NVIDIA Persistence Daemon,,,:/nonexistent:/usr/sbin/nologin
systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
mysql:x:127:135:MySQL Server,,,:/nonexistent:/bin/false
joaovitor:x:1001:1001:João Vitor,,,:/home/joaovitor:/bin/bash

Thanks!

Answer 1

I had the same issue.

To fix that I did these steps in a terminal:

• sudo su we need to be superuser
• cd /var/lib/AccountsService/users here we go to the service that shows users, issue is here (at least in my case)
• you should see multiple files, one for each of your users, including the old one that is not showed in your screen. In this file check the value of SystemAccount. If it's true, then this is the issue: it should be false.
• if it does not help you, simply check differences between users files, the one that works with ones that don't. Also check that Icon path is correct.
• don't forget to exit su, and reboot after each try. Good luck, it took 3h digging before a fixed my issue.

Answer 2

I was facing the same issue after uninstalling zsh. Your default user's (jvbs–João Vitor) default shell is zsh, so was mine. I changed it using cmd sudo --shell /bin/bash username from zsh to bash, after logging out and logging in again my issue was fixed.
Hope this works for you too!

Answer 3

I got this error while I was trying to install zsh on Ubuntu 20.04 Command : sudo su was throwing error ("no such file or directory"). So at first I fixed this problem by editing root configuration on /etc/passwd file

It was like this before: root:x:0:0:root:/root:/usr/bin/bash

I changed it to: root:x:0:0:root:/root:/bin/bash

It fixed my sudo su error. Then I followed the steps recommended by Richard Haddad up there. It worked. Thanks.

Answer 4

I had this problem yesterday. Installing zsh system wide solved the problem. I don't have enough reputation to upvote appropriate responses but sudo apt get install zsh solved it.

Answer 5

Try finding your old account in the password file, then go change (an):x:1000:1000... (an) is your account name. I used sudo vipw in 19, but I'm not so sure about 20.04.

Answer 6

I think that the issue was triggered somehow after setting zsh as default shell. I followed comments in this page and it resolved the issue for me. I first switched back to bash and then updated /var/lib/AccountsService/users/... as suggested.