Ubuntu 18.04 on login loop, even with correct password
up vote
3
down vote
favorite
I installed Ubuntu 18.04 yesterday, done some app installation and configurations and went to sleep. This morning, the login simply didn't work: the system is unable to log into my session, even with the correct password. Every time I try it, it flashes the screen into black and purple, the mouse pointer is available, but it flashes back to the login screen again: no error message prompts and I spent quite some time amusing myself trying to win it by attrition =). I also tried switch over to Wayland, and the same result: screen flashes to black, couple of seconds later, I'm back at the login stage.
There is nothing wrong with my password, since I can log into my user account on the Terminal (CTRL+ALT+F1). Once there, I did a sudo apt update/upgrade in the hopes it'd fix something, but my system was up to date and it didn't solve anything after I rebooted.
I've seen a lot of similar reports on the internet and the only solution that it seemed worthwhile to my noobish eyes was removing/deleting the .Xauthority file. But when I tried it, the return I got was that there was no such file on my Home directory. The other solutions applied to people upgrading their systems - mine was a fresh install - or with pretty specific hardware and conditions that don't apply to me.
So, what should I do to fix this?
18.04
add a comment |
up vote
3
down vote
favorite
I installed Ubuntu 18.04 yesterday, done some app installation and configurations and went to sleep. This morning, the login simply didn't work: the system is unable to log into my session, even with the correct password. Every time I try it, it flashes the screen into black and purple, the mouse pointer is available, but it flashes back to the login screen again: no error message prompts and I spent quite some time amusing myself trying to win it by attrition =). I also tried switch over to Wayland, and the same result: screen flashes to black, couple of seconds later, I'm back at the login stage.
There is nothing wrong with my password, since I can log into my user account on the Terminal (CTRL+ALT+F1). Once there, I did a sudo apt update/upgrade in the hopes it'd fix something, but my system was up to date and it didn't solve anything after I rebooted.
I've seen a lot of similar reports on the internet and the only solution that it seemed worthwhile to my noobish eyes was removing/deleting the .Xauthority file. But when I tried it, the return I got was that there was no such file on my Home directory. The other solutions applied to people upgrading their systems - mine was a fresh install - or with pretty specific hardware and conditions that don't apply to me.
So, what should I do to fix this?
18.04
2
Possible duplicate of Ubuntu gets stuck in a login loop
– Elder Geek
Jul 25 at 21:43
Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04
– Sumit
Sep 25 at 6:37
Check againls -l ~/.Xauthority
ls -l ~/.ICEauthority
ls -ld ~
– Hobbyist
Oct 30 at 15:35
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I installed Ubuntu 18.04 yesterday, done some app installation and configurations and went to sleep. This morning, the login simply didn't work: the system is unable to log into my session, even with the correct password. Every time I try it, it flashes the screen into black and purple, the mouse pointer is available, but it flashes back to the login screen again: no error message prompts and I spent quite some time amusing myself trying to win it by attrition =). I also tried switch over to Wayland, and the same result: screen flashes to black, couple of seconds later, I'm back at the login stage.
There is nothing wrong with my password, since I can log into my user account on the Terminal (CTRL+ALT+F1). Once there, I did a sudo apt update/upgrade in the hopes it'd fix something, but my system was up to date and it didn't solve anything after I rebooted.
I've seen a lot of similar reports on the internet and the only solution that it seemed worthwhile to my noobish eyes was removing/deleting the .Xauthority file. But when I tried it, the return I got was that there was no such file on my Home directory. The other solutions applied to people upgrading their systems - mine was a fresh install - or with pretty specific hardware and conditions that don't apply to me.
So, what should I do to fix this?
18.04
I installed Ubuntu 18.04 yesterday, done some app installation and configurations and went to sleep. This morning, the login simply didn't work: the system is unable to log into my session, even with the correct password. Every time I try it, it flashes the screen into black and purple, the mouse pointer is available, but it flashes back to the login screen again: no error message prompts and I spent quite some time amusing myself trying to win it by attrition =). I also tried switch over to Wayland, and the same result: screen flashes to black, couple of seconds later, I'm back at the login stage.
There is nothing wrong with my password, since I can log into my user account on the Terminal (CTRL+ALT+F1). Once there, I did a sudo apt update/upgrade in the hopes it'd fix something, but my system was up to date and it didn't solve anything after I rebooted.
I've seen a lot of similar reports on the internet and the only solution that it seemed worthwhile to my noobish eyes was removing/deleting the .Xauthority file. But when I tried it, the return I got was that there was no such file on my Home directory. The other solutions applied to people upgrading their systems - mine was a fresh install - or with pretty specific hardware and conditions that don't apply to me.
So, what should I do to fix this?
18.04
18.04
asked Jul 25 at 18:31
wowbagger
2614
2614
2
Possible duplicate of Ubuntu gets stuck in a login loop
– Elder Geek
Jul 25 at 21:43
Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04
– Sumit
Sep 25 at 6:37
Check againls -l ~/.Xauthority
ls -l ~/.ICEauthority
ls -ld ~
– Hobbyist
Oct 30 at 15:35
add a comment |
2
Possible duplicate of Ubuntu gets stuck in a login loop
– Elder Geek
Jul 25 at 21:43
Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04
– Sumit
Sep 25 at 6:37
Check againls -l ~/.Xauthority
ls -l ~/.ICEauthority
ls -ld ~
– Hobbyist
Oct 30 at 15:35
2
2
Possible duplicate of Ubuntu gets stuck in a login loop
– Elder Geek
Jul 25 at 21:43
Possible duplicate of Ubuntu gets stuck in a login loop
– Elder Geek
Jul 25 at 21:43
Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04
– Sumit
Sep 25 at 6:37
Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04
– Sumit
Sep 25 at 6:37
Check again
ls -l ~/.Xauthority
ls -l ~/.ICEauthority
ls -ld ~
– Hobbyist
Oct 30 at 15:35
Check again
ls -l ~/.Xauthority
ls -l ~/.ICEauthority
ls -ld ~
– Hobbyist
Oct 30 at 15:35
add a comment |
3 Answers
3
active
oldest
votes
up vote
1
down vote
I had the same problem.
Then I found out that I accidentally changed the ownership of my /home/username
directory to root
.
So you can go to the terminal by CTRL+ALT+F1, and change the username
directory ownership with
sudo chown username:username -R /home/username
add a comment |
up vote
1
down vote
accepted
I ended up solving this by disabling secure boot on my notebook. As I understand, my issue was caused by wonky Nvidia drivers.
add a comment |
up vote
0
down vote
Experienced the same problem today for the first time since moving on to Beaver. Weirdly immediately post full wizard install.
Initially I thought it was a Wayland issue but despite attempts to force other compositors the issue remained until I cracked-open a Shell and removed my freshly created user /home folder. Upon the next initialisation of my chosen GDM I was shown the new user config wizard and all has been fine since.
New contributor
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
I had the same problem.
Then I found out that I accidentally changed the ownership of my /home/username
directory to root
.
So you can go to the terminal by CTRL+ALT+F1, and change the username
directory ownership with
sudo chown username:username -R /home/username
add a comment |
up vote
1
down vote
I had the same problem.
Then I found out that I accidentally changed the ownership of my /home/username
directory to root
.
So you can go to the terminal by CTRL+ALT+F1, and change the username
directory ownership with
sudo chown username:username -R /home/username
add a comment |
up vote
1
down vote
up vote
1
down vote
I had the same problem.
Then I found out that I accidentally changed the ownership of my /home/username
directory to root
.
So you can go to the terminal by CTRL+ALT+F1, and change the username
directory ownership with
sudo chown username:username -R /home/username
I had the same problem.
Then I found out that I accidentally changed the ownership of my /home/username
directory to root
.
So you can go to the terminal by CTRL+ALT+F1, and change the username
directory ownership with
sudo chown username:username -R /home/username
edited Sep 27 at 23:40
zx485
1,43831114
1,43831114
answered Sep 27 at 18:43
HosseinNedaee
111
111
add a comment |
add a comment |
up vote
1
down vote
accepted
I ended up solving this by disabling secure boot on my notebook. As I understand, my issue was caused by wonky Nvidia drivers.
add a comment |
up vote
1
down vote
accepted
I ended up solving this by disabling secure boot on my notebook. As I understand, my issue was caused by wonky Nvidia drivers.
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I ended up solving this by disabling secure boot on my notebook. As I understand, my issue was caused by wonky Nvidia drivers.
I ended up solving this by disabling secure boot on my notebook. As I understand, my issue was caused by wonky Nvidia drivers.
answered Nov 19 at 21:49
wowbagger
2614
2614
add a comment |
add a comment |
up vote
0
down vote
Experienced the same problem today for the first time since moving on to Beaver. Weirdly immediately post full wizard install.
Initially I thought it was a Wayland issue but despite attempts to force other compositors the issue remained until I cracked-open a Shell and removed my freshly created user /home folder. Upon the next initialisation of my chosen GDM I was shown the new user config wizard and all has been fine since.
New contributor
add a comment |
up vote
0
down vote
Experienced the same problem today for the first time since moving on to Beaver. Weirdly immediately post full wizard install.
Initially I thought it was a Wayland issue but despite attempts to force other compositors the issue remained until I cracked-open a Shell and removed my freshly created user /home folder. Upon the next initialisation of my chosen GDM I was shown the new user config wizard and all has been fine since.
New contributor
add a comment |
up vote
0
down vote
up vote
0
down vote
Experienced the same problem today for the first time since moving on to Beaver. Weirdly immediately post full wizard install.
Initially I thought it was a Wayland issue but despite attempts to force other compositors the issue remained until I cracked-open a Shell and removed my freshly created user /home folder. Upon the next initialisation of my chosen GDM I was shown the new user config wizard and all has been fine since.
New contributor
Experienced the same problem today for the first time since moving on to Beaver. Weirdly immediately post full wizard install.
Initially I thought it was a Wayland issue but despite attempts to force other compositors the issue remained until I cracked-open a Shell and removed my freshly created user /home folder. Upon the next initialisation of my chosen GDM I was shown the new user config wizard and all has been fine since.
New contributor
New contributor
answered Nov 18 at 19:05
Rob
1
1
New contributor
New contributor
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1059458%2fubuntu-18-04-on-login-loop-even-with-correct-password%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Possible duplicate of Ubuntu gets stuck in a login loop
– Elder Geek
Jul 25 at 21:43
Did you find a solution for this? I have the same problem and the solution mentioned on the above link does not work for Ubuntu 18.04
– Sumit
Sep 25 at 6:37
Check again
ls -l ~/.Xauthority
ls -l ~/.ICEauthority
ls -ld ~
– Hobbyist
Oct 30 at 15:35