Correct password fails to login (login loop) in Ubuntu 16.04Upgrade from 12.04lts to 14.04lts login loopPassword fails to loginUbuntu 16.04 nvidia driver login loop even after trying nvidia-364 and nvidia-currentLogin loop on Ubuntu 16.04.1Ubuntu 16.04 automatically logs out after admin changeAfter Purpule screen Balck Screen insted of login screen on ubuntu 16.04Stuck in an infinite loop at login on Ubuntu 16.04Ubuntu 16.04 Login Loop After Updatexubuntu 18.04 login loopUbuntu 16.04 login loop, unity-panel-service-lockscreen fails
Creating two special characters
What is the English pronunciation of "pain au chocolat"?
Why is the Sun approximated as a black body at ~ 5800 K?
Does the Linux kernel need a file system to run?
Delete multiple columns using awk or sed
How does electrical safety system work on ISS?
Is it allowed to activate the ability of multiple planeswalkers in a single turn?
Quoting Keynes in a lecture
How many arrows is an archer expected to fire by the end of the Tyranny of Dragons pair of adventures?
Make a Bowl of Alphabet Soup
Is it necessary to use pronouns with the verb "essere"?
Strong empirical falsification of quantum mechanics based on vacuum energy density?
Why is so much work done on numerical verification of the Riemann Hypothesis?
Can you use Vicious Mockery to win an argument or gain favours?
Is there a nicer/politer/more positive alternative for "negates"?
Fantasy comedy romance novel, set in medieval times, involving a siege, a nun, and enchanted pickles
What does Apple's new App Store requirement mean
US tourist/student visa
When were female captains banned from Starfleet?
Why do Radio Buttons not fill the entire outer circle?
Why can't the Brexit deadlock in the UK parliament be solved with a plurality vote?
Why does this expression simplify as such?
How to get directions in deep space?
Multiplicative persistence
Correct password fails to login (login loop) in Ubuntu 16.04
Upgrade from 12.04lts to 14.04lts login loopPassword fails to loginUbuntu 16.04 nvidia driver login loop even after trying nvidia-364 and nvidia-currentLogin loop on Ubuntu 16.04.1Ubuntu 16.04 automatically logs out after admin changeAfter Purpule screen Balck Screen insted of login screen on ubuntu 16.04Stuck in an infinite loop at login on Ubuntu 16.04Ubuntu 16.04 Login Loop After Updatexubuntu 18.04 login loopUbuntu 16.04 login loop, unity-panel-service-lockscreen fails
I know this question asked so many times before but none of the solutions worked for me. My OS is Ubuntu 16.04.5 (alongside Win10) when I type the correct pw it enters the login loop.
journalctl
colored output: https://gist.github.com/ridvansumset/40e9223262361fa9590aa5e5bc5e10a6
The solutions I found on the web and tried are:
1- (at login screen) Ctrl+Alt+F3 then chown username:username .Xauthority
then mv .Xauthority .Xauthority.bak
2- (at login screen) Ctrl+Alt+F3 then remove lightdm
and reinstall it
3- Entering the recovery mode then choosing dpkg then relogin
4- sudo apt-get purge nvidia*
5- etc/shadow file already exists.
Nothing works for me :(. Can someone please help? It's urgent
16.04 password login-screen
add a comment |
I know this question asked so many times before but none of the solutions worked for me. My OS is Ubuntu 16.04.5 (alongside Win10) when I type the correct pw it enters the login loop.
journalctl
colored output: https://gist.github.com/ridvansumset/40e9223262361fa9590aa5e5bc5e10a6
The solutions I found on the web and tried are:
1- (at login screen) Ctrl+Alt+F3 then chown username:username .Xauthority
then mv .Xauthority .Xauthority.bak
2- (at login screen) Ctrl+Alt+F3 then remove lightdm
and reinstall it
3- Entering the recovery mode then choosing dpkg then relogin
4- sudo apt-get purge nvidia*
5- etc/shadow file already exists.
Nothing works for me :(. Can someone please help? It's urgent
16.04 password login-screen
Also, how can I go back to login screen after entering terminal with CTRL+ALT+F3?
– Rıdvan Sumset
Sep 30 '18 at 14:37
In 16.04, press CTRL+ALT+F7 to return to the login screen (or the desktop if you are already logged in).
– danzel
Sep 30 '18 at 15:12
add a comment |
I know this question asked so many times before but none of the solutions worked for me. My OS is Ubuntu 16.04.5 (alongside Win10) when I type the correct pw it enters the login loop.
journalctl
colored output: https://gist.github.com/ridvansumset/40e9223262361fa9590aa5e5bc5e10a6
The solutions I found on the web and tried are:
1- (at login screen) Ctrl+Alt+F3 then chown username:username .Xauthority
then mv .Xauthority .Xauthority.bak
2- (at login screen) Ctrl+Alt+F3 then remove lightdm
and reinstall it
3- Entering the recovery mode then choosing dpkg then relogin
4- sudo apt-get purge nvidia*
5- etc/shadow file already exists.
Nothing works for me :(. Can someone please help? It's urgent
16.04 password login-screen
I know this question asked so many times before but none of the solutions worked for me. My OS is Ubuntu 16.04.5 (alongside Win10) when I type the correct pw it enters the login loop.
journalctl
colored output: https://gist.github.com/ridvansumset/40e9223262361fa9590aa5e5bc5e10a6
The solutions I found on the web and tried are:
1- (at login screen) Ctrl+Alt+F3 then chown username:username .Xauthority
then mv .Xauthority .Xauthority.bak
2- (at login screen) Ctrl+Alt+F3 then remove lightdm
and reinstall it
3- Entering the recovery mode then choosing dpkg then relogin
4- sudo apt-get purge nvidia*
5- etc/shadow file already exists.
Nothing works for me :(. Can someone please help? It's urgent
16.04 password login-screen
16.04 password login-screen
edited Oct 3 '18 at 8:44
Rıdvan Sumset
asked Sep 30 '18 at 14:36
Rıdvan SumsetRıdvan Sumset
115
115
Also, how can I go back to login screen after entering terminal with CTRL+ALT+F3?
– Rıdvan Sumset
Sep 30 '18 at 14:37
In 16.04, press CTRL+ALT+F7 to return to the login screen (or the desktop if you are already logged in).
– danzel
Sep 30 '18 at 15:12
add a comment |
Also, how can I go back to login screen after entering terminal with CTRL+ALT+F3?
– Rıdvan Sumset
Sep 30 '18 at 14:37
In 16.04, press CTRL+ALT+F7 to return to the login screen (or the desktop if you are already logged in).
– danzel
Sep 30 '18 at 15:12
Also, how can I go back to login screen after entering terminal with CTRL+ALT+F3?
– Rıdvan Sumset
Sep 30 '18 at 14:37
Also, how can I go back to login screen after entering terminal with CTRL+ALT+F3?
– Rıdvan Sumset
Sep 30 '18 at 14:37
In 16.04, press CTRL+ALT+F7 to return to the login screen (or the desktop if you are already logged in).
– danzel
Sep 30 '18 at 15:12
In 16.04, press CTRL+ALT+F7 to return to the login screen (or the desktop if you are already logged in).
– danzel
Sep 30 '18 at 15:12
add a comment |
3 Answers
3
active
oldest
votes
OK! I figured out what my problem is and now I can login!!! Here how I solved it:
Press Ctrl+Alt+F3 to enter terminal then login with your username and password.
Firstly, run nano ~/bash_history
. This will show you the commands you used before. (Notice that the command at the top of the list is the oldest one). Then, look at your commands line by line, try to figure out which one can cause this problem. Pass unimportant commands like cd
or cat
. Try to focus on commands that makes effect on your system or environment. If you find anything, undo what you did.
In my case, it was sudo nano etc/environment
command. When I inspected that file, there wasn't even any typo. But still, I removed all the lines
that I added before to revert my changes. Now it includes only $PATH
variable which is:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
Then I ran source etc/environment
. After that I was able to login!
P.S: Never edit your etc/environment
file. Instead use export
command to set an environment variable. Besides, check if there is a typo in your ~/.profile
and ~/.bash_profile
files, as well.
add a comment |
Welcome to Hell. I faced this too, and all I had to blame are unsigned Nvidia modules, or similar thing. So, I assume this isn't the first time you boot into Ubuntu since the first setup? And you got Nvidia drivers as well?
First of all, there has to be issues reported in your logs from
$ journalctl
If so, add to your post.
As a workaround, disable Secure Boot in your BIOS setup, if it's on (I mean, it MUST be on, because usually it blocks unsigned gfx driver from loading to kernel. This was my issue, however, since I left Ubuntu long time ago, I have different issue, for ex., on Arch, where desktop environment literally won't load up). Write me back with your results
I've been using ubuntu since may 2017. I had nvidia drivers but I usedsudo apt-get purge nvidia*
I don't know if I still have them. Secure boot was ON I disabled it from Windows BIOS. Then I tried to login and failed again.journalctl
command's output is too big but I saw a line says secureboot: secure boot could not be determined(mode 0).
– Rıdvan Sumset
Sep 30 '18 at 19:53
I also tried to login in recovery mode but still no luck :/
– Rıdvan Sumset
Sep 30 '18 at 19:57
1
bugzilla.redhat.com/show_bug.cgi?id=1451071 Also, it's obvious journalctl will output much info, but it's the system logs, it's supposed to be like that. I don't feel that the error message you shared is enough for clarifying. You could save all the error lines in some file and report back if possible like $ journalctl 2> ~/errors.txt
– xt1zer
Oct 1 '18 at 14:10
here is the colored output (if you open it in terminal) gist.github.com/ridvansumset/40e9223262361fa9590aa5e5bc5e10a6
– Rıdvan Sumset
Oct 2 '18 at 9:11
add a comment |
1. Problem description
Nvidia-396, which you have installed intently or unawarely auto-installed by other related package, such as swig, can not properly used in utuntu 16.04.
2. Solution
The best way to solve the problem would be ever find the miss-operation firstly. To do this, firstly, you need to check your command history by :
vi ~/.bash_history
and then search "sudo" keywords which indicate essential command, and find suspects. In my case, it is
sudo install swig
Finally, revert it by :
sudo apt-get purge swig
CAUTION : PLEASE NEVER DO
sudo apt-get upgrade
It will install newest package of your whole system which will include nividia-396
New contributor
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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%2f1079737%2fcorrect-password-fails-to-login-login-loop-in-ubuntu-16-04%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
OK! I figured out what my problem is and now I can login!!! Here how I solved it:
Press Ctrl+Alt+F3 to enter terminal then login with your username and password.
Firstly, run nano ~/bash_history
. This will show you the commands you used before. (Notice that the command at the top of the list is the oldest one). Then, look at your commands line by line, try to figure out which one can cause this problem. Pass unimportant commands like cd
or cat
. Try to focus on commands that makes effect on your system or environment. If you find anything, undo what you did.
In my case, it was sudo nano etc/environment
command. When I inspected that file, there wasn't even any typo. But still, I removed all the lines
that I added before to revert my changes. Now it includes only $PATH
variable which is:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
Then I ran source etc/environment
. After that I was able to login!
P.S: Never edit your etc/environment
file. Instead use export
command to set an environment variable. Besides, check if there is a typo in your ~/.profile
and ~/.bash_profile
files, as well.
add a comment |
OK! I figured out what my problem is and now I can login!!! Here how I solved it:
Press Ctrl+Alt+F3 to enter terminal then login with your username and password.
Firstly, run nano ~/bash_history
. This will show you the commands you used before. (Notice that the command at the top of the list is the oldest one). Then, look at your commands line by line, try to figure out which one can cause this problem. Pass unimportant commands like cd
or cat
. Try to focus on commands that makes effect on your system or environment. If you find anything, undo what you did.
In my case, it was sudo nano etc/environment
command. When I inspected that file, there wasn't even any typo. But still, I removed all the lines
that I added before to revert my changes. Now it includes only $PATH
variable which is:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
Then I ran source etc/environment
. After that I was able to login!
P.S: Never edit your etc/environment
file. Instead use export
command to set an environment variable. Besides, check if there is a typo in your ~/.profile
and ~/.bash_profile
files, as well.
add a comment |
OK! I figured out what my problem is and now I can login!!! Here how I solved it:
Press Ctrl+Alt+F3 to enter terminal then login with your username and password.
Firstly, run nano ~/bash_history
. This will show you the commands you used before. (Notice that the command at the top of the list is the oldest one). Then, look at your commands line by line, try to figure out which one can cause this problem. Pass unimportant commands like cd
or cat
. Try to focus on commands that makes effect on your system or environment. If you find anything, undo what you did.
In my case, it was sudo nano etc/environment
command. When I inspected that file, there wasn't even any typo. But still, I removed all the lines
that I added before to revert my changes. Now it includes only $PATH
variable which is:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
Then I ran source etc/environment
. After that I was able to login!
P.S: Never edit your etc/environment
file. Instead use export
command to set an environment variable. Besides, check if there is a typo in your ~/.profile
and ~/.bash_profile
files, as well.
OK! I figured out what my problem is and now I can login!!! Here how I solved it:
Press Ctrl+Alt+F3 to enter terminal then login with your username and password.
Firstly, run nano ~/bash_history
. This will show you the commands you used before. (Notice that the command at the top of the list is the oldest one). Then, look at your commands line by line, try to figure out which one can cause this problem. Pass unimportant commands like cd
or cat
. Try to focus on commands that makes effect on your system or environment. If you find anything, undo what you did.
In my case, it was sudo nano etc/environment
command. When I inspected that file, there wasn't even any typo. But still, I removed all the lines
that I added before to revert my changes. Now it includes only $PATH
variable which is:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
Then I ran source etc/environment
. After that I was able to login!
P.S: Never edit your etc/environment
file. Instead use export
command to set an environment variable. Besides, check if there is a typo in your ~/.profile
and ~/.bash_profile
files, as well.
edited Oct 4 '18 at 21:04
answered Oct 4 '18 at 14:30
Rıdvan SumsetRıdvan Sumset
115
115
add a comment |
add a comment |
Welcome to Hell. I faced this too, and all I had to blame are unsigned Nvidia modules, or similar thing. So, I assume this isn't the first time you boot into Ubuntu since the first setup? And you got Nvidia drivers as well?
First of all, there has to be issues reported in your logs from
$ journalctl
If so, add to your post.
As a workaround, disable Secure Boot in your BIOS setup, if it's on (I mean, it MUST be on, because usually it blocks unsigned gfx driver from loading to kernel. This was my issue, however, since I left Ubuntu long time ago, I have different issue, for ex., on Arch, where desktop environment literally won't load up). Write me back with your results
I've been using ubuntu since may 2017. I had nvidia drivers but I usedsudo apt-get purge nvidia*
I don't know if I still have them. Secure boot was ON I disabled it from Windows BIOS. Then I tried to login and failed again.journalctl
command's output is too big but I saw a line says secureboot: secure boot could not be determined(mode 0).
– Rıdvan Sumset
Sep 30 '18 at 19:53
I also tried to login in recovery mode but still no luck :/
– Rıdvan Sumset
Sep 30 '18 at 19:57
1
bugzilla.redhat.com/show_bug.cgi?id=1451071 Also, it's obvious journalctl will output much info, but it's the system logs, it's supposed to be like that. I don't feel that the error message you shared is enough for clarifying. You could save all the error lines in some file and report back if possible like $ journalctl 2> ~/errors.txt
– xt1zer
Oct 1 '18 at 14:10
here is the colored output (if you open it in terminal) gist.github.com/ridvansumset/40e9223262361fa9590aa5e5bc5e10a6
– Rıdvan Sumset
Oct 2 '18 at 9:11
add a comment |
Welcome to Hell. I faced this too, and all I had to blame are unsigned Nvidia modules, or similar thing. So, I assume this isn't the first time you boot into Ubuntu since the first setup? And you got Nvidia drivers as well?
First of all, there has to be issues reported in your logs from
$ journalctl
If so, add to your post.
As a workaround, disable Secure Boot in your BIOS setup, if it's on (I mean, it MUST be on, because usually it blocks unsigned gfx driver from loading to kernel. This was my issue, however, since I left Ubuntu long time ago, I have different issue, for ex., on Arch, where desktop environment literally won't load up). Write me back with your results
I've been using ubuntu since may 2017. I had nvidia drivers but I usedsudo apt-get purge nvidia*
I don't know if I still have them. Secure boot was ON I disabled it from Windows BIOS. Then I tried to login and failed again.journalctl
command's output is too big but I saw a line says secureboot: secure boot could not be determined(mode 0).
– Rıdvan Sumset
Sep 30 '18 at 19:53
I also tried to login in recovery mode but still no luck :/
– Rıdvan Sumset
Sep 30 '18 at 19:57
1
bugzilla.redhat.com/show_bug.cgi?id=1451071 Also, it's obvious journalctl will output much info, but it's the system logs, it's supposed to be like that. I don't feel that the error message you shared is enough for clarifying. You could save all the error lines in some file and report back if possible like $ journalctl 2> ~/errors.txt
– xt1zer
Oct 1 '18 at 14:10
here is the colored output (if you open it in terminal) gist.github.com/ridvansumset/40e9223262361fa9590aa5e5bc5e10a6
– Rıdvan Sumset
Oct 2 '18 at 9:11
add a comment |
Welcome to Hell. I faced this too, and all I had to blame are unsigned Nvidia modules, or similar thing. So, I assume this isn't the first time you boot into Ubuntu since the first setup? And you got Nvidia drivers as well?
First of all, there has to be issues reported in your logs from
$ journalctl
If so, add to your post.
As a workaround, disable Secure Boot in your BIOS setup, if it's on (I mean, it MUST be on, because usually it blocks unsigned gfx driver from loading to kernel. This was my issue, however, since I left Ubuntu long time ago, I have different issue, for ex., on Arch, where desktop environment literally won't load up). Write me back with your results
Welcome to Hell. I faced this too, and all I had to blame are unsigned Nvidia modules, or similar thing. So, I assume this isn't the first time you boot into Ubuntu since the first setup? And you got Nvidia drivers as well?
First of all, there has to be issues reported in your logs from
$ journalctl
If so, add to your post.
As a workaround, disable Secure Boot in your BIOS setup, if it's on (I mean, it MUST be on, because usually it blocks unsigned gfx driver from loading to kernel. This was my issue, however, since I left Ubuntu long time ago, I have different issue, for ex., on Arch, where desktop environment literally won't load up). Write me back with your results
answered Sep 30 '18 at 15:29
xt1zerxt1zer
789
789
I've been using ubuntu since may 2017. I had nvidia drivers but I usedsudo apt-get purge nvidia*
I don't know if I still have them. Secure boot was ON I disabled it from Windows BIOS. Then I tried to login and failed again.journalctl
command's output is too big but I saw a line says secureboot: secure boot could not be determined(mode 0).
– Rıdvan Sumset
Sep 30 '18 at 19:53
I also tried to login in recovery mode but still no luck :/
– Rıdvan Sumset
Sep 30 '18 at 19:57
1
bugzilla.redhat.com/show_bug.cgi?id=1451071 Also, it's obvious journalctl will output much info, but it's the system logs, it's supposed to be like that. I don't feel that the error message you shared is enough for clarifying. You could save all the error lines in some file and report back if possible like $ journalctl 2> ~/errors.txt
– xt1zer
Oct 1 '18 at 14:10
here is the colored output (if you open it in terminal) gist.github.com/ridvansumset/40e9223262361fa9590aa5e5bc5e10a6
– Rıdvan Sumset
Oct 2 '18 at 9:11
add a comment |
I've been using ubuntu since may 2017. I had nvidia drivers but I usedsudo apt-get purge nvidia*
I don't know if I still have them. Secure boot was ON I disabled it from Windows BIOS. Then I tried to login and failed again.journalctl
command's output is too big but I saw a line says secureboot: secure boot could not be determined(mode 0).
– Rıdvan Sumset
Sep 30 '18 at 19:53
I also tried to login in recovery mode but still no luck :/
– Rıdvan Sumset
Sep 30 '18 at 19:57
1
bugzilla.redhat.com/show_bug.cgi?id=1451071 Also, it's obvious journalctl will output much info, but it's the system logs, it's supposed to be like that. I don't feel that the error message you shared is enough for clarifying. You could save all the error lines in some file and report back if possible like $ journalctl 2> ~/errors.txt
– xt1zer
Oct 1 '18 at 14:10
here is the colored output (if you open it in terminal) gist.github.com/ridvansumset/40e9223262361fa9590aa5e5bc5e10a6
– Rıdvan Sumset
Oct 2 '18 at 9:11
I've been using ubuntu since may 2017. I had nvidia drivers but I used
sudo apt-get purge nvidia*
I don't know if I still have them. Secure boot was ON I disabled it from Windows BIOS. Then I tried to login and failed again. journalctl
command's output is too big but I saw a line says secureboot: secure boot could not be determined(mode 0).– Rıdvan Sumset
Sep 30 '18 at 19:53
I've been using ubuntu since may 2017. I had nvidia drivers but I used
sudo apt-get purge nvidia*
I don't know if I still have them. Secure boot was ON I disabled it from Windows BIOS. Then I tried to login and failed again. journalctl
command's output is too big but I saw a line says secureboot: secure boot could not be determined(mode 0).– Rıdvan Sumset
Sep 30 '18 at 19:53
I also tried to login in recovery mode but still no luck :/
– Rıdvan Sumset
Sep 30 '18 at 19:57
I also tried to login in recovery mode but still no luck :/
– Rıdvan Sumset
Sep 30 '18 at 19:57
1
1
bugzilla.redhat.com/show_bug.cgi?id=1451071 Also, it's obvious journalctl will output much info, but it's the system logs, it's supposed to be like that. I don't feel that the error message you shared is enough for clarifying. You could save all the error lines in some file and report back if possible like $ journalctl 2> ~/errors.txt
– xt1zer
Oct 1 '18 at 14:10
bugzilla.redhat.com/show_bug.cgi?id=1451071 Also, it's obvious journalctl will output much info, but it's the system logs, it's supposed to be like that. I don't feel that the error message you shared is enough for clarifying. You could save all the error lines in some file and report back if possible like $ journalctl 2> ~/errors.txt
– xt1zer
Oct 1 '18 at 14:10
here is the colored output (if you open it in terminal) gist.github.com/ridvansumset/40e9223262361fa9590aa5e5bc5e10a6
– Rıdvan Sumset
Oct 2 '18 at 9:11
here is the colored output (if you open it in terminal) gist.github.com/ridvansumset/40e9223262361fa9590aa5e5bc5e10a6
– Rıdvan Sumset
Oct 2 '18 at 9:11
add a comment |
1. Problem description
Nvidia-396, which you have installed intently or unawarely auto-installed by other related package, such as swig, can not properly used in utuntu 16.04.
2. Solution
The best way to solve the problem would be ever find the miss-operation firstly. To do this, firstly, you need to check your command history by :
vi ~/.bash_history
and then search "sudo" keywords which indicate essential command, and find suspects. In my case, it is
sudo install swig
Finally, revert it by :
sudo apt-get purge swig
CAUTION : PLEASE NEVER DO
sudo apt-get upgrade
It will install newest package of your whole system which will include nividia-396
New contributor
add a comment |
1. Problem description
Nvidia-396, which you have installed intently or unawarely auto-installed by other related package, such as swig, can not properly used in utuntu 16.04.
2. Solution
The best way to solve the problem would be ever find the miss-operation firstly. To do this, firstly, you need to check your command history by :
vi ~/.bash_history
and then search "sudo" keywords which indicate essential command, and find suspects. In my case, it is
sudo install swig
Finally, revert it by :
sudo apt-get purge swig
CAUTION : PLEASE NEVER DO
sudo apt-get upgrade
It will install newest package of your whole system which will include nividia-396
New contributor
add a comment |
1. Problem description
Nvidia-396, which you have installed intently or unawarely auto-installed by other related package, such as swig, can not properly used in utuntu 16.04.
2. Solution
The best way to solve the problem would be ever find the miss-operation firstly. To do this, firstly, you need to check your command history by :
vi ~/.bash_history
and then search "sudo" keywords which indicate essential command, and find suspects. In my case, it is
sudo install swig
Finally, revert it by :
sudo apt-get purge swig
CAUTION : PLEASE NEVER DO
sudo apt-get upgrade
It will install newest package of your whole system which will include nividia-396
New contributor
1. Problem description
Nvidia-396, which you have installed intently or unawarely auto-installed by other related package, such as swig, can not properly used in utuntu 16.04.
2. Solution
The best way to solve the problem would be ever find the miss-operation firstly. To do this, firstly, you need to check your command history by :
vi ~/.bash_history
and then search "sudo" keywords which indicate essential command, and find suspects. In my case, it is
sudo install swig
Finally, revert it by :
sudo apt-get purge swig
CAUTION : PLEASE NEVER DO
sudo apt-get upgrade
It will install newest package of your whole system which will include nividia-396
New contributor
New contributor
answered 1 hour ago
user936845user936845
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2f1079737%2fcorrect-password-fails-to-login-login-loop-in-ubuntu-16-04%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
Also, how can I go back to login screen after entering terminal with CTRL+ALT+F3?
– Rıdvan Sumset
Sep 30 '18 at 14:37
In 16.04, press CTRL+ALT+F7 to return to the login screen (or the desktop if you are already logged in).
– danzel
Sep 30 '18 at 15:12