Can't login, although password is correct [duplicate]












0















This question already has an answer here:




  • Ubuntu gets stuck in a login loop

    40 answers




Here what's happening when I try to log in.



I'm entering the right password



login screen



users at login screen



It brings me back me to the login screen.



I tried to change password via another user but it didn't help.










share|improve this question















marked as duplicate by Zanna, karel, pomsky, Kulfy, Thomas Dec 29 '18 at 9:08


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • If you have no space in your $HOME (/home/user/ directory), there will be no space for required working-files used by the gui, and login cannot proceed so you are returned to the login dialog. As Kulfy suggested I'd suggest switching to terminal (ctrl+alt+f4) and login, it'll prove your credentials are fine, and then you can df -hl to see if you have enough disk space free to enable gui to work; if not you can find some files to delete, increasing space allowing gui login.
    – guiverc
    Nov 25 '18 at 21:30
















0















This question already has an answer here:




  • Ubuntu gets stuck in a login loop

    40 answers




Here what's happening when I try to log in.



I'm entering the right password



login screen



users at login screen



It brings me back me to the login screen.



I tried to change password via another user but it didn't help.










share|improve this question















marked as duplicate by Zanna, karel, pomsky, Kulfy, Thomas Dec 29 '18 at 9:08


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • If you have no space in your $HOME (/home/user/ directory), there will be no space for required working-files used by the gui, and login cannot proceed so you are returned to the login dialog. As Kulfy suggested I'd suggest switching to terminal (ctrl+alt+f4) and login, it'll prove your credentials are fine, and then you can df -hl to see if you have enough disk space free to enable gui to work; if not you can find some files to delete, increasing space allowing gui login.
    – guiverc
    Nov 25 '18 at 21:30














0












0








0








This question already has an answer here:




  • Ubuntu gets stuck in a login loop

    40 answers




Here what's happening when I try to log in.



I'm entering the right password



login screen



users at login screen



It brings me back me to the login screen.



I tried to change password via another user but it didn't help.










share|improve this question
















This question already has an answer here:




  • Ubuntu gets stuck in a login loop

    40 answers




Here what's happening when I try to log in.



I'm entering the right password



login screen



users at login screen



It brings me back me to the login screen.



I tried to change password via another user but it didn't help.





This question already has an answer here:




  • Ubuntu gets stuck in a login loop

    40 answers








login password users






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 28 '18 at 14:59









Zanna

50k13131239




50k13131239










asked Nov 25 '18 at 20:49









Itra

14712




14712




marked as duplicate by Zanna, karel, pomsky, Kulfy, Thomas Dec 29 '18 at 9:08


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






marked as duplicate by Zanna, karel, pomsky, Kulfy, Thomas Dec 29 '18 at 9:08


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • If you have no space in your $HOME (/home/user/ directory), there will be no space for required working-files used by the gui, and login cannot proceed so you are returned to the login dialog. As Kulfy suggested I'd suggest switching to terminal (ctrl+alt+f4) and login, it'll prove your credentials are fine, and then you can df -hl to see if you have enough disk space free to enable gui to work; if not you can find some files to delete, increasing space allowing gui login.
    – guiverc
    Nov 25 '18 at 21:30


















  • If you have no space in your $HOME (/home/user/ directory), there will be no space for required working-files used by the gui, and login cannot proceed so you are returned to the login dialog. As Kulfy suggested I'd suggest switching to terminal (ctrl+alt+f4) and login, it'll prove your credentials are fine, and then you can df -hl to see if you have enough disk space free to enable gui to work; if not you can find some files to delete, increasing space allowing gui login.
    – guiverc
    Nov 25 '18 at 21:30
















If you have no space in your $HOME (/home/user/ directory), there will be no space for required working-files used by the gui, and login cannot proceed so you are returned to the login dialog. As Kulfy suggested I'd suggest switching to terminal (ctrl+alt+f4) and login, it'll prove your credentials are fine, and then you can df -hl to see if you have enough disk space free to enable gui to work; if not you can find some files to delete, increasing space allowing gui login.
– guiverc
Nov 25 '18 at 21:30




If you have no space in your $HOME (/home/user/ directory), there will be no space for required working-files used by the gui, and login cannot proceed so you are returned to the login dialog. As Kulfy suggested I'd suggest switching to terminal (ctrl+alt+f4) and login, it'll prove your credentials are fine, and then you can df -hl to see if you have enough disk space free to enable gui to work; if not you can find some files to delete, increasing space allowing gui login.
– guiverc
Nov 25 '18 at 21:30










2 Answers
2






active

oldest

votes


















1














If you've been starting graphic applications from the terminal using sudo, that's what probably caused your problem. Always use sudo -H.




  • boot to the GRUB menu

  • choose Advanced Options

  • choose Recovery mode

  • choose Root access

  • at the # prompt, type:



    • sudo mount -o remount,rw / # remount the disk as rw


    • cd /home/your_username # change directory


    • ls -al .*thority* # list some files




You should see something like this...



-rw------- 1 your_username your_username 407910 Nov  2 08:56 .ICEauthority
-rw------- 1 your_username your_username 58 Jun 23 2017 .Xauthority


If it DOES NOT show -rw------- then...





  • sudo chmod 600 .*thority* # change file protection


If it DOES SHOW root root then...




  • sudo chown your_username:your_username .*thority* # change file ownership


  • reboot # reboot the computer



Reboot and see if you can log in.






share|improve this answer





















  • It works thanks :)
    – Itra
    Nov 26 '18 at 13:46



















-1














If you know root credentials, go into text-mode via Ctrl-Alt F2. Log in with root and set your password with sudo passwd Frag (it will ask you to enter the new password twice).






