Ubuntu infamous login loop
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I haven't recently updated Ubuntu or anything, it was working perfectly fine, until it suddenly refused to log me into desktop anymore. Whenever I login, it pauses for seconds, then brings the login screen again.
I've seen countless questions/articles/threads on the Internet explaining how to fix this, but sadly nothing has worked for me yet. I've even turned to second Google results page... Do you imagine?
Anyways, the only thing I recognize that could f**k up my machine is installing these two
http://www.ext2fsd.com/
and
https://www.paragon-software.com/home/linuxfs-windows/
installed by that order. Ext2Fsd didn't work for me, so I had to resort to Paragon's solution instead. The login loop problem only appeared after using these programs. I tried opening them, unmounting everything, remounting in read-only in hopes of reverting something that could've f**ked up, to no avail.
Of the many solutions that I found, one command seems to be very weird, which is strace xauth list, it almost always fails, either by telling me there's no .Xauthority file (after deliberately deleting it while following some article's advice), or just spitting walls of text that just look like a logcat.
I also tried doing strace startx, but it always complains that Xauthority could not be read, permission denied, and the whole tty blacks out, that I need to start another tty to continue tinkering.
I don't even know where to start debugging, and how to debug. I hope someone can help me.
NOTE: Someone suggested that the home directory could be encrypted, and to install ecryptfs-utils to fix it, I did so but didn't change a thing.
EDIT: Running df -hl shows that sda6 or / has 6% free, which is 34 GB.
EDIT: I tried installing LightDM instead of GDM3, but it has the same issue of redirecting back to login screen. I guess this eliminates the possibility of DM issues.
EDIT: I tried running sudo prime-select intel, but it didn't solve anything, I believe this means there's no problem with my NVIDIA card? Side note: I use bumblebee.
EDIT: Not really sure if this is needed, but I'd love to document everything. When I reboot the system and go into tty again, entering username automatically inserts another new line, which is directed to the password field, and it complains that the new line is a wrong password. It keeps looping this until it restarts/cleans the tty and asks for username again. The only solution to this is rebooting into the previous linux version, then rebooting into the current one again. But a reboot on the same version will introduce it and the loop goes on.
18.04 gnome xorg gdm xserver
asked Apr 2 at 20:03
mohkamfermohkamfer
43
|
show 2 more comments
I haven't recently updated Ubuntu or anything, it was working perfectly fine, until it suddenly refused to log me into desktop anymore. Whenever I login, it pauses for seconds, then brings the login screen again.
I've seen countless questions/articles/threads on the Internet explaining how to fix this, but sadly nothing has worked for me yet. I've even turned to second Google results page... Do you imagine?
Anyways, the only thing I recognize that could f**k up my machine is installing these two
http://www.ext2fsd.com/
and
https://www.paragon-software.com/home/linuxfs-windows/
installed by that order. Ext2Fsd didn't work for me, so I had to resort to Paragon's solution instead. The login loop problem only appeared after using these programs. I tried opening them, unmounting everything, remounting in read-only in hopes of reverting something that could've f**ked up, to no avail.
Of the many solutions that I found, one command seems to be very weird, which is strace xauth list, it almost always fails, either by telling me there's no .Xauthority file (after deliberately deleting it while following some article's advice), or just spitting walls of text that just look like a logcat.
I also tried doing strace startx, but it always complains that Xauthority could not be read, permission denied, and the whole tty blacks out, that I need to start another tty to continue tinkering.
I don't even know where to start debugging, and how to debug. I hope someone can help me.
NOTE: Someone suggested that the home directory could be encrypted, and to install ecryptfs-utils to fix it, I did so but didn't change a thing.
EDIT: Running df -hl shows that sda6 or / has 6% free, which is 34 GB.
EDIT: I tried installing LightDM instead of GDM3, but it has the same issue of redirecting back to login screen. I guess this eliminates the possibility of DM issues.
EDIT: I tried running sudo prime-select intel, but it didn't solve anything, I believe this means there's no problem with my NVIDIA card? Side note: I use bumblebee.
EDIT: Not really sure if this is needed, but I'd love to document everything. When I reboot the system and go into tty again, entering username automatically inserts another new line, which is directed to the password field, and it complains that the new line is a wrong password. It keeps looping this until it restarts/cleans the tty and asks for username again. The only solution to this is rebooting into the previous linux version, then rebooting into the current one again. But a reboot on the same version will introduce it and the loop goes on.
18.04 gnome xorg gdm xserver
asked Apr 2 at 20:03
mohkamfermohkamfer
43
You've documented many things that could now complicate things. If you've had no updates, installed nothing new nor changed any hardware but can no longer login - the first thing I check is I have space in $HOME (your user directory). If it's full or very-near-full a GUI login cannot proceed as it can't create temporary work files needed for gui operation, and you return to greeter/login screen. Login using a terminal anddf -hl(disk free - local drives, human output) & check you have space (text logins will work). This changes nothing, but eliminates one (primary) cause.
– guiverc
Apr 2 at 21:47
Check edited post, it shows I have 34 gigs left in root
– mohkamfer
Apr 13 at 17:47
I said $HOME (/home/user/) which may be on a separate partition, and then (more unlikely) i'd also check inodes you didn't mention.
– guiverc
Apr 13 at 17:54
Well I can't find $HOME in the output.. The only recognizable entries are /dev /run / /dev/shm /run/lock /sys/fs/cgroup /boot/efi /run/user/120 /run/user/1000 rest is a bunch of weird /dev/loop#
– mohkamfer
Apr 13 at 17:57
df -h |grep $HOMEor if you want to see what $HOME represents you couldecho $HOME. To view inodes you use the -i option withdf. Of note if you create problems on your system, they don't show until you next boot it, as for example, if you delete (rm) a needed file that was being used at the time, the file won't be noticed until next reboot or next login, but the current session can still use it as the inode isn't freed until the session ends (thru logout or off/reset)
– guiverc
Apr 13 at 18:06
|
show 2 more comments
I haven't recently updated Ubuntu or anything, it was working perfectly fine, until it suddenly refused to log me into desktop anymore. Whenever I login, it pauses for seconds, then brings the login screen again.
I've seen countless questions/articles/threads on the Internet explaining how to fix this, but sadly nothing has worked for me yet. I've even turned to second Google results page... Do you imagine?
Anyways, the only thing I recognize that could f**k up my machine is installing these two
http://www.ext2fsd.com/
and
https://www.paragon-software.com/home/linuxfs-windows/
installed by that order. Ext2Fsd didn't work for me, so I had to resort to Paragon's solution instead. The login loop problem only appeared after using these programs. I tried opening them, unmounting everything, remounting in read-only in hopes of reverting something that could've f**ked up, to no avail.
Of the many solutions that I found, one command seems to be very weird, which is strace xauth list, it almost always fails, either by telling me there's no .Xauthority file (after deliberately deleting it while following some article's advice), or just spitting walls of text that just look like a logcat.
I also tried doing strace startx, but it always complains that Xauthority could not be read, permission denied, and the whole tty blacks out, that I need to start another tty to continue tinkering.
I don't even know where to start debugging, and how to debug. I hope someone can help me.
NOTE: Someone suggested that the home directory could be encrypted, and to install ecryptfs-utils to fix it, I did so but didn't change a thing.
EDIT: Running df -hl shows that sda6 or / has 6% free, which is 34 GB.
EDIT: I tried installing LightDM instead of GDM3, but it has the same issue of redirecting back to login screen. I guess this eliminates the possibility of DM issues.
EDIT: I tried running sudo prime-select intel, but it didn't solve anything, I believe this means there's no problem with my NVIDIA card? Side note: I use bumblebee.
EDIT: Not really sure if this is needed, but I'd love to document everything. When I reboot the system and go into tty again, entering username automatically inserts another new line, which is directed to the password field, and it complains that the new line is a wrong password. It keeps looping this until it restarts/cleans the tty and asks for username again. The only solution to this is rebooting into the previous linux version, then rebooting into the current one again. But a reboot on the same version will introduce it and the loop goes on.
18.04 gnome xorg gdm xserver
asked Apr 2 at 20:03
mohkamfermohkamfer
43
I haven't recently updated Ubuntu or anything, it was working perfectly fine, until it suddenly refused to log me into desktop anymore. Whenever I login, it pauses for seconds, then brings the login screen again.
I've seen countless questions/articles/threads on the Internet explaining how to fix this, but sadly nothing has worked for me yet. I've even turned to second Google results page... Do you imagine?
Anyways, the only thing I recognize that could f**k up my machine is installing these two
http://www.ext2fsd.com/
and
https://www.paragon-software.com/home/linuxfs-windows/
installed by that order. Ext2Fsd didn't work for me, so I had to resort to Paragon's solution instead. The login loop problem only appeared after using these programs. I tried opening them, unmounting everything, remounting in read-only in hopes of reverting something that could've f**ked up, to no avail.
Of the many solutions that I found, one command seems to be very weird, which is strace xauth list, it almost always fails, either by telling me there's no .Xauthority file (after deliberately deleting it while following some article's advice), or just spitting walls of text that just look like a logcat.
I also tried doing strace startx, but it always complains that Xauthority could not be read, permission denied, and the whole tty blacks out, that I need to start another tty to continue tinkering.
I don't even know where to start debugging, and how to debug. I hope someone can help me.
NOTE: Someone suggested that the home directory could be encrypted, and to install ecryptfs-utils to fix it, I did so but didn't change a thing.
EDIT: Running df -hl shows that sda6 or / has 6% free, which is 34 GB.
EDIT: I tried installing LightDM instead of GDM3, but it has the same issue of redirecting back to login screen. I guess this eliminates the possibility of DM issues.
EDIT: I tried running sudo prime-select intel, but it didn't solve anything, I believe this means there's no problem with my NVIDIA card? Side note: I use bumblebee.
EDIT: Not really sure if this is needed, but I'd love to document everything. When I reboot the system and go into tty again, entering username automatically inserts another new line, which is directed to the password field, and it complains that the new line is a wrong password. It keeps looping this until it restarts/cleans the tty and asks for username again. The only solution to this is rebooting into the previous linux version, then rebooting into the current one again. But a reboot on the same version will introduce it and the loop goes on.
18.04 gnome xorg gdm xserver
18.04 gnome xorg gdm xserver
asked Apr 2 at 20:03
mohkamfermohkamfer
43
asked Apr 2 at 20:03
mohkamfermohkamfer
43
edited Apr 13 at 19:44
mohkamfer
asked Apr 2 at 20:03
mohkamfermohkamfer
43
asked Apr 2 at 20:03
mohkamfermohkamfer
43
asked Apr 2 at 20:03
mohkamfermohkamfer
43
43
You've documented many things that could now complicate things. If you've had no updates, installed nothing new nor changed any hardware but can no longer login - the first thing I check is I have space in $HOME (your user directory). If it's full or very-near-full a GUI login cannot proceed as it can't create temporary work files needed for gui operation, and you return to greeter/login screen. Login using a terminal anddf -hl(disk free - local drives, human output) & check you have space (text logins will work). This changes nothing, but eliminates one (primary) cause.
– guiverc
Apr 2 at 21:47
Check edited post, it shows I have 34 gigs left in root
– mohkamfer
Apr 13 at 17:47
I said $HOME (/home/user/) which may be on a separate partition, and then (more unlikely) i'd also check inodes you didn't mention.
– guiverc
Apr 13 at 17:54
Well I can't find $HOME in the output.. The only recognizable entries are /dev /run / /dev/shm /run/lock /sys/fs/cgroup /boot/efi /run/user/120 /run/user/1000 rest is a bunch of weird /dev/loop#
– mohkamfer
Apr 13 at 17:57
df -h |grep $HOMEor if you want to see what $HOME represents you couldecho $HOME. To view inodes you use the -i option withdf. Of note if you create problems on your system, they don't show until you next boot it, as for example, if you delete (rm) a needed file that was being used at the time, the file won't be noticed until next reboot or next login, but the current session can still use it as the inode isn't freed until the session ends (thru logout or off/reset)
– guiverc
Apr 13 at 18:06
|
show 2 more comments
You've documented many things that could now complicate things. If you've had no updates, installed nothing new nor changed any hardware but can no longer login - the first thing I check is I have space in $HOME (your user directory). If it's full or very-near-full a GUI login cannot proceed as it can't create temporary work files needed for gui operation, and you return to greeter/login screen. Login using a terminal anddf -hl(disk free - local drives, human output) & check you have space (text logins will work). This changes nothing, but eliminates one (primary) cause.
– guiverc
Apr 2 at 21:47
Check edited post, it shows I have 34 gigs left in root
– mohkamfer
Apr 13 at 17:47
I said $HOME (/home/user/) which may be on a separate partition, and then (more unlikely) i'd also check inodes you didn't mention.
– guiverc
Apr 13 at 17:54
Well I can't find $HOME in the output.. The only recognizable entries are /dev /run / /dev/shm /run/lock /sys/fs/cgroup /boot/efi /run/user/120 /run/user/1000 rest is a bunch of weird /dev/loop#
– mohkamfer
Apr 13 at 17:57
df -h |grep $HOMEor if you want to see what $HOME represents you couldecho $HOME. To view inodes you use the -i option withdf. Of note if you create problems on your system, they don't show until you next boot it, as for example, if you delete (rm) a needed file that was being used at the time, the file won't be noticed until next reboot or next login, but the current session can still use it as the inode isn't freed until the session ends (thru logout or off/reset)
– guiverc
Apr 13 at 18:06
You've documented many things that could now complicate things. If you've had no updates, installed nothing new nor changed any hardware but can no longer login - the first thing I check is I have space in $HOME (your user directory). If it's full or very-near-full a GUI login cannot proceed as it can't create temporary work files needed for gui operation, and you return to greeter/login screen. Login using a terminal and
df -hl (disk free - local drives, human output) & check you have space (text logins will work). This changes nothing, but eliminates one (primary) cause.– guiverc
Apr 2 at 21:47
You've documented many things that could now complicate things. If you've had no updates, installed nothing new nor changed any hardware but can no longer login - the first thing I check is I have space in $HOME (your user directory). If it's full or very-near-full a GUI login cannot proceed as it can't create temporary work files needed for gui operation, and you return to greeter/login screen. Login using a terminal and
df -hl (disk free - local drives, human output) & check you have space (text logins will work). This changes nothing, but eliminates one (primary) cause.– guiverc
Apr 2 at 21:47
Check edited post, it shows I have 34 gigs left in root
– mohkamfer
Apr 13 at 17:47
Check edited post, it shows I have 34 gigs left in root
– mohkamfer
Apr 13 at 17:47
I said $HOME (/home/user/) which may be on a separate partition, and then (more unlikely) i'd also check inodes you didn't mention.
– guiverc
Apr 13 at 17:54
I said $HOME (/home/user/) which may be on a separate partition, and then (more unlikely) i'd also check inodes you didn't mention.
– guiverc
Apr 13 at 17:54
Well I can't find $HOME in the output.. The only recognizable entries are /dev /run / /dev/shm /run/lock /sys/fs/cgroup /boot/efi /run/user/120 /run/user/1000 rest is a bunch of weird /dev/loop#
– mohkamfer
Apr 13 at 17:57
Well I can't find $HOME in the output.. The only recognizable entries are /dev /run / /dev/shm /run/lock /sys/fs/cgroup /boot/efi /run/user/120 /run/user/1000 rest is a bunch of weird /dev/loop#
– mohkamfer
Apr 13 at 17:57
df -h |grep $HOME or if you want to see what $HOME represents you could echo $HOME. To view inodes you use the -i option with df. Of note if you create problems on your system, they don't show until you next boot it, as for example, if you delete (rm) a needed file that was being used at the time, the file won't be noticed until next reboot or next login, but the current session can still use it as the inode isn't freed until the session ends (thru logout or off/reset)– guiverc
Apr 13 at 18:06
df -h |grep $HOME or if you want to see what $HOME represents you could echo $HOME. To view inodes you use the -i option with df. Of note if you create problems on your system, they don't show until you next boot it, as for example, if you delete (rm) a needed file that was being used at the time, the file won't be noticed until next reboot or next login, but the current session can still use it as the inode isn't freed until the session ends (thru logout or off/reset)– guiverc
Apr 13 at 18:06
|
show 2 more comments
0
active
oldest
votes
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%2f1130720%2fubuntu-infamous-login-loop%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1130720%2fubuntu-infamous-login-loop%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
You've documented many things that could now complicate things. If you've had no updates, installed nothing new nor changed any hardware but can no longer login - the first thing I check is I have space in $HOME (your user directory). If it's full or very-near-full a GUI login cannot proceed as it can't create temporary work files needed for gui operation, and you return to greeter/login screen. Login using a terminal and
df -hl(disk free - local drives, human output) & check you have space (text logins will work). This changes nothing, but eliminates one (primary) cause.– guiverc
Apr 2 at 21:47
Check edited post, it shows I have 34 gigs left in root
– mohkamfer
Apr 13 at 17:47
I said $HOME (/home/user/) which may be on a separate partition, and then (more unlikely) i'd also check inodes you didn't mention.
– guiverc
Apr 13 at 17:54
Well I can't find $HOME in the output.. The only recognizable entries are /dev /run / /dev/shm /run/lock /sys/fs/cgroup /boot/efi /run/user/120 /run/user/1000 rest is a bunch of weird /dev/loop#
– mohkamfer
Apr 13 at 17:57
df -h |grep $HOMEor if you want to see what $HOME represents you couldecho $HOME. To view inodes you use the -i option withdf. Of note if you create problems on your system, they don't show until you next boot it, as for example, if you delete (rm) a needed file that was being used at the time, the file won't be noticed until next reboot or next login, but the current session can still use it as the inode isn't freed until the session ends (thru logout or off/reset)– guiverc
Apr 13 at 18:06