Ubuntu won't login, password is true
My ubuntu won't login but password is true!
Here what's output. First image I try to login, and password is true!
It back me to login screen. I don't know I try to change password via other user and not working.
login password users
asked Nov 25 at 20:49
Itra
14612
add a comment |
My ubuntu won't login but password is true!
Here what's output. First image I try to login, and password is true!
It back me to login screen. I don't know I try to change password via other user and not working.
login password users
asked Nov 25 at 20:49
Itra
14612
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 candf -hlto 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 at 21:30
add a comment |
My ubuntu won't login but password is true!
Here what's output. First image I try to login, and password is true!
It back me to login screen. I don't know I try to change password via other user and not working.
login password users
asked Nov 25 at 20:49
Itra
14612
My ubuntu won't login but password is true!
Here what's output. First image I try to login, and password is true!
It back me to login screen. I don't know I try to change password via other user and not working.
login password users
login password users
asked Nov 25 at 20:49
Itra
14612
asked Nov 25 at 20:49
Itra
14612
asked Nov 25 at 20:49
Itra
14612
asked Nov 25 at 20:49
Itra
14612
asked Nov 25 at 20:49
Itra
14612
14612
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 candf -hlto 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 at 21:30
add a comment |
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 candf -hlto 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 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 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 at 21:30
add a comment |
3 Answers
3
active
oldest
votes
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 ownershipreboot# reboot the computer
Reboot and see if you can log in.
answered Nov 26 at 0:15
heynnema
18k22054
It works thanks :)
– Itra
Nov 26 at 13:46
add a comment |
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).
answered Nov 25 at 21:01
Turtle10000
1295
I tried it, it's not that problem
– Itra
yesterday
add a comment |
You'll be able to login with a new password, using these commands:
- Allow write access:
mount -rw -o remount /
- Check username:
ls /home
- Change password for username:
passwd username
edited yesterday
Pierre.Vriens
1,12761116
answered yesterday
Badr
1
New contributor
Badr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This is a duplicate of two other existing answers.
– karel
22 hours ago
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%2f1096011%2fubuntu-wont-login-password-is-true%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
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 ownershipreboot# reboot the computer
Reboot and see if you can log in.
answered Nov 26 at 0:15
heynnema
18k22054
It works thanks :)
– Itra
Nov 26 at 13:46
add a comment |
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 ownershipreboot# reboot the computer
Reboot and see if you can log in.
answered Nov 26 at 0:15
heynnema
18k22054
It works thanks :)
– Itra
Nov 26 at 13:46
add a comment |
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 ownershipreboot# reboot the computer
Reboot and see if you can log in.
answered Nov 26 at 0:15
heynnema
18k22054
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 ownershipreboot# reboot the computer
Reboot and see if you can log in.
answered Nov 26 at 0:15
heynnema
18k22054
answered Nov 26 at 0:15
heynnema
18k22054
answered Nov 26 at 0:15
heynnema
18k22054
answered Nov 26 at 0:15
heynnema
18k22054
18k22054
It works thanks :)
– Itra
Nov 26 at 13:46
add a comment |
It works thanks :)
– Itra
Nov 26 at 13:46
It works thanks :)
– Itra
Nov 26 at 13:46
It works thanks :)
– Itra
Nov 26 at 13:46
add a comment |
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).
answered Nov 25 at 21:01
Turtle10000
1295
I tried it, it's not that problem
– Itra
yesterday
add a comment |
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).
answered Nov 25 at 21:01
Turtle10000
1295
I tried it, it's not that problem
– Itra
yesterday
add a comment |
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).
answered Nov 25 at 21:01
Turtle10000
1295
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).
answered Nov 25 at 21:01
Turtle10000
1295
answered Nov 25 at 21:01
Turtle10000
1295
answered Nov 25 at 21:01
Turtle10000
1295
answered Nov 25 at 21:01
Turtle10000
1295
1295
I tried it, it's not that problem
– Itra
yesterday
add a comment |
I tried it, it's not that problem
– Itra
yesterday
I tried it, it's not that problem
– Itra
yesterday
I tried it, it's not that problem
– Itra
yesterday
add a comment |
You'll be able to login with a new password, using these commands:
- Allow write access:
mount -rw -o remount /
- Check username:
ls /home
- Change password for username:
passwd username
edited yesterday
Pierre.Vriens
1,12761116
answered yesterday
Badr
1
New contributor
Badr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This is a duplicate of two other existing answers.
– karel
22 hours ago
add a comment |
You'll be able to login with a new password, using these commands:
- Allow write access:
mount -rw -o remount /
- Check username:
ls /home
- Change password for username:
passwd username
edited yesterday
Pierre.Vriens
1,12761116
answered yesterday
Badr
1
New contributor
Badr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This is a duplicate of two other existing answers.
– karel
22 hours ago
add a comment |
You'll be able to login with a new password, using these commands:
- Allow write access:
mount -rw -o remount /
- Check username:
ls /home
- Change password for username:
passwd username
edited yesterday
Pierre.Vriens
1,12761116
answered yesterday
Badr
1
New contributor
Badr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
You'll be able to login with a new password, using these commands:
- Allow write access:
mount -rw -o remount /
- Check username:
ls /home
- Change password for username:
passwd username
edited yesterday
Pierre.Vriens
1,12761116
answered yesterday
Badr
1
New contributor
Badr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
Pierre.Vriens
1,12761116
edited yesterday
Pierre.Vriens
1,12761116
edited yesterday
Pierre.Vriens
1,12761116
1,12761116
answered yesterday
Badr
1
New contributor
Badr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
Badr
1
answered yesterday
Badr
1
1
New contributor
Badr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Badr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Badr is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This is a duplicate of two other existing answers.
– karel
22 hours ago
add a comment |
This is a duplicate of two other existing answers.
– karel
22 hours ago
This is a duplicate of two other existing answers.
– karel
22 hours ago
This is a duplicate of two other existing answers.
– karel
22 hours ago
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1096011%2fubuntu-wont-login-password-is-true%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
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 -hlto 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 at 21:30