28

I installed Ubuntu 16.04 (dual boot with Win 10) and it doesn't login after. I upgraded from Ubuntu 15.10 via update-manager

I have tried old workarounds for previous versions, like:

  • dpkg-reconfigure lightDM
  • chown user:user .Xauthority
  • chmod 666 .Xauthority
  • chmod a+wt /temp
  • mv .Xauthority smth
  • apt-get install ubuntu-session
  • Reinstalling Nvidia Drivers

Any suggestions appre

Java Jedi
  • 281

5 Answers5

32

I was in the same situation as you.

I did not reinstall nvidia drivers but remove it.

sudo apt-get purge nvidia*

And it worked.

d a i s y
  • 5,551
Nuno
  • 321
8

On all my systems (all had the same problem) the solution was:

  • Switch to console using Ctrl+Alt+F1
  • Login to text console (your username is enough if your system only has one user. otherwise you will need root user or sudo)
  • rm /home/*/.Xauthority
  • reboot
Daniel Alder
  • 2,612
3

I ran into the same problem on my upgrade to 16.04 from 15.10. I recalled that during the upgrade, there was a prompt regarding UEFI Secure Boot options. I checked my BIOS settings and sure enough, Secure Boot was set to "Windows Only". I selected "Other OS" from the list (your options may be different) and booted normally. All fixed.

Have not seen any other mentions of this fix so hopefully this will help.

bennsarrow
  • 31
1

I have this problem to. This problem reason is the new Unity match with 4.4.0 kernel version, and your kernel version same as 4.2.x now You have 2 solution for this problem:

  1. temp: install another desktop env same as gnome,lxde,or etc...
  2. or update the kernel.

for run the command before or after loop ctrl+alt+F1:

for check kernel version: send this command

$ uname -a

and fore update kernel :

http://ubuntuhandbook.org/index.php/2016/01/how-to-install-linux-kernel-4-4-in-ubuntu/

for install other desktop env googling about your desktop env.

A1Gard
  • 260
0

I just tried Nuno's idea.. Negative for me.. still stuck in the login loop on Console-7.. But, able to log in via console 1 (TTY1).. I also ran into this back when i went the route of 12.10 to 13.x (both), and it landed in the same loop.. Only workaround I could find, was using an old "Installed" software list from Synaptic, doing a fresh install of 13.04, and also doing the same when i bumped up to 15.04. , getting Synaptic loaded 1st, and then reading in the old software list.

Stephen Griswold
  • 1