Ask Ubuntu is a question and answer site for Ubuntu users and developers. It only takes a minute to sign up.
Sign up to join this community
I've just installed Ubuntu 20.04 on my PC (this is a completely clean install) and I've had nothing but problems. Firstly it would keep booting into GRUB and absolutely nothing in BIOS settings fixed it. I had to reinstall Ubuntu to fix it.
Now I can't even log in! Every time I press enter after my password it takes me back to the login screen! Does anyone know how to fix it?
It seems to be an issue with the auto-login. One way to fix this is by disabling auto-login from the command prompt:
sudo nano /etc/gdm3/custom.confLine number 5 and 6 of custom.conf should be:
AutomaticLoginEnable=true
AutomaticLogin=[username]
where, [username] is the name of the user for auto-login. Change this to:
#AutomaticLoginEnable=true
#AutomaticLogin=[username]
Hit Ctrl + S to save, then reboot by hitting Ctrl+Alt+F1 and selecting restart from the login menu.
I found another solution in the comments on this article. Chrome remote desktop seems not to work well. From the login screen, I did Ctrl+Alt+F3 to get the command line, I logged in, then ran
sudo apt-get purge chrome-remote-desktop
Alt+F1 took me back to the login screen and I was able to login. Thanks to pRose there.
appstream error, comment out if /usr/bin/test -w /var/cache/app-info in file /etc/apt/apt.conf.d/50appstream. do apt-get update and apt-get upgrade and that should fix appstream and accept package maintainer config. Try logging after all the previous commands completed successfully.
chrome-remote-desktop solved the problem (after a reboot).
In Ubuntu 20.04 the reason for this login screen loop can also be in conflicting environment variables setup ($PATH).
In case PATH variable is assigned in several places simultaneously like:
/etc/environment/etc/profile~/.profile~/.bashrcPATH modifications should be in one place (~/.profile), not several. This might help.
JAVA_HOME to PATH in /etc/environment. I moved it to ~/.profile where all the other PATH modifications are and I can now log in.
The answer from Jonathan Lisic above was the most helpful of the many that I have had to go through today. This is a new Login Loop problem, and yes it does appear that the latest NVidia drivers on 20.04 LTS actually block the progress from Login Screen to the Desktop Screen if Automatic Login is active.
The editing using nano works, but I used Ctrl-O then Ctrl-X to save and exit, (as Ctrl-S was not available), and then I used shutdown -r 0 to restart the machine.
Worked fine.
After restart and successful login, I updated the Graphics Driver to the latest version of the NVidia proprietary drivers, from the GUI "Additional Drivers", and tested the login again.
Glad to report that the Login Loop has been eliminated.
When I tried Ctrl+Alt+F3 or F4, the screen froze and I had to press the power button to power off.
Instead, I simply chose the "Ubuntu on Wayland" option at the bottom right corner and I immediately logged in!
I had a similar login problem with Xubuntu 20.04.1 after an update. I figured out my disk is out of space. So I logged in via the text console (Ctrl+Alt+F3) and ran
sudo apt autoremove
then, I was able to log in normally.
I had the same issue, please try these steps:
Go to your recovery and log in as root by choosing the respective option in GUI.
Run:
sudo pam-auth-update
Hit YES and at the next prompt window select all stars and hit Enter so the changes will be applied.
Reboot and you will be fine.
Like you, I installed Ubuntu 20.04, spent half a day working on a project, then was unable to login the next day I booted up again in recovery mode and added a new user #useradd test then booted up again, tried to login as test - didn't work Switched back to the original user and it allowed me to login
From the login screen, press ctrl + alt + F3 to enter the grub mode, give the following commands:
sudo apt-get update
sudo apt-get dist-upgrade
sudo dpkg --configure -a
running these commands worked for me.
Nothing above worked in my Ubuntu. Ultimately I switched to command mode and restarted the default-device-manager.
View your device-manager:
cat /etc/X11/default-display-manager
In my case it was gdm3. After that type:
sudo service gdm3 restart
Now reboot the system. Hope this works!
Current Exprience
I'm using BackBox 20x (a pentasting version of ubuntu) on my other pc. It turns out this can also happen if you do not have enough space. Problem fixed after deleting some old files on terminal pressing ctrl + alt + F3 on login screen and then I deleted some old movies which I already watched. After that the issue was gone.
Previous Experience
This also happens on this pc I'm using now (Ubuntu 18x) apart from my other pc. When you modify the '.profile' file. Not sure why but resetting the .profile file to the previous version resolves this issue. Then if you wanna modify environment variables on your system just use .bashrc file.
This happened to me after a reboot following a kernel version bump. I was using gdm3 as my display manager. I fixed it by switching to a tty login, installing lightdm, configuring it as my display manager, rebooting, logging in, setting gdm3 as the DM and rebooting again.
Ctrl-Alt-F3 (login as normal)sudo dpkg-reconfigure lightdm (choose lightdm in dialog)lightdm to ensure it workssudo dpkg-reconfigure gdm3 (choose gdm3in dialog)I do not know if installing lightdm was necessary or if just reconfiguring gdm3 would have done the trick, but at least it would have given me a usable system. After reconfiguring gdm3 logins started working again.
This fix doesn't rise to much more than mystic incantations as I have no idea what went wrong. Correlation isn't causation, but in addition to a broken display manager, something pretty comprehensively borked my Python3 installation at the same time, to the extent of having to nuke and reinstall.
