Ubuntu 14.04 Returns to Login Screen After Login
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
When I type in my password to my newly installed Ubuntu 14.04 computer, it returns me to the login screen. I've seen other answers but those were to Ubuntu 13.04 and older and didn't work.
14.04 login login-screen
add a comment |
When I type in my password to my newly installed Ubuntu 14.04 computer, it returns me to the login screen. I've seen other answers but those were to Ubuntu 13.04 and older and didn't work.
14.04 login login-screen
1
Ctrl+Alt+F1, login,rm .Xauthority
, Alt+F7, login and report back.
– s3lph
May 27 '15 at 14:30
But where is the .Xauthority file, I've seen that answer before but on Ubuntu 13.04 and older.
– jjjhfam
May 27 '15 at 14:43
It is a hidden file in/home/username
folder also known as your (username's) home folder. Therm
command deletes the file. It will be recreated the next time you login using the GUI.
– user68186
May 27 '15 at 14:51
As I said, I've never been in my account so when I am in that directory and type 'ls -a' I do not see it.
– jjjhfam
May 27 '15 at 15:41
add a comment |
When I type in my password to my newly installed Ubuntu 14.04 computer, it returns me to the login screen. I've seen other answers but those were to Ubuntu 13.04 and older and didn't work.
14.04 login login-screen
When I type in my password to my newly installed Ubuntu 14.04 computer, it returns me to the login screen. I've seen other answers but those were to Ubuntu 13.04 and older and didn't work.
14.04 login login-screen
14.04 login login-screen
edited May 27 '15 at 14:46
jjjhfam
asked May 27 '15 at 14:25
jjjhfamjjjhfam
21113
21113
1
Ctrl+Alt+F1, login,rm .Xauthority
, Alt+F7, login and report back.
– s3lph
May 27 '15 at 14:30
But where is the .Xauthority file, I've seen that answer before but on Ubuntu 13.04 and older.
– jjjhfam
May 27 '15 at 14:43
It is a hidden file in/home/username
folder also known as your (username's) home folder. Therm
command deletes the file. It will be recreated the next time you login using the GUI.
– user68186
May 27 '15 at 14:51
As I said, I've never been in my account so when I am in that directory and type 'ls -a' I do not see it.
– jjjhfam
May 27 '15 at 15:41
add a comment |
1
Ctrl+Alt+F1, login,rm .Xauthority
, Alt+F7, login and report back.
– s3lph
May 27 '15 at 14:30
But where is the .Xauthority file, I've seen that answer before but on Ubuntu 13.04 and older.
– jjjhfam
May 27 '15 at 14:43
It is a hidden file in/home/username
folder also known as your (username's) home folder. Therm
command deletes the file. It will be recreated the next time you login using the GUI.
– user68186
May 27 '15 at 14:51
As I said, I've never been in my account so when I am in that directory and type 'ls -a' I do not see it.
– jjjhfam
May 27 '15 at 15:41
1
1
Ctrl+Alt+F1, login,
rm .Xauthority
, Alt+F7, login and report back.– s3lph
May 27 '15 at 14:30
Ctrl+Alt+F1, login,
rm .Xauthority
, Alt+F7, login and report back.– s3lph
May 27 '15 at 14:30
But where is the .Xauthority file, I've seen that answer before but on Ubuntu 13.04 and older.
– jjjhfam
May 27 '15 at 14:43
But where is the .Xauthority file, I've seen that answer before but on Ubuntu 13.04 and older.
– jjjhfam
May 27 '15 at 14:43
It is a hidden file in
/home/username
folder also known as your (username's) home folder. The rm
command deletes the file. It will be recreated the next time you login using the GUI.– user68186
May 27 '15 at 14:51
It is a hidden file in
/home/username
folder also known as your (username's) home folder. The rm
command deletes the file. It will be recreated the next time you login using the GUI.– user68186
May 27 '15 at 14:51
As I said, I've never been in my account so when I am in that directory and type 'ls -a' I do not see it.
– jjjhfam
May 27 '15 at 15:41
As I said, I've never been in my account so when I am in that directory and type 'ls -a' I do not see it.
– jjjhfam
May 27 '15 at 15:41
add a comment |
7 Answers
7
active
oldest
votes
Press Ctrl + Alt + F1 and log in there and run:
sudo chown -R $USER:$USER $HOME
Then press Ctrl + Alt + F7 and try to log in.
This worked like charm on Ubuntu 18.04 with a difference of hitting Ctrl + Alt + F2 to get to text terminal session and Ctrl + Alt + F1 to get back to GUI session
– Anton Matosov
Mar 31 at 3:16
add a comment |
Look at here: Can't login to Ubuntu 14.04 after upgrade maybe can help you.
Check the
$HOME
permission and owner,chown $USER:$USER -R $HOME; chmod +x -R $HOME
, or try to use a Guest Session, or tryadduser
to create a user then login.Try reinstall Ubuntu Desktop,
sudo apt-get install --reinstall ubuntu-desktop ubuntu-session
.If all above can't work, maybe the lightdm is break, try to fix
sudo apt-get install lightdm --reinstall
.Or, just try to use kdm & Kde desktop:
sudo apt-get install kubuntu-desktop kde-standard
. (。・_・。)
You seem to be having trouble typing "reinstall", but I was able to add another user account and then add myself to the sudo file. Thanks!
– jjjhfam
May 27 '15 at 16:30
Thx. Does it that mean you can login ubuntu with another account? If so, just backup your old$HOME
directory, and create a new$HOME
directory then replace it. (´・ω・`)
– scue
May 29 '15 at 13:58
Yep, I just went into the virtual terminal and moved the files I wanted from old to new account.
– jjjhfam
May 29 '15 at 20:18
2
Don't executechmod +x -R $HOME
, it will make ALL files in $HOME executable. Please change this in the original comment.
– Minras
Jan 23 '17 at 10:34
I was able to ssh into my account, and execute the reinstall of Unbuntu Dekstop from there. I restarted the VM and it was fixed.
– nixkuroi
Apr 8 at 19:35
add a comment |
I had same issue i was setting up oracle and messed up with .bashrc
PATH
variable, with this i could not get past the login screen. Thing that solved my issue was that, in .bashrc
, I accidentally did not append $PATH:
in PATH
variable.
I wrote:
PATH=<other paths>
Correct format:
PATH=$PATH:<other paths>
This worked for me, if this is the case it should work for you too.
add a comment |
I had similar issue on fresh 18.04 install. Safemode worked well, normal mode kept kicking me out after logging in. UI also lagged during animations, so it was clear that was a graphics issue. So I just updated my Nvidia drivers and it worked.
sudo add-apt-repository ppa:graphics-drivers
sudo apt-get update
sudo apt-get install nvidia-390
add a comment |
Do experience any graphical glitches?
This might be the result of Unity not beeing able to start due to a problem with getting 3D acceleration - so your graphics-card driver is in question (thanks for nothing compiz).
Do you happen to know which graphics card you are using?
When in doubt you can press CTRL+ALT+F1, login, type:
lspic | grep VGA
usually you ll get something like
you@yourPc:~$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GK110B [GeForce GTX 780 Ti] (rev a1)
You'll then have to update your graphics-card driver, which either might be:
ATI/AMD:
sudo apt-get install fglrx
NVIDIA:
sudo apt-get install nvidia-current
Intel cards usualy don't cause problems.
If this all did not help you might consider booting an older kernel from GRUB, if any is installed.
(you can return to your graphical enviroment by pressing CTRL+ALT+F7)
add a comment |
I had the same problem in 16.04
rm .Xauthority // like the_Seppi said
sudo chown -R $USER:$USER $HOME // like praveen said
chmod +x -R $HOME
and a reboot
did it fore me
3
Whychmod +x -R $HOME
? it will make ALL files in $HOME executable.
– Minras
Jan 23 '17 at 10:36
add a comment |
I had same problem with Ubuntu 18.10 and following method help me:
At the login screen use Alt+Ctrl+F3 to access the command line login method.
Log in to the shell with your username and password.
Uninstall and reinstall Ubuntu lightdm. Run the following (be sure to connect to the network):
sudo apt-get purge lightdm
sudo apt-get install lightdm
dpkg-reconfigure lightdm
Once reconfigured, now reboot.
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%2f628974%2fubuntu-14-04-returns-to-login-screen-after-login%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
Press Ctrl + Alt + F1 and log in there and run:
sudo chown -R $USER:$USER $HOME
Then press Ctrl + Alt + F7 and try to log in.
This worked like charm on Ubuntu 18.04 with a difference of hitting Ctrl + Alt + F2 to get to text terminal session and Ctrl + Alt + F1 to get back to GUI session
– Anton Matosov
Mar 31 at 3:16
add a comment |
Press Ctrl + Alt + F1 and log in there and run:
sudo chown -R $USER:$USER $HOME
Then press Ctrl + Alt + F7 and try to log in.
This worked like charm on Ubuntu 18.04 with a difference of hitting Ctrl + Alt + F2 to get to text terminal session and Ctrl + Alt + F1 to get back to GUI session
– Anton Matosov
Mar 31 at 3:16
add a comment |
Press Ctrl + Alt + F1 and log in there and run:
sudo chown -R $USER:$USER $HOME
Then press Ctrl + Alt + F7 and try to log in.
Press Ctrl + Alt + F1 and log in there and run:
sudo chown -R $USER:$USER $HOME
Then press Ctrl + Alt + F7 and try to log in.
edited Aug 17 '16 at 21:33
Hizqeel
1,75551421
1,75551421
answered Dec 16 '15 at 14:07
praveenpraveen
258312
258312
This worked like charm on Ubuntu 18.04 with a difference of hitting Ctrl + Alt + F2 to get to text terminal session and Ctrl + Alt + F1 to get back to GUI session
– Anton Matosov
Mar 31 at 3:16
add a comment |
This worked like charm on Ubuntu 18.04 with a difference of hitting Ctrl + Alt + F2 to get to text terminal session and Ctrl + Alt + F1 to get back to GUI session
– Anton Matosov
Mar 31 at 3:16
This worked like charm on Ubuntu 18.04 with a difference of hitting Ctrl + Alt + F2 to get to text terminal session and Ctrl + Alt + F1 to get back to GUI session
– Anton Matosov
Mar 31 at 3:16
This worked like charm on Ubuntu 18.04 with a difference of hitting Ctrl + Alt + F2 to get to text terminal session and Ctrl + Alt + F1 to get back to GUI session
– Anton Matosov
Mar 31 at 3:16
add a comment |
Look at here: Can't login to Ubuntu 14.04 after upgrade maybe can help you.
Check the
$HOME
permission and owner,chown $USER:$USER -R $HOME; chmod +x -R $HOME
, or try to use a Guest Session, or tryadduser
to create a user then login.Try reinstall Ubuntu Desktop,
sudo apt-get install --reinstall ubuntu-desktop ubuntu-session
.If all above can't work, maybe the lightdm is break, try to fix
sudo apt-get install lightdm --reinstall
.Or, just try to use kdm & Kde desktop:
sudo apt-get install kubuntu-desktop kde-standard
. (。・_・。)
You seem to be having trouble typing "reinstall", but I was able to add another user account and then add myself to the sudo file. Thanks!
– jjjhfam
May 27 '15 at 16:30
Thx. Does it that mean you can login ubuntu with another account? If so, just backup your old$HOME
directory, and create a new$HOME
directory then replace it. (´・ω・`)
– scue
May 29 '15 at 13:58
Yep, I just went into the virtual terminal and moved the files I wanted from old to new account.
– jjjhfam
May 29 '15 at 20:18
2
Don't executechmod +x -R $HOME
, it will make ALL files in $HOME executable. Please change this in the original comment.
– Minras
Jan 23 '17 at 10:34
I was able to ssh into my account, and execute the reinstall of Unbuntu Dekstop from there. I restarted the VM and it was fixed.
– nixkuroi
Apr 8 at 19:35
add a comment |
Look at here: Can't login to Ubuntu 14.04 after upgrade maybe can help you.
Check the
$HOME
permission and owner,chown $USER:$USER -R $HOME; chmod +x -R $HOME
, or try to use a Guest Session, or tryadduser
to create a user then login.Try reinstall Ubuntu Desktop,
sudo apt-get install --reinstall ubuntu-desktop ubuntu-session
.If all above can't work, maybe the lightdm is break, try to fix
sudo apt-get install lightdm --reinstall
.Or, just try to use kdm & Kde desktop:
sudo apt-get install kubuntu-desktop kde-standard
. (。・_・。)
You seem to be having trouble typing "reinstall", but I was able to add another user account and then add myself to the sudo file. Thanks!
– jjjhfam
May 27 '15 at 16:30
Thx. Does it that mean you can login ubuntu with another account? If so, just backup your old$HOME
directory, and create a new$HOME
directory then replace it. (´・ω・`)
– scue
May 29 '15 at 13:58
Yep, I just went into the virtual terminal and moved the files I wanted from old to new account.
– jjjhfam
May 29 '15 at 20:18
2
Don't executechmod +x -R $HOME
, it will make ALL files in $HOME executable. Please change this in the original comment.
– Minras
Jan 23 '17 at 10:34
I was able to ssh into my account, and execute the reinstall of Unbuntu Dekstop from there. I restarted the VM and it was fixed.
– nixkuroi
Apr 8 at 19:35
add a comment |
Look at here: Can't login to Ubuntu 14.04 after upgrade maybe can help you.
Check the
$HOME
permission and owner,chown $USER:$USER -R $HOME; chmod +x -R $HOME
, or try to use a Guest Session, or tryadduser
to create a user then login.Try reinstall Ubuntu Desktop,
sudo apt-get install --reinstall ubuntu-desktop ubuntu-session
.If all above can't work, maybe the lightdm is break, try to fix
sudo apt-get install lightdm --reinstall
.Or, just try to use kdm & Kde desktop:
sudo apt-get install kubuntu-desktop kde-standard
. (。・_・。)
Look at here: Can't login to Ubuntu 14.04 after upgrade maybe can help you.
Check the
$HOME
permission and owner,chown $USER:$USER -R $HOME; chmod +x -R $HOME
, or try to use a Guest Session, or tryadduser
to create a user then login.Try reinstall Ubuntu Desktop,
sudo apt-get install --reinstall ubuntu-desktop ubuntu-session
.If all above can't work, maybe the lightdm is break, try to fix
sudo apt-get install lightdm --reinstall
.Or, just try to use kdm & Kde desktop:
sudo apt-get install kubuntu-desktop kde-standard
. (。・_・。)
edited May 29 '15 at 13:53
answered May 27 '15 at 14:48
scuescue
393
393
You seem to be having trouble typing "reinstall", but I was able to add another user account and then add myself to the sudo file. Thanks!
– jjjhfam
May 27 '15 at 16:30
Thx. Does it that mean you can login ubuntu with another account? If so, just backup your old$HOME
directory, and create a new$HOME
directory then replace it. (´・ω・`)
– scue
May 29 '15 at 13:58
Yep, I just went into the virtual terminal and moved the files I wanted from old to new account.
– jjjhfam
May 29 '15 at 20:18
2
Don't executechmod +x -R $HOME
, it will make ALL files in $HOME executable. Please change this in the original comment.
– Minras
Jan 23 '17 at 10:34
I was able to ssh into my account, and execute the reinstall of Unbuntu Dekstop from there. I restarted the VM and it was fixed.
– nixkuroi
Apr 8 at 19:35
add a comment |
You seem to be having trouble typing "reinstall", but I was able to add another user account and then add myself to the sudo file. Thanks!
– jjjhfam
May 27 '15 at 16:30
Thx. Does it that mean you can login ubuntu with another account? If so, just backup your old$HOME
directory, and create a new$HOME
directory then replace it. (´・ω・`)
– scue
May 29 '15 at 13:58
Yep, I just went into the virtual terminal and moved the files I wanted from old to new account.
– jjjhfam
May 29 '15 at 20:18
2
Don't executechmod +x -R $HOME
, it will make ALL files in $HOME executable. Please change this in the original comment.
– Minras
Jan 23 '17 at 10:34
I was able to ssh into my account, and execute the reinstall of Unbuntu Dekstop from there. I restarted the VM and it was fixed.
– nixkuroi
Apr 8 at 19:35
You seem to be having trouble typing "reinstall", but I was able to add another user account and then add myself to the sudo file. Thanks!
– jjjhfam
May 27 '15 at 16:30
You seem to be having trouble typing "reinstall", but I was able to add another user account and then add myself to the sudo file. Thanks!
– jjjhfam
May 27 '15 at 16:30
Thx. Does it that mean you can login ubuntu with another account? If so, just backup your old
$HOME
directory, and create a new $HOME
directory then replace it. (´・ω・`)– scue
May 29 '15 at 13:58
Thx. Does it that mean you can login ubuntu with another account? If so, just backup your old
$HOME
directory, and create a new $HOME
directory then replace it. (´・ω・`)– scue
May 29 '15 at 13:58
Yep, I just went into the virtual terminal and moved the files I wanted from old to new account.
– jjjhfam
May 29 '15 at 20:18
Yep, I just went into the virtual terminal and moved the files I wanted from old to new account.
– jjjhfam
May 29 '15 at 20:18
2
2
Don't execute
chmod +x -R $HOME
, it will make ALL files in $HOME executable. Please change this in the original comment.– Minras
Jan 23 '17 at 10:34
Don't execute
chmod +x -R $HOME
, it will make ALL files in $HOME executable. Please change this in the original comment.– Minras
Jan 23 '17 at 10:34
I was able to ssh into my account, and execute the reinstall of Unbuntu Dekstop from there. I restarted the VM and it was fixed.
– nixkuroi
Apr 8 at 19:35
I was able to ssh into my account, and execute the reinstall of Unbuntu Dekstop from there. I restarted the VM and it was fixed.
– nixkuroi
Apr 8 at 19:35
add a comment |
I had same issue i was setting up oracle and messed up with .bashrc
PATH
variable, with this i could not get past the login screen. Thing that solved my issue was that, in .bashrc
, I accidentally did not append $PATH:
in PATH
variable.
I wrote:
PATH=<other paths>
Correct format:
PATH=$PATH:<other paths>
This worked for me, if this is the case it should work for you too.
add a comment |
I had same issue i was setting up oracle and messed up with .bashrc
PATH
variable, with this i could not get past the login screen. Thing that solved my issue was that, in .bashrc
, I accidentally did not append $PATH:
in PATH
variable.
I wrote:
PATH=<other paths>
Correct format:
PATH=$PATH:<other paths>
This worked for me, if this is the case it should work for you too.
add a comment |
I had same issue i was setting up oracle and messed up with .bashrc
PATH
variable, with this i could not get past the login screen. Thing that solved my issue was that, in .bashrc
, I accidentally did not append $PATH:
in PATH
variable.
I wrote:
PATH=<other paths>
Correct format:
PATH=$PATH:<other paths>
This worked for me, if this is the case it should work for you too.
I had same issue i was setting up oracle and messed up with .bashrc
PATH
variable, with this i could not get past the login screen. Thing that solved my issue was that, in .bashrc
, I accidentally did not append $PATH:
in PATH
variable.
I wrote:
PATH=<other paths>
Correct format:
PATH=$PATH:<other paths>
This worked for me, if this is the case it should work for you too.
edited Apr 12 '18 at 8:48
Eliah Kagan
83.5k22229369
83.5k22229369
answered Apr 12 '18 at 8:28
Piyush jainPiyush jain
111
111
add a comment |
add a comment |
I had similar issue on fresh 18.04 install. Safemode worked well, normal mode kept kicking me out after logging in. UI also lagged during animations, so it was clear that was a graphics issue. So I just updated my Nvidia drivers and it worked.
sudo add-apt-repository ppa:graphics-drivers
sudo apt-get update
sudo apt-get install nvidia-390
add a comment |
I had similar issue on fresh 18.04 install. Safemode worked well, normal mode kept kicking me out after logging in. UI also lagged during animations, so it was clear that was a graphics issue. So I just updated my Nvidia drivers and it worked.
sudo add-apt-repository ppa:graphics-drivers
sudo apt-get update
sudo apt-get install nvidia-390
add a comment |
I had similar issue on fresh 18.04 install. Safemode worked well, normal mode kept kicking me out after logging in. UI also lagged during animations, so it was clear that was a graphics issue. So I just updated my Nvidia drivers and it worked.
sudo add-apt-repository ppa:graphics-drivers
sudo apt-get update
sudo apt-get install nvidia-390
I had similar issue on fresh 18.04 install. Safemode worked well, normal mode kept kicking me out after logging in. UI also lagged during animations, so it was clear that was a graphics issue. So I just updated my Nvidia drivers and it worked.
sudo add-apt-repository ppa:graphics-drivers
sudo apt-get update
sudo apt-get install nvidia-390
answered May 6 '18 at 6:05
georgegachgeorgegach
111
111
add a comment |
add a comment |
Do experience any graphical glitches?
This might be the result of Unity not beeing able to start due to a problem with getting 3D acceleration - so your graphics-card driver is in question (thanks for nothing compiz).
Do you happen to know which graphics card you are using?
When in doubt you can press CTRL+ALT+F1, login, type:
lspic | grep VGA
usually you ll get something like
you@yourPc:~$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GK110B [GeForce GTX 780 Ti] (rev a1)
You'll then have to update your graphics-card driver, which either might be:
ATI/AMD:
sudo apt-get install fglrx
NVIDIA:
sudo apt-get install nvidia-current
Intel cards usualy don't cause problems.
If this all did not help you might consider booting an older kernel from GRUB, if any is installed.
(you can return to your graphical enviroment by pressing CTRL+ALT+F7)
add a comment |
Do experience any graphical glitches?
This might be the result of Unity not beeing able to start due to a problem with getting 3D acceleration - so your graphics-card driver is in question (thanks for nothing compiz).
Do you happen to know which graphics card you are using?
When in doubt you can press CTRL+ALT+F1, login, type:
lspic | grep VGA
usually you ll get something like
you@yourPc:~$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GK110B [GeForce GTX 780 Ti] (rev a1)
You'll then have to update your graphics-card driver, which either might be:
ATI/AMD:
sudo apt-get install fglrx
NVIDIA:
sudo apt-get install nvidia-current
Intel cards usualy don't cause problems.
If this all did not help you might consider booting an older kernel from GRUB, if any is installed.
(you can return to your graphical enviroment by pressing CTRL+ALT+F7)
add a comment |
Do experience any graphical glitches?
This might be the result of Unity not beeing able to start due to a problem with getting 3D acceleration - so your graphics-card driver is in question (thanks for nothing compiz).
Do you happen to know which graphics card you are using?
When in doubt you can press CTRL+ALT+F1, login, type:
lspic | grep VGA
usually you ll get something like
you@yourPc:~$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GK110B [GeForce GTX 780 Ti] (rev a1)
You'll then have to update your graphics-card driver, which either might be:
ATI/AMD:
sudo apt-get install fglrx
NVIDIA:
sudo apt-get install nvidia-current
Intel cards usualy don't cause problems.
If this all did not help you might consider booting an older kernel from GRUB, if any is installed.
(you can return to your graphical enviroment by pressing CTRL+ALT+F7)
Do experience any graphical glitches?
This might be the result of Unity not beeing able to start due to a problem with getting 3D acceleration - so your graphics-card driver is in question (thanks for nothing compiz).
Do you happen to know which graphics card you are using?
When in doubt you can press CTRL+ALT+F1, login, type:
lspic | grep VGA
usually you ll get something like
you@yourPc:~$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GK110B [GeForce GTX 780 Ti] (rev a1)
You'll then have to update your graphics-card driver, which either might be:
ATI/AMD:
sudo apt-get install fglrx
NVIDIA:
sudo apt-get install nvidia-current
Intel cards usualy don't cause problems.
If this all did not help you might consider booting an older kernel from GRUB, if any is installed.
(you can return to your graphical enviroment by pressing CTRL+ALT+F7)
answered May 27 '15 at 17:37
user1078701user1078701
666
666
add a comment |
add a comment |
I had the same problem in 16.04
rm .Xauthority // like the_Seppi said
sudo chown -R $USER:$USER $HOME // like praveen said
chmod +x -R $HOME
and a reboot
did it fore me
3
Whychmod +x -R $HOME
? it will make ALL files in $HOME executable.
– Minras
Jan 23 '17 at 10:36
add a comment |
I had the same problem in 16.04
rm .Xauthority // like the_Seppi said
sudo chown -R $USER:$USER $HOME // like praveen said
chmod +x -R $HOME
and a reboot
did it fore me
3
Whychmod +x -R $HOME
? it will make ALL files in $HOME executable.
– Minras
Jan 23 '17 at 10:36
add a comment |
I had the same problem in 16.04
rm .Xauthority // like the_Seppi said
sudo chown -R $USER:$USER $HOME // like praveen said
chmod +x -R $HOME
and a reboot
did it fore me
I had the same problem in 16.04
rm .Xauthority // like the_Seppi said
sudo chown -R $USER:$USER $HOME // like praveen said
chmod +x -R $HOME
and a reboot
did it fore me
answered Aug 17 '16 at 13:06
D MD M
11
11
3
Whychmod +x -R $HOME
? it will make ALL files in $HOME executable.
– Minras
Jan 23 '17 at 10:36
add a comment |
3
Whychmod +x -R $HOME
? it will make ALL files in $HOME executable.
– Minras
Jan 23 '17 at 10:36
3
3
Why
chmod +x -R $HOME
? it will make ALL files in $HOME executable.– Minras
Jan 23 '17 at 10:36
Why
chmod +x -R $HOME
? it will make ALL files in $HOME executable.– Minras
Jan 23 '17 at 10:36
add a comment |
I had same problem with Ubuntu 18.10 and following method help me:
At the login screen use Alt+Ctrl+F3 to access the command line login method.
Log in to the shell with your username and password.
Uninstall and reinstall Ubuntu lightdm. Run the following (be sure to connect to the network):
sudo apt-get purge lightdm
sudo apt-get install lightdm
dpkg-reconfigure lightdm
Once reconfigured, now reboot.
add a comment |
I had same problem with Ubuntu 18.10 and following method help me:
At the login screen use Alt+Ctrl+F3 to access the command line login method.
Log in to the shell with your username and password.
Uninstall and reinstall Ubuntu lightdm. Run the following (be sure to connect to the network):
sudo apt-get purge lightdm
sudo apt-get install lightdm
dpkg-reconfigure lightdm
Once reconfigured, now reboot.
add a comment |
I had same problem with Ubuntu 18.10 and following method help me:
At the login screen use Alt+Ctrl+F3 to access the command line login method.
Log in to the shell with your username and password.
Uninstall and reinstall Ubuntu lightdm. Run the following (be sure to connect to the network):
sudo apt-get purge lightdm
sudo apt-get install lightdm
dpkg-reconfigure lightdm
Once reconfigured, now reboot.
I had same problem with Ubuntu 18.10 and following method help me:
At the login screen use Alt+Ctrl+F3 to access the command line login method.
Log in to the shell with your username and password.
Uninstall and reinstall Ubuntu lightdm. Run the following (be sure to connect to the network):
sudo apt-get purge lightdm
sudo apt-get install lightdm
dpkg-reconfigure lightdm
Once reconfigured, now reboot.
edited Apr 2 at 20:28
Kulfy
5,36861945
5,36861945
answered Apr 2 at 20:22
Sadegh-khanSadegh-khan
1013
1013
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%2f628974%2fubuntu-14-04-returns-to-login-screen-after-login%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
1
Ctrl+Alt+F1, login,
rm .Xauthority
, Alt+F7, login and report back.– s3lph
May 27 '15 at 14:30
But where is the .Xauthority file, I've seen that answer before but on Ubuntu 13.04 and older.
– jjjhfam
May 27 '15 at 14:43
It is a hidden file in
/home/username
folder also known as your (username's) home folder. Therm
command deletes the file. It will be recreated the next time you login using the GUI.– user68186
May 27 '15 at 14:51
As I said, I've never been in my account so when I am in that directory and type 'ls -a' I do not see it.
– jjjhfam
May 27 '15 at 15:41