Attached is the journalctl.out.bz2, but it only shows that gnome-initial-setup is called and later it states that gnome-initial-setup is using the logname "x" which is what I was forced to use. I know that gnome-initial-setup is part of the problem because if you try to break out of it with Ctrl-Alt-Del, the exit screen says" "log out gnome-initial-setup Cancel or Exit?"
However, using your suggestion to check the /etc/passwd entries, I came up with a temporary solution: I removed all end user entries except for my logname, UID=1000, and the logname "x" entry. After comparing the various passwd fields the only one that was different (not counting the uid, gid) was the SHELL. I use /bin/ksh2020 whereas the "x" uses the default /bin/bash. When I change my logname's SHELL to bash, then I can cold boot and get a normal login screen. So I want to change this bug [or create a new one] that says: UID=1000 (first user, sudo user) can have a SHELL that is NOT /bin/bash. I have been using a SHELL of ksh93 or now ksh2020 since Ubuntu 14.04 or so. As long as there has been a .bash_profile in my home directory, I could log in and use all the ksh login files like .env and .profile without other system files like /etc/profile or bash complaining. Thanks for pursuing this new issue. ** Attachment added: "shows startup including references to gnome-initial-setup" https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1876141/+attachment/5365905/+files/journalctl.out.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876141 Title: before login screen the setup forces a new login name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1876141/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
