Ubuntu 16.04 LTS will automatically log out
up vote
3
down vote
favorite
It kills all the opened applications and processes and then automatically logs out, and then goes into the log-in UI. But after I relog-in, the mounted drives are still mounted. Is there any related settings, or is this a bug? Thanks!
16.04
asked May 15 '16 at 14:10
mining
14219
add a comment |
up vote
3
down vote
favorite
It kills all the opened applications and processes and then automatically logs out, and then goes into the log-in UI. But after I relog-in, the mounted drives are still mounted. Is there any related settings, or is this a bug? Thanks!
16.04
asked May 15 '16 at 14:10
mining
14219
When dies this happen? Sorry but this question is unclear (at least to me)
– Elder Geek
2 days ago
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
It kills all the opened applications and processes and then automatically logs out, and then goes into the log-in UI. But after I relog-in, the mounted drives are still mounted. Is there any related settings, or is this a bug? Thanks!
16.04
asked May 15 '16 at 14:10
mining
14219
It kills all the opened applications and processes and then automatically logs out, and then goes into the log-in UI. But after I relog-in, the mounted drives are still mounted. Is there any related settings, or is this a bug? Thanks!
16.04
16.04
asked May 15 '16 at 14:10
mining
14219
asked May 15 '16 at 14:10
mining
14219
edited May 15 '16 at 14:36
asked May 15 '16 at 14:10
mining
14219
asked May 15 '16 at 14:10
mining
14219
asked May 15 '16 at 14:10
mining
14219
14219
When dies this happen? Sorry but this question is unclear (at least to me)
– Elder Geek
2 days ago
add a comment |
When dies this happen? Sorry but this question is unclear (at least to me)
– Elder Geek
2 days ago
When dies this happen? Sorry but this question is unclear (at least to me)
– Elder Geek
2 days ago
When dies this happen? Sorry but this question is unclear (at least to me)
– Elder Geek
2 days ago
add a comment |
4 Answers
4
active
oldest
votes
up vote
1
down vote
accepted
Similar problem happened to my friend because somehow he corrupted the .Xautority file.
Log into a tty (Ctrl+Alt+F6) and after typing your username and password:
sudo rm -v .Xauthority
.Xauthority file can be found in /home/, which is where the terminal's default working path also usually is. If you use a tty to sign in as one user to delete another's .Xauthority file, make sure you've cd'd to the right directory first.
Then restart lightdm with:
sudo service lightdm restart
The system will recreate the .Xautority file.
Hope it helps.
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered May 15 '16 at 14:29
Sinscary
835522
hi, I'll try this method and give a feedback, thanks you!
– mining
May 15 '16 at 14:33
Hi, thank you! After doing as you kindly suggested, the system seems work very well and the strange error is gone(as far as now).
– mining
May 16 '16 at 3:55
glad it worked.
– Sinscary
May 16 '16 at 3:56
add a comment |
up vote
1
down vote
I installed Chrome Remote Desktop on my Ubuntu and after reboot, this problem happened.
From the terminal Ctrl+Alt+F6, I uninstalled Chrome Remote Desktop by:
sudo apt-get remove chrome-remote-desktop/stable
The problem solved...
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered Dec 7 '17 at 6:55
ahmadalibaloch
1113
2
Hi, thanks a lot for sharing possible solutions!
– mining
Dec 7 '17 at 7:04
add a comment |
up vote
1
down vote
I have faced similar issues. Then realized that the problem was in the way I lock my system.
On windows, we lock using shortcut ALT + Ctrl + Del, and then press Enter.
But in Linux, it is logoff shortcut. It's written clearly on the prompted window, but most of the time, people like me, won't read it at all.
On Ubuntu, shortcut to lock the system is ALT + Ctrl + L.
So before trying something, make sure you are not doing the same.
Hope it helps!
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered Jan 17 at 11:28
Santhu M
113
Hi, thanks a lot for your kind answer!
– mining
Jan 17 at 13:44
add a comment |
up vote
0
down vote
I just experienced this issue today on my fully updated Ubuntu 16.04. I tried all the methods mentioned above but failed.
Fortunately, I solved the problem myself 4 hours later (sigh).
It turned out to be my disk didn't have enough free space. In this case, at the login screen, ALT + Ctrl + F1 to a terminal, login to your account, delete some unimportant files in your home directory, and try to login with GUI mode again.
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered 2 days ago
bcli
1
New contributor
bcli is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Similar problem happened to my friend because somehow he corrupted the .Xautority file.
Log into a tty (Ctrl+Alt+F6) and after typing your username and password:
sudo rm -v .Xauthority
.Xauthority file can be found in /home/, which is where the terminal's default working path also usually is. If you use a tty to sign in as one user to delete another's .Xauthority file, make sure you've cd'd to the right directory first.
Then restart lightdm with:
sudo service lightdm restart
The system will recreate the .Xautority file.
Hope it helps.
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered May 15 '16 at 14:29
Sinscary
835522
hi, I'll try this method and give a feedback, thanks you!
– mining
May 15 '16 at 14:33
Hi, thank you! After doing as you kindly suggested, the system seems work very well and the strange error is gone(as far as now).
– mining
May 16 '16 at 3:55
glad it worked.
– Sinscary
May 16 '16 at 3:56
add a comment |
up vote
1
down vote
accepted
Similar problem happened to my friend because somehow he corrupted the .Xautority file.
Log into a tty (Ctrl+Alt+F6) and after typing your username and password:
sudo rm -v .Xauthority
.Xauthority file can be found in /home/, which is where the terminal's default working path also usually is. If you use a tty to sign in as one user to delete another's .Xauthority file, make sure you've cd'd to the right directory first.
Then restart lightdm with:
sudo service lightdm restart
The system will recreate the .Xautority file.
Hope it helps.
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered May 15 '16 at 14:29
Sinscary
835522
hi, I'll try this method and give a feedback, thanks you!
– mining
May 15 '16 at 14:33
Hi, thank you! After doing as you kindly suggested, the system seems work very well and the strange error is gone(as far as now).
– mining
May 16 '16 at 3:55
glad it worked.
– Sinscary
May 16 '16 at 3:56
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Similar problem happened to my friend because somehow he corrupted the .Xautority file.
Log into a tty (Ctrl+Alt+F6) and after typing your username and password:
sudo rm -v .Xauthority
.Xauthority file can be found in /home/, which is where the terminal's default working path also usually is. If you use a tty to sign in as one user to delete another's .Xauthority file, make sure you've cd'd to the right directory first.
Then restart lightdm with:
sudo service lightdm restart
The system will recreate the .Xautority file.
Hope it helps.
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered May 15 '16 at 14:29
Sinscary
835522
Similar problem happened to my friend because somehow he corrupted the .Xautority file.
Log into a tty (Ctrl+Alt+F6) and after typing your username and password:
sudo rm -v .Xauthority
.Xauthority file can be found in /home/, which is where the terminal's default working path also usually is. If you use a tty to sign in as one user to delete another's .Xauthority file, make sure you've cd'd to the right directory first.
Then restart lightdm with:
sudo service lightdm restart
The system will recreate the .Xautority file.
Hope it helps.
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered May 15 '16 at 14:29
Sinscary
835522
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
1,4604924
answered May 15 '16 at 14:29
Sinscary
835522
answered May 15 '16 at 14:29
Sinscary
835522
answered May 15 '16 at 14:29
Sinscary
835522
835522
hi, I'll try this method and give a feedback, thanks you!
– mining
May 15 '16 at 14:33
Hi, thank you! After doing as you kindly suggested, the system seems work very well and the strange error is gone(as far as now).
– mining
May 16 '16 at 3:55
glad it worked.
– Sinscary
May 16 '16 at 3:56
add a comment |
hi, I'll try this method and give a feedback, thanks you!
– mining
May 15 '16 at 14:33
Hi, thank you! After doing as you kindly suggested, the system seems work very well and the strange error is gone(as far as now).
– mining
May 16 '16 at 3:55
glad it worked.
– Sinscary
May 16 '16 at 3:56
hi, I'll try this method and give a feedback, thanks you!
– mining
May 15 '16 at 14:33
hi, I'll try this method and give a feedback, thanks you!
– mining
May 15 '16 at 14:33
Hi, thank you! After doing as you kindly suggested, the system seems work very well and the strange error is gone(as far as now).
– mining
May 16 '16 at 3:55
Hi, thank you! After doing as you kindly suggested, the system seems work very well and the strange error is gone(as far as now).
– mining
May 16 '16 at 3:55
glad it worked.
– Sinscary
May 16 '16 at 3:56
glad it worked.
– Sinscary
May 16 '16 at 3:56
add a comment |
up vote
1
down vote
I installed Chrome Remote Desktop on my Ubuntu and after reboot, this problem happened.
From the terminal Ctrl+Alt+F6, I uninstalled Chrome Remote Desktop by:
sudo apt-get remove chrome-remote-desktop/stable
The problem solved...
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered Dec 7 '17 at 6:55
ahmadalibaloch
1113
2
Hi, thanks a lot for sharing possible solutions!
– mining
Dec 7 '17 at 7:04
add a comment |
up vote
1
down vote
I installed Chrome Remote Desktop on my Ubuntu and after reboot, this problem happened.
From the terminal Ctrl+Alt+F6, I uninstalled Chrome Remote Desktop by:
sudo apt-get remove chrome-remote-desktop/stable
The problem solved...
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered Dec 7 '17 at 6:55
ahmadalibaloch
1113
2
Hi, thanks a lot for sharing possible solutions!
– mining
Dec 7 '17 at 7:04
add a comment |
up vote
1
down vote
up vote
1
down vote
I installed Chrome Remote Desktop on my Ubuntu and after reboot, this problem happened.
From the terminal Ctrl+Alt+F6, I uninstalled Chrome Remote Desktop by:
sudo apt-get remove chrome-remote-desktop/stable
The problem solved...
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered Dec 7 '17 at 6:55
ahmadalibaloch
1113
I installed Chrome Remote Desktop on my Ubuntu and after reboot, this problem happened.
From the terminal Ctrl+Alt+F6, I uninstalled Chrome Remote Desktop by:
sudo apt-get remove chrome-remote-desktop/stable
The problem solved...
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered Dec 7 '17 at 6:55
ahmadalibaloch
1113
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
1,4604924
answered Dec 7 '17 at 6:55
ahmadalibaloch
1113
answered Dec 7 '17 at 6:55
ahmadalibaloch
1113
answered Dec 7 '17 at 6:55
ahmadalibaloch
1113
1113
2
Hi, thanks a lot for sharing possible solutions!
– mining
Dec 7 '17 at 7:04
add a comment |
2
Hi, thanks a lot for sharing possible solutions!
– mining
Dec 7 '17 at 7:04
2
2
Hi, thanks a lot for sharing possible solutions!
– mining
Dec 7 '17 at 7:04
Hi, thanks a lot for sharing possible solutions!
– mining
Dec 7 '17 at 7:04
add a comment |
up vote
1
down vote
I have faced similar issues. Then realized that the problem was in the way I lock my system.
On windows, we lock using shortcut ALT + Ctrl + Del, and then press Enter.
But in Linux, it is logoff shortcut. It's written clearly on the prompted window, but most of the time, people like me, won't read it at all.
On Ubuntu, shortcut to lock the system is ALT + Ctrl + L.
So before trying something, make sure you are not doing the same.
Hope it helps!
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered Jan 17 at 11:28
Santhu M
113
Hi, thanks a lot for your kind answer!
– mining
Jan 17 at 13:44
add a comment |
up vote
1
down vote
I have faced similar issues. Then realized that the problem was in the way I lock my system.
On windows, we lock using shortcut ALT + Ctrl + Del, and then press Enter.
But in Linux, it is logoff shortcut. It's written clearly on the prompted window, but most of the time, people like me, won't read it at all.
On Ubuntu, shortcut to lock the system is ALT + Ctrl + L.
So before trying something, make sure you are not doing the same.
Hope it helps!
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered Jan 17 at 11:28
Santhu M
113
Hi, thanks a lot for your kind answer!
– mining
Jan 17 at 13:44
add a comment |
up vote
1
down vote
up vote
1
down vote
I have faced similar issues. Then realized that the problem was in the way I lock my system.
On windows, we lock using shortcut ALT + Ctrl + Del, and then press Enter.
But in Linux, it is logoff shortcut. It's written clearly on the prompted window, but most of the time, people like me, won't read it at all.
On Ubuntu, shortcut to lock the system is ALT + Ctrl + L.
So before trying something, make sure you are not doing the same.
Hope it helps!
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered Jan 17 at 11:28
Santhu M
113
I have faced similar issues. Then realized that the problem was in the way I lock my system.
On windows, we lock using shortcut ALT + Ctrl + Del, and then press Enter.
But in Linux, it is logoff shortcut. It's written clearly on the prompted window, but most of the time, people like me, won't read it at all.
On Ubuntu, shortcut to lock the system is ALT + Ctrl + L.
So before trying something, make sure you are not doing the same.
Hope it helps!
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered Jan 17 at 11:28
Santhu M
113
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
1,4604924
answered Jan 17 at 11:28
Santhu M
113
answered Jan 17 at 11:28
Santhu M
113
answered Jan 17 at 11:28
Santhu M
113
113
Hi, thanks a lot for your kind answer!
– mining
Jan 17 at 13:44
add a comment |
Hi, thanks a lot for your kind answer!
– mining
Jan 17 at 13:44
Hi, thanks a lot for your kind answer!
– mining
Jan 17 at 13:44
Hi, thanks a lot for your kind answer!
– mining
Jan 17 at 13:44
add a comment |
up vote
0
down vote
I just experienced this issue today on my fully updated Ubuntu 16.04. I tried all the methods mentioned above but failed.
Fortunately, I solved the problem myself 4 hours later (sigh).
It turned out to be my disk didn't have enough free space. In this case, at the login screen, ALT + Ctrl + F1 to a terminal, login to your account, delete some unimportant files in your home directory, and try to login with GUI mode again.
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered 2 days ago
bcli
1
New contributor
bcli is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
I just experienced this issue today on my fully updated Ubuntu 16.04. I tried all the methods mentioned above but failed.
Fortunately, I solved the problem myself 4 hours later (sigh).
It turned out to be my disk didn't have enough free space. In this case, at the login screen, ALT + Ctrl + F1 to a terminal, login to your account, delete some unimportant files in your home directory, and try to login with GUI mode again.
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered 2 days ago
bcli
1
New contributor
bcli is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
I just experienced this issue today on my fully updated Ubuntu 16.04. I tried all the methods mentioned above but failed.
Fortunately, I solved the problem myself 4 hours later (sigh).
It turned out to be my disk didn't have enough free space. In this case, at the login screen, ALT + Ctrl + F1 to a terminal, login to your account, delete some unimportant files in your home directory, and try to login with GUI mode again.
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered 2 days ago
bcli
1
New contributor
bcli is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I just experienced this issue today on my fully updated Ubuntu 16.04. I tried all the methods mentioned above but failed.
Fortunately, I solved the problem myself 4 hours later (sigh).
It turned out to be my disk didn't have enough free space. In this case, at the login screen, ALT + Ctrl + F1 to a terminal, login to your account, delete some unimportant files in your home directory, and try to login with GUI mode again.
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
answered 2 days ago
bcli
1
New contributor
bcli is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
edited 2 days ago
Yufenyuy Veyeh Dider
1,4604924
1,4604924
answered 2 days ago
bcli
1
New contributor
bcli is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
bcli
1
answered 2 days ago
bcli
1
1
New contributor
bcli is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
bcli is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
bcli is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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%2f772777%2fubuntu-16-04-lts-will-automatically-log-out%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
When dies this happen? Sorry but this question is unclear (at least to me)
– Elder Geek
2 days ago