Ubuntu 18.04 Login window loopUbuntu gets stuck in a login loopHow to disable systemd-resolved in Ubuntu?No login screen after Ubuntu 18.04 updateLogin screen throws back to login screen13.10 login loop workaround creates unwanted root access17.04 update login loopInput devices stop working after logout or switch-user in ubuntu 18.04 LTSServer name resolution messed up when running PiHole in DockerNvidia Persistence Daemon/Login Loop 18.04
Group Delay for Hilbert Transformer and Resulting Dispersion
How to create slices for each selected area of a layer separated by transparency or solid color?
Is there a material or method to allow "swimmable" coins?
Why did they design new connectors for USB?
binomial coefficient equal to sum
Glass bowl safe in pressure cooker?
Film about the USA being run by fake videos of the president after his kidnapping
Turing award papers
Is there any difference between 旅行者 and 旅人?
How do I install this weird looking i9 9900K I bought?
PNGs in distance appear to overlap foreground PNGs when viewed at different angles
Interval variables in MIP
What is the difference between "ещё" and "больше"?
A short novel about reaching absolute zero
What is the difference between scissors and shears?
What type of glass fuse is this and what does the spring do?
how to remove some small rocks at the bottom of a 4' vertical water pipe 2 1/2" diameter?
Can any number of squares be a square?
I bought a pair of tefillin -- help me understand the accompanying certificate?
Bridge rectifier outputting 338 volts DC with 120 volts AC input
What are optical counterparts?
Does the item you apply the Replicate Magic item infusion change its shape to fit the magic item you chose?
What's that in front of the overhead panel?
Is American Express widely accepted in Hong Kong?
Ubuntu 18.04 Login window loop
Ubuntu gets stuck in a login loopHow to disable systemd-resolved in Ubuntu?No login screen after Ubuntu 18.04 updateLogin screen throws back to login screen13.10 login loop workaround creates unwanted root access17.04 update login loopInput devices stop working after logout or switch-user in ubuntu 18.04 LTSServer name resolution messed up when running PiHole in DockerNvidia Persistence Daemon/Login Loop 18.04
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
Is there any reason the login window would stop working and start looping? I'm running 18.04. I normally RDP into the ubuntu box, but that isn't working now. Using a keyboard and mouse, I see my username on the monitor. I type in my password. Then the screen goes blank for a few seconds... and I'm back to the login screen where my username is. I'm not getting through to my desktop!
I haven't messed with the machine except for the following, but, I'm not sure why any of these would impact the loginscreen.
- install pihole in a docker container,
- turn off systemd-resolved (to get port 53 working) per https://www.reddit.com/r/pihole/comments/8zamlk/trying_to_install_pihole_on_ubuntu_and_having/e2hd7qp/
and
How to disable systemd-resolved in Ubuntu?, and - installed gufw to graphically manage the firewall/open port 80 for pihole.
But none of these messed with the login manager. Does anyone have any idea what could be up? Interestingly, nearly all of my docker containers (portainer, heimdall, tatulli, sonarr, radarr, pihole) work, with the exception of anything using ssl (plex and cockpit). I'm guessing somehow the firewall blocked port 443, but I'm not sure why that would stop me from logging into the box using a keyboard and mouse...
Any help/insight is greatly appreciated!
EDIT1: I tried creating another user via
sudo useradd -d /home/testuser testuser
sudo passwd testuser
but the login manager still throws me for a loop
EDIT2: I've disabled the firewall via
sudo ufw disable
and I reversed the system-resolved.service work, but still no luck :(
18.04 login login-screen firewall gdm
add a comment
|
Is there any reason the login window would stop working and start looping? I'm running 18.04. I normally RDP into the ubuntu box, but that isn't working now. Using a keyboard and mouse, I see my username on the monitor. I type in my password. Then the screen goes blank for a few seconds... and I'm back to the login screen where my username is. I'm not getting through to my desktop!
I haven't messed with the machine except for the following, but, I'm not sure why any of these would impact the loginscreen.
- install pihole in a docker container,
- turn off systemd-resolved (to get port 53 working) per https://www.reddit.com/r/pihole/comments/8zamlk/trying_to_install_pihole_on_ubuntu_and_having/e2hd7qp/
and
How to disable systemd-resolved in Ubuntu?, and - installed gufw to graphically manage the firewall/open port 80 for pihole.
But none of these messed with the login manager. Does anyone have any idea what could be up? Interestingly, nearly all of my docker containers (portainer, heimdall, tatulli, sonarr, radarr, pihole) work, with the exception of anything using ssl (plex and cockpit). I'm guessing somehow the firewall blocked port 443, but I'm not sure why that would stop me from logging into the box using a keyboard and mouse...
Any help/insight is greatly appreciated!
EDIT1: I tried creating another user via
sudo useradd -d /home/testuser testuser
sudo passwd testuser
but the login manager still throws me for a loop
EDIT2: I've disabled the firewall via
sudo ufw disable
and I reversed the system-resolved.service work, but still no luck :(
18.04 login login-screen firewall gdm
Possible duplicate of Ubuntu gets stuck in a login loop
– karel
Oct 2 at 12:14
add a comment
|
Is there any reason the login window would stop working and start looping? I'm running 18.04. I normally RDP into the ubuntu box, but that isn't working now. Using a keyboard and mouse, I see my username on the monitor. I type in my password. Then the screen goes blank for a few seconds... and I'm back to the login screen where my username is. I'm not getting through to my desktop!
I haven't messed with the machine except for the following, but, I'm not sure why any of these would impact the loginscreen.
- install pihole in a docker container,
- turn off systemd-resolved (to get port 53 working) per https://www.reddit.com/r/pihole/comments/8zamlk/trying_to_install_pihole_on_ubuntu_and_having/e2hd7qp/
and
How to disable systemd-resolved in Ubuntu?, and - installed gufw to graphically manage the firewall/open port 80 for pihole.
But none of these messed with the login manager. Does anyone have any idea what could be up? Interestingly, nearly all of my docker containers (portainer, heimdall, tatulli, sonarr, radarr, pihole) work, with the exception of anything using ssl (plex and cockpit). I'm guessing somehow the firewall blocked port 443, but I'm not sure why that would stop me from logging into the box using a keyboard and mouse...
Any help/insight is greatly appreciated!
EDIT1: I tried creating another user via
sudo useradd -d /home/testuser testuser
sudo passwd testuser
but the login manager still throws me for a loop
EDIT2: I've disabled the firewall via
sudo ufw disable
and I reversed the system-resolved.service work, but still no luck :(
18.04 login login-screen firewall gdm
Is there any reason the login window would stop working and start looping? I'm running 18.04. I normally RDP into the ubuntu box, but that isn't working now. Using a keyboard and mouse, I see my username on the monitor. I type in my password. Then the screen goes blank for a few seconds... and I'm back to the login screen where my username is. I'm not getting through to my desktop!
I haven't messed with the machine except for the following, but, I'm not sure why any of these would impact the loginscreen.
- install pihole in a docker container,
- turn off systemd-resolved (to get port 53 working) per https://www.reddit.com/r/pihole/comments/8zamlk/trying_to_install_pihole_on_ubuntu_and_having/e2hd7qp/
and
How to disable systemd-resolved in Ubuntu?, and - installed gufw to graphically manage the firewall/open port 80 for pihole.
But none of these messed with the login manager. Does anyone have any idea what could be up? Interestingly, nearly all of my docker containers (portainer, heimdall, tatulli, sonarr, radarr, pihole) work, with the exception of anything using ssl (plex and cockpit). I'm guessing somehow the firewall blocked port 443, but I'm not sure why that would stop me from logging into the box using a keyboard and mouse...
Any help/insight is greatly appreciated!
EDIT1: I tried creating another user via
sudo useradd -d /home/testuser testuser
sudo passwd testuser
but the login manager still throws me for a loop
EDIT2: I've disabled the firewall via
sudo ufw disable
and I reversed the system-resolved.service work, but still no luck :(
18.04 login login-screen firewall gdm
18.04 login login-screen firewall gdm
edited Oct 23 '18 at 12:19
abu_bua
5,3708 gold badges20 silver badges41 bronze badges
5,3708 gold badges20 silver badges41 bronze badges
asked Oct 23 '18 at 10:59
EmmitEmmit
711 gold badge1 silver badge5 bronze badges
711 gold badge1 silver badge5 bronze badges
Possible duplicate of Ubuntu gets stuck in a login loop
– karel
Oct 2 at 12:14
add a comment
|
Possible duplicate of Ubuntu gets stuck in a login loop
– karel
Oct 2 at 12:14
Possible duplicate of Ubuntu gets stuck in a login loop
– karel
Oct 2 at 12:14
Possible duplicate of Ubuntu gets stuck in a login loop
– karel
Oct 2 at 12:14
add a comment
|
9 Answers
9
active
oldest
votes
I've almost done all suggestions here, but none of them didn't work.
Also gd3 reconfigure has no effect.
But I had suspected to my last gnome extensions.
The system-monitor@paradoxxx.zero.gmail.com
was the problem.
So I disabled all gnome extensions to solve login loop as following steps:
- Press Ctrl+Alt+F2 or Ctrl+Alt+F3 or ...
- Enter your username and password
cd ~/.local/share/gnome-shell/
mv extensions extensions.bak
mkdir extensions
- Press Ctrl+Alt+F1
- Login and Thanks God
Hope help somebody else. I almost worked full day to find this solution.
PS: I've installed my favorite extentions again and I have to tell you Login Loop disaster in ubuntu has wide variety causes. So try to find your special cause and solve it.
This worked for me. I had an out-of-date extension (workspace-grid@mathematical.coffee.gmail.com). Copying all extensions, then adding them back one-by-one (I only had two, so it was easy) allowed me to identify this as the culprit. Thank you!
– Kryten
Jan 22 at 23:12
After two days of frantic googling re "18.04 login loop after software update" and trying all standard recipes to no avail I found your above extensions suggestion. Saved me! For me also the workspace grid. Thank YOU!
– Rob Rutten
Feb 1 at 16:04
@RobRutten , @ Kryten Happy it helped you. Thanks God :))
– Khalil Laleh
Feb 2 at 8:40
I had to reinstall my GPU drivers and waist hours just to come across with the post. - I love you
– DsCpp
Apr 10 at 15:21
add a comment
|
Looks like it may have been related to "upgrading" from 18.04 to 18.04.01: No login screen after ubuntu 18.04.1 update
In any case, doing the following fixed it for me:
systemctl stop gdm.service
systemctl restart gdm.service
sudo dpkg-reconfigure gdm3
reboot
add a comment
|
I also had tried a lot of solution but none of that work for me, but this did.
- Press Ctrl+Alt+F2
- Login with your username and password
- Enter
ls -ld ~/
after you will see something like thisdrwxr-xr-x 30 root root 4096 Jul 6 20:26 /home/yourcutename/
- Now Enter
sudo chown username:username /home/yourcutename/
This worked for me :-)
You'll go to heaven for this. Before almost deciding to reinstall Ubuntu I tried this and it worked. Thanks mate.
– Amit Yadav
Aug 25 at 11:17
add a comment
|
My ubuntu loop login problem started after switching from java11 openjdk to java8 openjdk.
I had logged in via CTRL+ALT+F3 to terminal and switched back to java 11 viasudo update-alternatives --config java
and login loop stopped.
add a comment
|
i have that same problem on Ubuntu 19.04. What i did was reinstall gnome and works fines.
sudo apt-get install gnome-session gnome
Then on the log in screen i change to gnome
add a comment
|
My issue started after I messed with the /etc/environment
file by adding the following to my path variable:
PATH=$JAVA_HOME:$PATH
I fixed the issue by going into one of the strips down mode in grep, launching a command prompt, launching VI and removing the above.
I believe what happens, is by messing with the path variable, Ubuntu couldn't find some things.
I initially did this because I installed java manually.
** by strip down mode, I mean recovery mode
– AndreGraveler
Jun 13 at 0:45
It seems if you change the path variable manually it throws off things. Its best to do auto install.
– AndreGraveler
Jun 13 at 0:48
add a comment
|
I faced the same problem with my Ubuntu 18.04 a couple of days ago. I tried all the mentioned solutions on the web. But I think, in the end, the problem with mine was some wonky graphics drivers. All I did was log in on my system on Ubuntu Wayland (by clicking that gear button at the time of login) opened the Terminal Window and upgraded. The commands were:
sudo apt update
sudo apt upgrade
And then rebooted my system. Ready as new!!!
If you want you can stay and use it on Wayland, but some applications do not work properly on Wayland (like VLC).
Well, the other solutions on the web did not work for me. So, all the others and even if this solution does not work then I think only one option is left: Reinstall
add a comment
|
The cause for me was that I was playing around with the DISPLAY variable
and had set export DISPLAY=:1.0
in my .profile
when I commented out that line, I could log in again ie. no more looping.
add a comment
|
This issue seems to have a different solution for everyone. I tried many different solutions that I found throughout forums and nothing worked for me. After looking around I found the issue was that somehow my user had lost write permissions in my own $HOME folder.... Solution for me was:
- Load command line (ALT+CTRL+F2 or ALT+CTRL+F3)
chmod 755 $HOME
- restart the Desktop Environment.
Hope this can help someone else.
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/4.0/"u003ecc by-sa 4.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%2f1086367%2fubuntu-18-04-login-window-loop%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
9 Answers
9
active
oldest
votes
9 Answers
9
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've almost done all suggestions here, but none of them didn't work.
Also gd3 reconfigure has no effect.
But I had suspected to my last gnome extensions.
The system-monitor@paradoxxx.zero.gmail.com
was the problem.
So I disabled all gnome extensions to solve login loop as following steps:
- Press Ctrl+Alt+F2 or Ctrl+Alt+F3 or ...
- Enter your username and password
cd ~/.local/share/gnome-shell/
mv extensions extensions.bak
mkdir extensions
- Press Ctrl+Alt+F1
- Login and Thanks God
Hope help somebody else. I almost worked full day to find this solution.
PS: I've installed my favorite extentions again and I have to tell you Login Loop disaster in ubuntu has wide variety causes. So try to find your special cause and solve it.
This worked for me. I had an out-of-date extension (workspace-grid@mathematical.coffee.gmail.com). Copying all extensions, then adding them back one-by-one (I only had two, so it was easy) allowed me to identify this as the culprit. Thank you!
– Kryten
Jan 22 at 23:12
After two days of frantic googling re "18.04 login loop after software update" and trying all standard recipes to no avail I found your above extensions suggestion. Saved me! For me also the workspace grid. Thank YOU!
– Rob Rutten
Feb 1 at 16:04
@RobRutten , @ Kryten Happy it helped you. Thanks God :))
– Khalil Laleh
Feb 2 at 8:40
I had to reinstall my GPU drivers and waist hours just to come across with the post. - I love you
– DsCpp
Apr 10 at 15:21
add a comment
|
I've almost done all suggestions here, but none of them didn't work.
Also gd3 reconfigure has no effect.
But I had suspected to my last gnome extensions.
The system-monitor@paradoxxx.zero.gmail.com
was the problem.
So I disabled all gnome extensions to solve login loop as following steps:
- Press Ctrl+Alt+F2 or Ctrl+Alt+F3 or ...
- Enter your username and password
cd ~/.local/share/gnome-shell/
mv extensions extensions.bak
mkdir extensions
- Press Ctrl+Alt+F1
- Login and Thanks God
Hope help somebody else. I almost worked full day to find this solution.
PS: I've installed my favorite extentions again and I have to tell you Login Loop disaster in ubuntu has wide variety causes. So try to find your special cause and solve it.
This worked for me. I had an out-of-date extension (workspace-grid@mathematical.coffee.gmail.com). Copying all extensions, then adding them back one-by-one (I only had two, so it was easy) allowed me to identify this as the culprit. Thank you!
– Kryten
Jan 22 at 23:12
After two days of frantic googling re "18.04 login loop after software update" and trying all standard recipes to no avail I found your above extensions suggestion. Saved me! For me also the workspace grid. Thank YOU!
– Rob Rutten
Feb 1 at 16:04
@RobRutten , @ Kryten Happy it helped you. Thanks God :))
– Khalil Laleh
Feb 2 at 8:40
I had to reinstall my GPU drivers and waist hours just to come across with the post. - I love you
– DsCpp
Apr 10 at 15:21
add a comment
|
I've almost done all suggestions here, but none of them didn't work.
Also gd3 reconfigure has no effect.
But I had suspected to my last gnome extensions.
The system-monitor@paradoxxx.zero.gmail.com
was the problem.
So I disabled all gnome extensions to solve login loop as following steps:
- Press Ctrl+Alt+F2 or Ctrl+Alt+F3 or ...
- Enter your username and password
cd ~/.local/share/gnome-shell/
mv extensions extensions.bak
mkdir extensions
- Press Ctrl+Alt+F1
- Login and Thanks God
Hope help somebody else. I almost worked full day to find this solution.
PS: I've installed my favorite extentions again and I have to tell you Login Loop disaster in ubuntu has wide variety causes. So try to find your special cause and solve it.
I've almost done all suggestions here, but none of them didn't work.
Also gd3 reconfigure has no effect.
But I had suspected to my last gnome extensions.
The system-monitor@paradoxxx.zero.gmail.com
was the problem.
So I disabled all gnome extensions to solve login loop as following steps:
- Press Ctrl+Alt+F2 or Ctrl+Alt+F3 or ...
- Enter your username and password
cd ~/.local/share/gnome-shell/
mv extensions extensions.bak
mkdir extensions
- Press Ctrl+Alt+F1
- Login and Thanks God
Hope help somebody else. I almost worked full day to find this solution.
PS: I've installed my favorite extentions again and I have to tell you Login Loop disaster in ubuntu has wide variety causes. So try to find your special cause and solve it.
edited Feb 12 at 23:03
mature
3,0785 gold badges14 silver badges42 bronze badges
3,0785 gold badges14 silver badges42 bronze badges
answered Jan 20 at 14:23
Khalil LalehKhalil Laleh
1811 silver badge9 bronze badges
1811 silver badge9 bronze badges
This worked for me. I had an out-of-date extension (workspace-grid@mathematical.coffee.gmail.com). Copying all extensions, then adding them back one-by-one (I only had two, so it was easy) allowed me to identify this as the culprit. Thank you!
– Kryten
Jan 22 at 23:12
After two days of frantic googling re "18.04 login loop after software update" and trying all standard recipes to no avail I found your above extensions suggestion. Saved me! For me also the workspace grid. Thank YOU!
– Rob Rutten
Feb 1 at 16:04
@RobRutten , @ Kryten Happy it helped you. Thanks God :))
– Khalil Laleh
Feb 2 at 8:40
I had to reinstall my GPU drivers and waist hours just to come across with the post. - I love you
– DsCpp
Apr 10 at 15:21
add a comment
|
This worked for me. I had an out-of-date extension (workspace-grid@mathematical.coffee.gmail.com). Copying all extensions, then adding them back one-by-one (I only had two, so it was easy) allowed me to identify this as the culprit. Thank you!
– Kryten
Jan 22 at 23:12
After two days of frantic googling re "18.04 login loop after software update" and trying all standard recipes to no avail I found your above extensions suggestion. Saved me! For me also the workspace grid. Thank YOU!
– Rob Rutten
Feb 1 at 16:04
@RobRutten , @ Kryten Happy it helped you. Thanks God :))
– Khalil Laleh
Feb 2 at 8:40
I had to reinstall my GPU drivers and waist hours just to come across with the post. - I love you
– DsCpp
Apr 10 at 15:21
This worked for me. I had an out-of-date extension (workspace-grid@mathematical.coffee.gmail.com). Copying all extensions, then adding them back one-by-one (I only had two, so it was easy) allowed me to identify this as the culprit. Thank you!
– Kryten
Jan 22 at 23:12
This worked for me. I had an out-of-date extension (workspace-grid@mathematical.coffee.gmail.com). Copying all extensions, then adding them back one-by-one (I only had two, so it was easy) allowed me to identify this as the culprit. Thank you!
– Kryten
Jan 22 at 23:12
After two days of frantic googling re "18.04 login loop after software update" and trying all standard recipes to no avail I found your above extensions suggestion. Saved me! For me also the workspace grid. Thank YOU!
– Rob Rutten
Feb 1 at 16:04
After two days of frantic googling re "18.04 login loop after software update" and trying all standard recipes to no avail I found your above extensions suggestion. Saved me! For me also the workspace grid. Thank YOU!
– Rob Rutten
Feb 1 at 16:04
@RobRutten , @ Kryten Happy it helped you. Thanks God :))
– Khalil Laleh
Feb 2 at 8:40
@RobRutten , @ Kryten Happy it helped you. Thanks God :))
– Khalil Laleh
Feb 2 at 8:40
I had to reinstall my GPU drivers and waist hours just to come across with the post. - I love you
– DsCpp
Apr 10 at 15:21
I had to reinstall my GPU drivers and waist hours just to come across with the post. - I love you
– DsCpp
Apr 10 at 15:21
add a comment
|
Looks like it may have been related to "upgrading" from 18.04 to 18.04.01: No login screen after ubuntu 18.04.1 update
In any case, doing the following fixed it for me:
systemctl stop gdm.service
systemctl restart gdm.service
sudo dpkg-reconfigure gdm3
reboot
add a comment
|
Looks like it may have been related to "upgrading" from 18.04 to 18.04.01: No login screen after ubuntu 18.04.1 update
In any case, doing the following fixed it for me:
systemctl stop gdm.service
systemctl restart gdm.service
sudo dpkg-reconfigure gdm3
reboot
add a comment
|
Looks like it may have been related to "upgrading" from 18.04 to 18.04.01: No login screen after ubuntu 18.04.1 update
In any case, doing the following fixed it for me:
systemctl stop gdm.service
systemctl restart gdm.service
sudo dpkg-reconfigure gdm3
reboot
Looks like it may have been related to "upgrading" from 18.04 to 18.04.01: No login screen after ubuntu 18.04.1 update
In any case, doing the following fixed it for me:
systemctl stop gdm.service
systemctl restart gdm.service
sudo dpkg-reconfigure gdm3
reboot
edited Jan 20 at 14:31
Kulfy
9,26711 gold badges36 silver badges61 bronze badges
9,26711 gold badges36 silver badges61 bronze badges
answered Oct 23 '18 at 12:09
EmmitEmmit
711 gold badge1 silver badge5 bronze badges
711 gold badge1 silver badge5 bronze badges
add a comment
|
add a comment
|
I also had tried a lot of solution but none of that work for me, but this did.
- Press Ctrl+Alt+F2
- Login with your username and password
- Enter
ls -ld ~/
after you will see something like thisdrwxr-xr-x 30 root root 4096 Jul 6 20:26 /home/yourcutename/
- Now Enter
sudo chown username:username /home/yourcutename/
This worked for me :-)
You'll go to heaven for this. Before almost deciding to reinstall Ubuntu I tried this and it worked. Thanks mate.
– Amit Yadav
Aug 25 at 11:17
add a comment
|
I also had tried a lot of solution but none of that work for me, but this did.
- Press Ctrl+Alt+F2
- Login with your username and password
- Enter
ls -ld ~/
after you will see something like thisdrwxr-xr-x 30 root root 4096 Jul 6 20:26 /home/yourcutename/
- Now Enter
sudo chown username:username /home/yourcutename/
This worked for me :-)
You'll go to heaven for this. Before almost deciding to reinstall Ubuntu I tried this and it worked. Thanks mate.
– Amit Yadav
Aug 25 at 11:17
add a comment
|
I also had tried a lot of solution but none of that work for me, but this did.
- Press Ctrl+Alt+F2
- Login with your username and password
- Enter
ls -ld ~/
after you will see something like thisdrwxr-xr-x 30 root root 4096 Jul 6 20:26 /home/yourcutename/
- Now Enter
sudo chown username:username /home/yourcutename/
This worked for me :-)
I also had tried a lot of solution but none of that work for me, but this did.
- Press Ctrl+Alt+F2
- Login with your username and password
- Enter
ls -ld ~/
after you will see something like thisdrwxr-xr-x 30 root root 4096 Jul 6 20:26 /home/yourcutename/
- Now Enter
sudo chown username:username /home/yourcutename/
This worked for me :-)
edited Jul 6 at 15:27
Kulfy
9,26711 gold badges36 silver badges61 bronze badges
9,26711 gold badges36 silver badges61 bronze badges
answered Jul 6 at 15:07
Mr BumblebeeMr Bumblebee
1314 bronze badges
1314 bronze badges
You'll go to heaven for this. Before almost deciding to reinstall Ubuntu I tried this and it worked. Thanks mate.
– Amit Yadav
Aug 25 at 11:17
add a comment
|
You'll go to heaven for this. Before almost deciding to reinstall Ubuntu I tried this and it worked. Thanks mate.
– Amit Yadav
Aug 25 at 11:17
You'll go to heaven for this. Before almost deciding to reinstall Ubuntu I tried this and it worked. Thanks mate.
– Amit Yadav
Aug 25 at 11:17
You'll go to heaven for this. Before almost deciding to reinstall Ubuntu I tried this and it worked. Thanks mate.
– Amit Yadav
Aug 25 at 11:17
add a comment
|
My ubuntu loop login problem started after switching from java11 openjdk to java8 openjdk.
I had logged in via CTRL+ALT+F3 to terminal and switched back to java 11 viasudo update-alternatives --config java
and login loop stopped.
add a comment
|
My ubuntu loop login problem started after switching from java11 openjdk to java8 openjdk.
I had logged in via CTRL+ALT+F3 to terminal and switched back to java 11 viasudo update-alternatives --config java
and login loop stopped.
add a comment
|
My ubuntu loop login problem started after switching from java11 openjdk to java8 openjdk.
I had logged in via CTRL+ALT+F3 to terminal and switched back to java 11 viasudo update-alternatives --config java
and login loop stopped.
My ubuntu loop login problem started after switching from java11 openjdk to java8 openjdk.
I had logged in via CTRL+ALT+F3 to terminal and switched back to java 11 viasudo update-alternatives --config java
and login loop stopped.
answered Sep 28 at 19:20
AhmetAhmet
111 bronze badge
111 bronze badge
add a comment
|
add a comment
|
i have that same problem on Ubuntu 19.04. What i did was reinstall gnome and works fines.
sudo apt-get install gnome-session gnome
Then on the log in screen i change to gnome
add a comment
|
i have that same problem on Ubuntu 19.04. What i did was reinstall gnome and works fines.
sudo apt-get install gnome-session gnome
Then on the log in screen i change to gnome
add a comment
|
i have that same problem on Ubuntu 19.04. What i did was reinstall gnome and works fines.
sudo apt-get install gnome-session gnome
Then on the log in screen i change to gnome
i have that same problem on Ubuntu 19.04. What i did was reinstall gnome and works fines.
sudo apt-get install gnome-session gnome
Then on the log in screen i change to gnome
answered Apr 25 at 22:17
RanosiRanosi
1
1
add a comment
|
add a comment
|
My issue started after I messed with the /etc/environment
file by adding the following to my path variable:
PATH=$JAVA_HOME:$PATH
I fixed the issue by going into one of the strips down mode in grep, launching a command prompt, launching VI and removing the above.
I believe what happens, is by messing with the path variable, Ubuntu couldn't find some things.
I initially did this because I installed java manually.
** by strip down mode, I mean recovery mode
– AndreGraveler
Jun 13 at 0:45
It seems if you change the path variable manually it throws off things. Its best to do auto install.
– AndreGraveler
Jun 13 at 0:48
add a comment
|
My issue started after I messed with the /etc/environment
file by adding the following to my path variable:
PATH=$JAVA_HOME:$PATH
I fixed the issue by going into one of the strips down mode in grep, launching a command prompt, launching VI and removing the above.
I believe what happens, is by messing with the path variable, Ubuntu couldn't find some things.
I initially did this because I installed java manually.
** by strip down mode, I mean recovery mode
– AndreGraveler
Jun 13 at 0:45
It seems if you change the path variable manually it throws off things. Its best to do auto install.
– AndreGraveler
Jun 13 at 0:48
add a comment
|
My issue started after I messed with the /etc/environment
file by adding the following to my path variable:
PATH=$JAVA_HOME:$PATH
I fixed the issue by going into one of the strips down mode in grep, launching a command prompt, launching VI and removing the above.
I believe what happens, is by messing with the path variable, Ubuntu couldn't find some things.
I initially did this because I installed java manually.
My issue started after I messed with the /etc/environment
file by adding the following to my path variable:
PATH=$JAVA_HOME:$PATH
I fixed the issue by going into one of the strips down mode in grep, launching a command prompt, launching VI and removing the above.
I believe what happens, is by messing with the path variable, Ubuntu couldn't find some things.
I initially did this because I installed java manually.
edited Jun 13 at 4:35
Kulfy
9,26711 gold badges36 silver badges61 bronze badges
9,26711 gold badges36 silver badges61 bronze badges
answered Jun 13 at 0:39
AndreGravelerAndreGraveler
11 bronze badge
11 bronze badge
** by strip down mode, I mean recovery mode
– AndreGraveler
Jun 13 at 0:45
It seems if you change the path variable manually it throws off things. Its best to do auto install.
– AndreGraveler
Jun 13 at 0:48
add a comment
|
** by strip down mode, I mean recovery mode
– AndreGraveler
Jun 13 at 0:45
It seems if you change the path variable manually it throws off things. Its best to do auto install.
– AndreGraveler
Jun 13 at 0:48
** by strip down mode, I mean recovery mode
– AndreGraveler
Jun 13 at 0:45
** by strip down mode, I mean recovery mode
– AndreGraveler
Jun 13 at 0:45
It seems if you change the path variable manually it throws off things. Its best to do auto install.
– AndreGraveler
Jun 13 at 0:48
It seems if you change the path variable manually it throws off things. Its best to do auto install.
– AndreGraveler
Jun 13 at 0:48
add a comment
|
I faced the same problem with my Ubuntu 18.04 a couple of days ago. I tried all the mentioned solutions on the web. But I think, in the end, the problem with mine was some wonky graphics drivers. All I did was log in on my system on Ubuntu Wayland (by clicking that gear button at the time of login) opened the Terminal Window and upgraded. The commands were:
sudo apt update
sudo apt upgrade
And then rebooted my system. Ready as new!!!
If you want you can stay and use it on Wayland, but some applications do not work properly on Wayland (like VLC).
Well, the other solutions on the web did not work for me. So, all the others and even if this solution does not work then I think only one option is left: Reinstall
add a comment
|
I faced the same problem with my Ubuntu 18.04 a couple of days ago. I tried all the mentioned solutions on the web. But I think, in the end, the problem with mine was some wonky graphics drivers. All I did was log in on my system on Ubuntu Wayland (by clicking that gear button at the time of login) opened the Terminal Window and upgraded. The commands were:
sudo apt update
sudo apt upgrade
And then rebooted my system. Ready as new!!!
If you want you can stay and use it on Wayland, but some applications do not work properly on Wayland (like VLC).
Well, the other solutions on the web did not work for me. So, all the others and even if this solution does not work then I think only one option is left: Reinstall
add a comment
|
I faced the same problem with my Ubuntu 18.04 a couple of days ago. I tried all the mentioned solutions on the web. But I think, in the end, the problem with mine was some wonky graphics drivers. All I did was log in on my system on Ubuntu Wayland (by clicking that gear button at the time of login) opened the Terminal Window and upgraded. The commands were:
sudo apt update
sudo apt upgrade
And then rebooted my system. Ready as new!!!
If you want you can stay and use it on Wayland, but some applications do not work properly on Wayland (like VLC).
Well, the other solutions on the web did not work for me. So, all the others and even if this solution does not work then I think only one option is left: Reinstall
I faced the same problem with my Ubuntu 18.04 a couple of days ago. I tried all the mentioned solutions on the web. But I think, in the end, the problem with mine was some wonky graphics drivers. All I did was log in on my system on Ubuntu Wayland (by clicking that gear button at the time of login) opened the Terminal Window and upgraded. The commands were:
sudo apt update
sudo apt upgrade
And then rebooted my system. Ready as new!!!
If you want you can stay and use it on Wayland, but some applications do not work properly on Wayland (like VLC).
Well, the other solutions on the web did not work for me. So, all the others and even if this solution does not work then I think only one option is left: Reinstall
answered Oct 2 at 11:56
n_195n_195
11 bronze badge
11 bronze badge
add a comment
|
add a comment
|
The cause for me was that I was playing around with the DISPLAY variable
and had set export DISPLAY=:1.0
in my .profile
when I commented out that line, I could log in again ie. no more looping.
add a comment
|
The cause for me was that I was playing around with the DISPLAY variable
and had set export DISPLAY=:1.0
in my .profile
when I commented out that line, I could log in again ie. no more looping.
add a comment
|
The cause for me was that I was playing around with the DISPLAY variable
and had set export DISPLAY=:1.0
in my .profile
when I commented out that line, I could log in again ie. no more looping.
The cause for me was that I was playing around with the DISPLAY variable
and had set export DISPLAY=:1.0
in my .profile
when I commented out that line, I could log in again ie. no more looping.
answered Nov 23 at 5:26
chaichai
311 silver badge5 bronze badges
311 silver badge5 bronze badges
add a comment
|
add a comment
|
This issue seems to have a different solution for everyone. I tried many different solutions that I found throughout forums and nothing worked for me. After looking around I found the issue was that somehow my user had lost write permissions in my own $HOME folder.... Solution for me was:
- Load command line (ALT+CTRL+F2 or ALT+CTRL+F3)
chmod 755 $HOME
- restart the Desktop Environment.
Hope this can help someone else.
add a comment
|
This issue seems to have a different solution for everyone. I tried many different solutions that I found throughout forums and nothing worked for me. After looking around I found the issue was that somehow my user had lost write permissions in my own $HOME folder.... Solution for me was:
- Load command line (ALT+CTRL+F2 or ALT+CTRL+F3)
chmod 755 $HOME
- restart the Desktop Environment.
Hope this can help someone else.
add a comment
|
This issue seems to have a different solution for everyone. I tried many different solutions that I found throughout forums and nothing worked for me. After looking around I found the issue was that somehow my user had lost write permissions in my own $HOME folder.... Solution for me was:
- Load command line (ALT+CTRL+F2 or ALT+CTRL+F3)
chmod 755 $HOME
- restart the Desktop Environment.
Hope this can help someone else.
This issue seems to have a different solution for everyone. I tried many different solutions that I found throughout forums and nothing worked for me. After looking around I found the issue was that somehow my user had lost write permissions in my own $HOME folder.... Solution for me was:
- Load command line (ALT+CTRL+F2 or ALT+CTRL+F3)
chmod 755 $HOME
- restart the Desktop Environment.
Hope this can help someone else.
edited Nov 27 at 14:40
Marc Vanhoomissen
1,0342 gold badges12 silver badges22 bronze badges
1,0342 gold badges12 silver badges22 bronze badges
answered Nov 27 at 11:03
NRWNRW
11 bronze badge
11 bronze badge
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%2f1086367%2fubuntu-18-04-login-window-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
Possible duplicate of Ubuntu gets stuck in a login loop
– karel
Oct 2 at 12:14