Login problem on 18.04
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Fresh install of 18.04 on an Intel NUC. Worked at first but now when I get to the login screen, it takes about a minute before my keyboard and mouse respond. My password is not accepted on the first attempt but on the second it is. On finally being allowed to log in, I am presented with a purple screen with no desktop.
Edit: I managed to get back in via a hard reboot but that's not an ideal solution.
Edit 2: Complete shutdown followed by disconnecting from the mains allows me to start up normally next time. Reboot or REISUB leads to issues described above.
video from fail
login 18.04
edited Feb 12 at 16:52
Aktony
33
asked Apr 27 '18 at 15:30
LolwhitesLolwhites
2233616
add a comment |
Fresh install of 18.04 on an Intel NUC. Worked at first but now when I get to the login screen, it takes about a minute before my keyboard and mouse respond. My password is not accepted on the first attempt but on the second it is. On finally being allowed to log in, I am presented with a purple screen with no desktop.
Edit: I managed to get back in via a hard reboot but that's not an ideal solution.
Edit 2: Complete shutdown followed by disconnecting from the mains allows me to start up normally next time. Reboot or REISUB leads to issues described above.
video from fail
login 18.04
edited Feb 12 at 16:52
Aktony
33
asked Apr 27 '18 at 15:30
LolwhitesLolwhites
2233616
Check you memory and do an update!
– George Udosen
Apr 27 '18 at 16:10
Since the keyboard isn't recognised while booting, I can't get into recovery mode run a memory check.
– Lolwhites
Apr 27 '18 at 19:34
'My password is not accepted on the first attempt but on the second it is. On finally being allowed to log in, I am presented with a purple screen with no desktop.' Please mark yourself as affected by this bug, thanks! :)
– Ads20000
May 1 '18 at 0:06
add a comment |
Fresh install of 18.04 on an Intel NUC. Worked at first but now when I get to the login screen, it takes about a minute before my keyboard and mouse respond. My password is not accepted on the first attempt but on the second it is. On finally being allowed to log in, I am presented with a purple screen with no desktop.
Edit: I managed to get back in via a hard reboot but that's not an ideal solution.
Edit 2: Complete shutdown followed by disconnecting from the mains allows me to start up normally next time. Reboot or REISUB leads to issues described above.
video from fail
login 18.04
edited Feb 12 at 16:52
Aktony
33
asked Apr 27 '18 at 15:30
LolwhitesLolwhites
2233616
Fresh install of 18.04 on an Intel NUC. Worked at first but now when I get to the login screen, it takes about a minute before my keyboard and mouse respond. My password is not accepted on the first attempt but on the second it is. On finally being allowed to log in, I am presented with a purple screen with no desktop.
Edit: I managed to get back in via a hard reboot but that's not an ideal solution.
Edit 2: Complete shutdown followed by disconnecting from the mains allows me to start up normally next time. Reboot or REISUB leads to issues described above.
video from fail
login 18.04
login 18.04
edited Feb 12 at 16:52
Aktony
33
asked Apr 27 '18 at 15:30
LolwhitesLolwhites
2233616
edited Feb 12 at 16:52
Aktony
33
asked Apr 27 '18 at 15:30
LolwhitesLolwhites
2233616
edited Feb 12 at 16:52
Aktony
33
edited Feb 12 at 16:52
Aktony
33
edited Feb 12 at 16:52
Aktony
33
33
asked Apr 27 '18 at 15:30
LolwhitesLolwhites
2233616
asked Apr 27 '18 at 15:30
LolwhitesLolwhites
2233616
asked Apr 27 '18 at 15:30
LolwhitesLolwhites
2233616
2233616
Check you memory and do an update!
– George Udosen
Apr 27 '18 at 16:10
Since the keyboard isn't recognised while booting, I can't get into recovery mode run a memory check.
– Lolwhites
Apr 27 '18 at 19:34
'My password is not accepted on the first attempt but on the second it is. On finally being allowed to log in, I am presented with a purple screen with no desktop.' Please mark yourself as affected by this bug, thanks! :)
– Ads20000
May 1 '18 at 0:06
add a comment |
Check you memory and do an update!
– George Udosen
Apr 27 '18 at 16:10
Since the keyboard isn't recognised while booting, I can't get into recovery mode run a memory check.
– Lolwhites
Apr 27 '18 at 19:34
'My password is not accepted on the first attempt but on the second it is. On finally being allowed to log in, I am presented with a purple screen with no desktop.' Please mark yourself as affected by this bug, thanks! :)
– Ads20000
May 1 '18 at 0:06
Check you memory and do an update!
– George Udosen
Apr 27 '18 at 16:10
Check you memory and do an update!
– George Udosen
Apr 27 '18 at 16:10
Since the keyboard isn't recognised while booting, I can't get into recovery mode run a memory check.
– Lolwhites
Apr 27 '18 at 19:34
Since the keyboard isn't recognised while booting, I can't get into recovery mode run a memory check.
– Lolwhites
Apr 27 '18 at 19:34
'My password is not accepted on the first attempt but on the second it is. On finally being allowed to log in, I am presented with a purple screen with no desktop.' Please mark yourself as affected by this bug, thanks! :)
– Ads20000
May 1 '18 at 0:06
'My password is not accepted on the first attempt but on the second it is. On finally being allowed to log in, I am presented with a purple screen with no desktop.' Please mark yourself as affected by this bug, thanks! :)
– Ads20000
May 1 '18 at 0:06
add a comment |
3 Answers
3
active
oldest
votes
I ran into a very similar issue, but even a hard reset did not allow me to log in. The last thing I had done before the issue presented itself was install the indicator-multiload package.
I was lucky, and simply logging into a console (CTRL + ALT + F2) and uninstalling the package (sudo apt remove --purge indicator-multiload) fixed the problem.
I have not dived any deeper into this issue to see why (or even whether) this package caused said issue, but I postulate that it has something to do with the package's integration with the Gnome desktop.
Maybe you can try to think what packages you might have installed recently that could have interfered with Gnome and attempt to uninstall them. If doing so works, at least you can get back into your desktop environment and troubleshoot further.
answered Apr 28 '18 at 10:38
foxyjacobfoxyjacob
812
This is my main machine and I really don't have the time to laboriously troubleshoot something like this. Furthermore, all the hard reboots can't have been doing it any good, so I "solved" the issue by installing another flavour - MATE.
– Lolwhites
Apr 28 '18 at 20:08
add a comment |
This problem could be resolved easily by following commands
Go to terminal mode by CTRL + ALT + F3 and login then
sudo apt install --reinstall ubuntu-desktop
sudo apt install --reinstall ubuntu-session
If it does not work, try as follow:
chown $USER:$USER .Xauthority
or try to rebuild .Xauthority
mv .Xauthority .Xauthority.bak
answered Aug 18 '18 at 15:52
HuseyinHuseyin
49711025
1
I upgraded from ubuntu 16.04 to 18.04 and had similar issues to OP. This solution worked perfectly for me. Thanks!
– mildewey
Aug 21 '18 at 16:42
upgrade from 16.04 to 18-04. The chown solved this problem. Thanks!!
– Yaskier
Dec 14 '18 at 0:34
add a comment |
I had the same problem, I removed the last package I had installed (Numix theme from PPA), reboot and the session could access.
answered Apr 30 '18 at 6:27
Daniel M.Daniel M.
11
add a comment |
protected by Community♦ Jul 24 '18 at 15:00
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I ran into a very similar issue, but even a hard reset did not allow me to log in. The last thing I had done before the issue presented itself was install the indicator-multiload package.
I was lucky, and simply logging into a console (CTRL + ALT + F2) and uninstalling the package (sudo apt remove --purge indicator-multiload) fixed the problem.
I have not dived any deeper into this issue to see why (or even whether) this package caused said issue, but I postulate that it has something to do with the package's integration with the Gnome desktop.
Maybe you can try to think what packages you might have installed recently that could have interfered with Gnome and attempt to uninstall them. If doing so works, at least you can get back into your desktop environment and troubleshoot further.
answered Apr 28 '18 at 10:38
foxyjacobfoxyjacob
812
This is my main machine and I really don't have the time to laboriously troubleshoot something like this. Furthermore, all the hard reboots can't have been doing it any good, so I "solved" the issue by installing another flavour - MATE.
– Lolwhites
Apr 28 '18 at 20:08
add a comment |
I ran into a very similar issue, but even a hard reset did not allow me to log in. The last thing I had done before the issue presented itself was install the indicator-multiload package.
I was lucky, and simply logging into a console (CTRL + ALT + F2) and uninstalling the package (sudo apt remove --purge indicator-multiload) fixed the problem.
I have not dived any deeper into this issue to see why (or even whether) this package caused said issue, but I postulate that it has something to do with the package's integration with the Gnome desktop.
Maybe you can try to think what packages you might have installed recently that could have interfered with Gnome and attempt to uninstall them. If doing so works, at least you can get back into your desktop environment and troubleshoot further.
answered Apr 28 '18 at 10:38
foxyjacobfoxyjacob
812
This is my main machine and I really don't have the time to laboriously troubleshoot something like this. Furthermore, all the hard reboots can't have been doing it any good, so I "solved" the issue by installing another flavour - MATE.
– Lolwhites
Apr 28 '18 at 20:08
add a comment |
I ran into a very similar issue, but even a hard reset did not allow me to log in. The last thing I had done before the issue presented itself was install the indicator-multiload package.
I was lucky, and simply logging into a console (CTRL + ALT + F2) and uninstalling the package (sudo apt remove --purge indicator-multiload) fixed the problem.
I have not dived any deeper into this issue to see why (or even whether) this package caused said issue, but I postulate that it has something to do with the package's integration with the Gnome desktop.
Maybe you can try to think what packages you might have installed recently that could have interfered with Gnome and attempt to uninstall them. If doing so works, at least you can get back into your desktop environment and troubleshoot further.
answered Apr 28 '18 at 10:38
foxyjacobfoxyjacob
812
I ran into a very similar issue, but even a hard reset did not allow me to log in. The last thing I had done before the issue presented itself was install the indicator-multiload package.
I was lucky, and simply logging into a console (CTRL + ALT + F2) and uninstalling the package (sudo apt remove --purge indicator-multiload) fixed the problem.
I have not dived any deeper into this issue to see why (or even whether) this package caused said issue, but I postulate that it has something to do with the package's integration with the Gnome desktop.
Maybe you can try to think what packages you might have installed recently that could have interfered with Gnome and attempt to uninstall them. If doing so works, at least you can get back into your desktop environment and troubleshoot further.
answered Apr 28 '18 at 10:38
foxyjacobfoxyjacob
812
answered Apr 28 '18 at 10:38
foxyjacobfoxyjacob
812
answered Apr 28 '18 at 10:38
foxyjacobfoxyjacob
812
answered Apr 28 '18 at 10:38
foxyjacobfoxyjacob
812
812
This is my main machine and I really don't have the time to laboriously troubleshoot something like this. Furthermore, all the hard reboots can't have been doing it any good, so I "solved" the issue by installing another flavour - MATE.
– Lolwhites
Apr 28 '18 at 20:08
add a comment |
This is my main machine and I really don't have the time to laboriously troubleshoot something like this. Furthermore, all the hard reboots can't have been doing it any good, so I "solved" the issue by installing another flavour - MATE.
– Lolwhites
Apr 28 '18 at 20:08
This is my main machine and I really don't have the time to laboriously troubleshoot something like this. Furthermore, all the hard reboots can't have been doing it any good, so I "solved" the issue by installing another flavour - MATE.
– Lolwhites
Apr 28 '18 at 20:08
This is my main machine and I really don't have the time to laboriously troubleshoot something like this. Furthermore, all the hard reboots can't have been doing it any good, so I "solved" the issue by installing another flavour - MATE.
– Lolwhites
Apr 28 '18 at 20:08
add a comment |
This problem could be resolved easily by following commands
Go to terminal mode by CTRL + ALT + F3 and login then
sudo apt install --reinstall ubuntu-desktop
sudo apt install --reinstall ubuntu-session
If it does not work, try as follow:
chown $USER:$USER .Xauthority
or try to rebuild .Xauthority
mv .Xauthority .Xauthority.bak
answered Aug 18 '18 at 15:52
HuseyinHuseyin
49711025
1
I upgraded from ubuntu 16.04 to 18.04 and had similar issues to OP. This solution worked perfectly for me. Thanks!
– mildewey
Aug 21 '18 at 16:42
upgrade from 16.04 to 18-04. The chown solved this problem. Thanks!!
– Yaskier
Dec 14 '18 at 0:34
add a comment |
This problem could be resolved easily by following commands
Go to terminal mode by CTRL + ALT + F3 and login then
sudo apt install --reinstall ubuntu-desktop
sudo apt install --reinstall ubuntu-session
If it does not work, try as follow:
chown $USER:$USER .Xauthority
or try to rebuild .Xauthority
mv .Xauthority .Xauthority.bak
answered Aug 18 '18 at 15:52
HuseyinHuseyin
49711025
1
I upgraded from ubuntu 16.04 to 18.04 and had similar issues to OP. This solution worked perfectly for me. Thanks!
– mildewey
Aug 21 '18 at 16:42
upgrade from 16.04 to 18-04. The chown solved this problem. Thanks!!
– Yaskier
Dec 14 '18 at 0:34
add a comment |
This problem could be resolved easily by following commands
Go to terminal mode by CTRL + ALT + F3 and login then
sudo apt install --reinstall ubuntu-desktop
sudo apt install --reinstall ubuntu-session
If it does not work, try as follow:
chown $USER:$USER .Xauthority
or try to rebuild .Xauthority
mv .Xauthority .Xauthority.bak
answered Aug 18 '18 at 15:52
HuseyinHuseyin
49711025
This problem could be resolved easily by following commands
Go to terminal mode by CTRL + ALT + F3 and login then
sudo apt install --reinstall ubuntu-desktop
sudo apt install --reinstall ubuntu-session
If it does not work, try as follow:
chown $USER:$USER .Xauthority
or try to rebuild .Xauthority
mv .Xauthority .Xauthority.bak
answered Aug 18 '18 at 15:52
HuseyinHuseyin
49711025
answered Aug 18 '18 at 15:52
HuseyinHuseyin
49711025
answered Aug 18 '18 at 15:52
HuseyinHuseyin
49711025
answered Aug 18 '18 at 15:52
HuseyinHuseyin
49711025
49711025
1
I upgraded from ubuntu 16.04 to 18.04 and had similar issues to OP. This solution worked perfectly for me. Thanks!
– mildewey
Aug 21 '18 at 16:42
upgrade from 16.04 to 18-04. The chown solved this problem. Thanks!!
– Yaskier
Dec 14 '18 at 0:34
add a comment |
1
I upgraded from ubuntu 16.04 to 18.04 and had similar issues to OP. This solution worked perfectly for me. Thanks!
– mildewey
Aug 21 '18 at 16:42
upgrade from 16.04 to 18-04. The chown solved this problem. Thanks!!
– Yaskier
Dec 14 '18 at 0:34
1
1
I upgraded from ubuntu 16.04 to 18.04 and had similar issues to OP. This solution worked perfectly for me. Thanks!
– mildewey
Aug 21 '18 at 16:42
I upgraded from ubuntu 16.04 to 18.04 and had similar issues to OP. This solution worked perfectly for me. Thanks!
– mildewey
Aug 21 '18 at 16:42
upgrade from 16.04 to 18-04. The chown solved this problem. Thanks!!
– Yaskier
Dec 14 '18 at 0:34
upgrade from 16.04 to 18-04. The chown solved this problem. Thanks!!
– Yaskier
Dec 14 '18 at 0:34
add a comment |
I had the same problem, I removed the last package I had installed (Numix theme from PPA), reboot and the session could access.
answered Apr 30 '18 at 6:27
Daniel M.Daniel M.
11
add a comment |
I had the same problem, I removed the last package I had installed (Numix theme from PPA), reboot and the session could access.
answered Apr 30 '18 at 6:27
Daniel M.Daniel M.
11
add a comment |
I had the same problem, I removed the last package I had installed (Numix theme from PPA), reboot and the session could access.
answered Apr 30 '18 at 6:27
Daniel M.Daniel M.
11
I had the same problem, I removed the last package I had installed (Numix theme from PPA), reboot and the session could access.
answered Apr 30 '18 at 6:27
Daniel M.Daniel M.
11
answered Apr 30 '18 at 6:27
Daniel M.Daniel M.
11
answered Apr 30 '18 at 6:27
Daniel M.Daniel M.
11
answered Apr 30 '18 at 6:27
Daniel M.Daniel M.
11
11
add a comment |
add a comment |
protected by Community♦ Jul 24 '18 at 15:00
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Check you memory and do an update!
– George Udosen
Apr 27 '18 at 16:10
Since the keyboard isn't recognised while booting, I can't get into recovery mode run a memory check.
– Lolwhites
Apr 27 '18 at 19:34
'My password is not accepted on the first attempt but on the second it is. On finally being allowed to log in, I am presented with a purple screen with no desktop.' Please mark yourself as affected by this bug, thanks! :)
– Ads20000
May 1 '18 at 0:06