After upgrade 19.04 to 19.10 user is no longer listed in settings or in gdm.

April 18th, 2011 #2
User: zvacet

Re: Add existing user to gdm

    You can do that from system>administration>users & groups>edit account and add it to gdm.Second way is from CLI following this guide.
see: ubuntuforums.org/showthread.php?t=1731264

does this solution no longer work now days? :)

there was a little joke, but seriously... " I can successfully login to my user." - it means that the user is present in the system.
and other settings if there was no backup - lost forever )

okey... maybe files in /etc/dconf/db/gdm.d - replacd by upgrade ?
check logs in /var/log/apt* history files

Hi, thanks for providing help :)

There is no gdm.d directory at /etc/dconf/db/gdm.d

Hi, thanks for providing help :)

There is no gdm.d directory at /etc/dconf/db/gdm.d

Sorry, typo.

There is no gdm.d directory at /etc/dconf/db/

Start-Date: 2019-11-07 20:20:48
Commandline: aptdaemon role='role-commit-packages' sender=':1.19746'
Upgrade: libwebkit2gtk-4.0-37:amd64 (2.24.4-0ubuntu0.19.04.1, 2.26.1-0ubuntu0.19.04.3), gir1.2-webkit2-4.0:amd64 (2.24.4-0ubuntu0.19.04.1, 2.26.1-0ubuntu0.19.04.3), unattended-upgrades:amd64 (1.10ubuntu5.1, 1.10ubuntu5.2), libjavascriptcoregtk-4.0-18:amd64 (2.24.4-0ubuntu0.19.04.1, 2.26.1-0ubuntu0.19.04.3), libwebkit2gtk-4.0-37-gtk2:amd64 (2.24.4-0ubuntu0.19.04.1, 2.26.1-0ubuntu0.19.04.3), libfribidi0:amd64 (1.0.5-3.1, 1.0.5-3.1ubuntu0.19.04.1), gir1.2-javascriptcoregtk-4.0:amd64 (2.24.4-0ubuntu0.19.04.1, 2.26.1-0ubuntu0.19.04.3)
End-Date: 2019-11-07 20:20:54

Start-Date: 2019-11-08 16:06:40
Commandline: aptdaemon role='role-commit-packages' sender=':1.20407'
Upgrade: python3-distutils:amd64 (3.7.3-1ubuntu1, 3.7.5-1~19.04), python3-lib2to3:amd64 (3.7.3-1ubuntu1, 3.7.5-1~19.04), python3-tk:amd64 (3.7.3-1ubuntu1, 3.7.5-1~19.04), python3-gdbm:amd64 (3.7.3-1ubuntu1, 3.7.5-1~19.04)
End-Date: 2019-11-08 16:06:42

Start-Date: 2019-11-10 07:23:12
Commandline: apt-get remove gnome-initial-setup
Remove: gnome-initial-setup:amd64 (3.34.1-1ubuntu1)
End-Date: 2019-11-10 07:23:13

Start-Date: 2019-11-12 18:07:35
Commandline: aptdaemon role='role-commit-packages' sender=':1.3126'
Upgrade: intel-microcode:amd64 (3.20190918.1ubuntu1, 3.20191112-0ubuntu0.19.10.2), libwebkit2gtk-4.0-37:amd64 (2.26.1-3, 2.26.2-0ubuntu0.19.10.1), gir1.2-webkit2-4.0:amd64 (2.26.1-3, 2.26.2-0ubuntu0.19.10.1), libjavascriptcoregtk-4.0-18:amd64 (2.26.1-3, 2.26.2-0ubuntu0.19.10.1), libwebkit2gtk-4.0-37-gtk2:amd64 (2.26.1-3, 2.26.2-0ubuntu0.19.10.1), gir1.2-javascriptcoregtk-4.0:amd64 (2.26.1-3, 2.26.2-0ubuntu0.19.10.1)
End-Date: 2019-11-12 18:08:00

Start-Date: 2019-11-12 18:14:08
Commandline: aptdaemon role='role-commit-packages' sender=':1.829'
Install: linux-image-5.3.0-22-generic:amd64 (5.3.0-22.24, automatic), linux-headers-5.3.0-22-generic:amd64 (5.3.0-22.24, automatic), linux-modules-extra-5.3.0-22-generic:amd64 (5.3.0-22.24, automatic), linux-headers-5.3.0-22:amd64 (5.3.0-22.24, automatic), linux-modules-5.3.0-22-generic:amd64 (5.3.0-22.24, automatic)
Upgrade: linux-headers-generic:amd64 (5.3.0.19.22, 5.3.0.22.26), linux-libc-dev:amd64 (5.3.0-19.20, 5.3.0-22.24), linux-image-generic:amd64 (5.3.0.19.22, 5.3.0.22.26), linux-signed-image-generic:amd64 (5.3.0.19.22, 5.3.0.22.26), linux-signed-generic:amd64 (5.3.0.19.22, 5.3.0.22.26), linux-generic:amd64 (5.3.0.19.22, 5.3.0.22.26)
End-Date: 2019-11-12 18:14:43

These are the logs from /var/log/apt/history.log

During the upgrade process I had an issue where I got stuck in the gnome initial setup, so I went into the grub menu and booted from the last functional kernel in recovery mode. I then deleted gnome initial setup and rebooted. Everything has worked since then except for this. May just need a clean install though.

If you are able to manually enter your username for logging in, then your user is defined in the system and cannot and need not be added again.

On the gdm greeter (the login screen) only those users are listed whose numeric User-ID is higher than a certain value. Maybe something has been changed during upgrade, and your user only met the old limit, but does not meet the new criteria?

What is the output of the commands

uname -a
lsb_release -crid
whoami
id
grep -i minimal /etc/gdm/gdm.conf
grep -i exclude /etc/gdm/gdm.conf

Hi Manfred, thanks for helping. Here is the output of the commands you wanted.

uname -a
> Linux evan-XPS-13-9360 5.3.0-22-generic #24-Ubuntu SMP Sat Nov 9 17:34:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -crid
>Distributor ID: Ubuntu
> Description: Ubuntu 19.10
> Release: 19.10
> Codename: eoan
whoami
> evan
id
> uid=1001(evan) gid=1001(evan)
> groups=1001(evan),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),117(lpadmin),128(sambashare)
 grep -i minimal /etc/gdm/gdm.conf
> grep: /etc/gdm/gdm.conf: No such file or directory
 grep -i exclude /etc/gdm/gdm.conf
> grep: /etc/gdm/gdm.conf: No such file or directory

Are there other users shown on the login greeter screen that can be selected for logging in?

What is the output of
grep evan /etc/passwd
gsettings list-recursively org.gnome.login-screen

hi Manfred, there are no other users listed on the greeter screen.

> grep evan /etc/passwd
evan:x:1001:1001:Evan,,,:/home/evan:bash

>gsettings list-recursively org.gnome.login-screen
org.gnome.login-screen allowed-failures 3
org.gnome.login-screen logo '/usr/share/plymouth/ubuntu-logo.png'
org.gnome.login-screen fallback-logo ''
org.gnome.login-screen banner-message-text ''
org.gnome.login-screen disable-restart-buttons false
org.gnome.login-screen enable-fingerprint-authentication true
org.gnome.login-screen enable-smartcard-authentication true
org.gnome.login-screen disable-user-list false
org.gnome.login-screen banner-message-enable false
org.gnome.login-screen enable-password-authentication true

The entry "evan:x:1001:1001:Evan,,,:/home/evan:bash" may be the culprit. "bash" is no valid shell program.

Run the command

chsh /bin/bash

and logout. Does this help?