share|improve this answer





















  • I tried it, it's not that problem
    – Itra
    Dec 26 '18 at 15:07


















2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














If you've been starting graphic applications from the terminal using sudo, that's what probably caused your problem. Always use sudo -H.




  • boot to the GRUB menu

  • choose Advanced Options

  • choose Recovery mode

  • choose Root access

  • at the # prompt, type:



    • sudo mount -o remount,rw / # remount the disk as rw


    • cd /home/your_username # change directory


    • ls -al .*thority* # list some files




You should see something like this...



-rw------- 1 your_username your_username 407910 Nov  2 08:56 .ICEauthority
-rw------- 1 your_username your_username 58 Jun 23 2017 .Xauthority


If it DOES NOT show -rw------- then...





  • sudo chmod 600 .*thority* # change file protection


If it DOES SHOW root root then...




  • sudo chown your_username:your_username .*thority* # change file ownership


  • reboot # reboot the computer



Reboot and see if you can log in.






share|improve this answer





















  • It works thanks :)
    – Itra
    Nov 26 '18 at 13:46
















1














If you've been starting graphic applications from the terminal using sudo, that's what probably caused your problem. Always use sudo -H.




  • boot to the GRUB menu

  • choose Advanced Options

  • choose Recovery mode

  • choose Root access

  • at the # prompt, type:



    • sudo mount -o remount,rw / # remount the disk as rw


    • cd /home/your_username # change directory


    • ls -al .*thority* # list some files




You should see something like this...



-rw------- 1 your_username your_username 407910 Nov  2 08:56 .ICEauthority
-rw------- 1 your_username your_username 58 Jun 23 2017 .Xauthority


If it DOES NOT show -rw------- then...





  • sudo chmod 600 .*thority* # change file protection


If it DOES SHOW root root then...




  • sudo chown your_username:your_username .*thority* # change file ownership


  • reboot # reboot the computer



Reboot and see if you can log in.






share|improve this answer





















  • It works thanks :)
    – Itra
    Nov 26 '18 at 13:46














1












1








1






If you've been starting graphic applications from the terminal using sudo, that's what probably caused your problem. Always use sudo -H.




  • boot to the GRUB menu

  • choose Advanced Options

  • choose Recovery mode

  • choose Root access

  • at the # prompt, type:



    • sudo mount -o remount,rw / # remount the disk as rw


    • cd /home/your_username # change directory


    • ls -al .*thority* # list some files




You should see something like this...



-rw------- 1 your_username your_username 407910 Nov  2 08:56 .ICEauthority
-rw------- 1 your_username your_username 58 Jun 23 2017 .Xauthority


If it DOES NOT show -rw------- then...





  • sudo chmod 600 .*thority* # change file protection


If it DOES SHOW root root then...




  • sudo chown your_username:your_username .*thority* # change file ownership


  • reboot # reboot the computer



Reboot and see if you can log in.






share|improve this answer












If you've been starting graphic applications from the terminal using sudo, that's what probably caused your problem. Always use sudo -H.




  • boot to the GRUB menu

  • choose Advanced Options

  • choose Recovery mode

  • choose Root access

  • at the # prompt, type:



    • sudo mount -o remount,rw / # remount the disk as rw


    • cd /home/your_username # change directory


    • ls -al .*thority* # list some files




You should see something like this...



-rw------- 1 your_username your_username 407910 Nov  2 08:56 .ICEauthority
-rw------- 1 your_username your_username 58 Jun 23 2017 .Xauthority


If it DOES NOT show -rw------- then...





  • sudo chmod 600 .*thority* # change file protection


If it DOES SHOW root root then...




  • sudo chown your_username:your_username .*thority* # change file ownership


  • reboot # reboot the computer



Reboot and see if you can log in.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 26 '18 at 0:15









heynnema

18.1k22054




18.1k22054












  • It works thanks :)
    – Itra
    Nov 26 '18 at 13:46


















  • It works thanks :)
    – Itra
    Nov 26 '18 at 13:46
















It works thanks :)
– Itra
Nov 26 '18 at 13:46




It works thanks :)
– Itra
Nov 26 '18 at 13:46













-1














If you know root credentials, go into text-mode via Ctrl-Alt F2. Log in with root and set your password with sudo passwd Frag (it will ask you to enter the new password twice).






share|improve this answer





















  • I tried it, it's not that problem
    – Itra
    Dec 26 '18 at 15:07
















-1














If you know root credentials, go into text-mode via Ctrl-Alt F2. Log in with root and set your password with sudo passwd Frag (it will ask you to enter the new password twice).






share|improve this answer





















  • I tried it, it's not that problem
    – Itra
    Dec 26 '18 at 15:07














-1












-1








-1






If you know root credentials, go into text-mode via Ctrl-Alt F2. Log in with root and set your password with sudo passwd Frag (it will ask you to enter the new password twice).






share|improve this answer












If you know root credentials, go into text-mode via Ctrl-Alt F2. Log in with root and set your password with sudo passwd Frag (it will ask you to enter the new password twice).







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 25 '18 at 21:01









Turtle10000

1295




1295












  • I tried it, it's not that problem
    – Itra
    Dec 26 '18 at 15:07


















  • I tried it, it's not that problem
    – Itra
    Dec 26 '18 at 15:07
















I tried it, it's not that problem
– Itra
Dec 26 '18 at 15:07




I tried it, it's not that problem
– Itra
Dec 26 '18 at 15:07



Popular posts from this blog

Questions related to Moebius Transform of Characteristic Function of the Primes

List of scandals in India

Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?