18.04 Stuck in login loop, startx fails












0















Per other threads I've verified that .Xauthority and .ICEauthoriy belong to my user, that I have free space on disk, and that /tmp is permissioned correctly



ls -lA
-rw------- 1 eights eights 51 Feb 8 12:31 .Xauthority


drwxrwxrwt  13 root root    602112 Feb  8 12:38 tmp


I looked at .xsession-errors it's just a bunch of setting lines



dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/eights/.Xauthority
...


I can login via SSH and TTY2, I've tried purging all nvidia packages and rebooting (login fails) then re-installing nvidia-384 and rebooting (login still fails).



I looked at Xorg.1.log and didn't see anything interesting (no EE, no WW)



https://pastebin.com/rwapVqqT



sudo startx fails but without useful information



X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-138-generic x86_64 Ubuntu
Current Operating System: Linux eights 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=93d06854-e049-4ccd-b9de-bdb2fe89b6ae ro acpi_enforce_resources=lax quiet splash vt.handoff=1
Build Date: 25 October 2018 04:11:27PM
xorg-server 2:1.19.6-1ubuntu4.2 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Fri Feb 8 12:44:48 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.


I've tried installing lightdm (and toggling desktop environment between ubuntu and ubuntu with wayland) both don't work. With gdm3 unity works (but I want what I had before). I tried purging and installing ubuntu-desktop but that doesn't fix it either :(










share|improve this question




















  • 1





    This isn't a forum! Please do not post a solution in the question itself (or add "solved"). Please remove the edit and post it as an answer that you can later accept and receive points for it.

    – GabrielaGarcia
    Feb 9 at 2:38
















0















Per other threads I've verified that .Xauthority and .ICEauthoriy belong to my user, that I have free space on disk, and that /tmp is permissioned correctly



ls -lA
-rw------- 1 eights eights 51 Feb 8 12:31 .Xauthority


drwxrwxrwt  13 root root    602112 Feb  8 12:38 tmp


I looked at .xsession-errors it's just a bunch of setting lines



dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/eights/.Xauthority
...


I can login via SSH and TTY2, I've tried purging all nvidia packages and rebooting (login fails) then re-installing nvidia-384 and rebooting (login still fails).



I looked at Xorg.1.log and didn't see anything interesting (no EE, no WW)



https://pastebin.com/rwapVqqT



sudo startx fails but without useful information



X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-138-generic x86_64 Ubuntu
Current Operating System: Linux eights 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=93d06854-e049-4ccd-b9de-bdb2fe89b6ae ro acpi_enforce_resources=lax quiet splash vt.handoff=1
Build Date: 25 October 2018 04:11:27PM
xorg-server 2:1.19.6-1ubuntu4.2 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Fri Feb 8 12:44:48 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.


I've tried installing lightdm (and toggling desktop environment between ubuntu and ubuntu with wayland) both don't work. With gdm3 unity works (but I want what I had before). I tried purging and installing ubuntu-desktop but that doesn't fix it either :(










share|improve this question




















  • 1





    This isn't a forum! Please do not post a solution in the question itself (or add "solved"). Please remove the edit and post it as an answer that you can later accept and receive points for it.

    – GabrielaGarcia
    Feb 9 at 2:38














0












0








0








Per other threads I've verified that .Xauthority and .ICEauthoriy belong to my user, that I have free space on disk, and that /tmp is permissioned correctly



ls -lA
-rw------- 1 eights eights 51 Feb 8 12:31 .Xauthority


drwxrwxrwt  13 root root    602112 Feb  8 12:38 tmp


I looked at .xsession-errors it's just a bunch of setting lines



dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/eights/.Xauthority
...


I can login via SSH and TTY2, I've tried purging all nvidia packages and rebooting (login fails) then re-installing nvidia-384 and rebooting (login still fails).



I looked at Xorg.1.log and didn't see anything interesting (no EE, no WW)



https://pastebin.com/rwapVqqT



sudo startx fails but without useful information



X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-138-generic x86_64 Ubuntu
Current Operating System: Linux eights 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=93d06854-e049-4ccd-b9de-bdb2fe89b6ae ro acpi_enforce_resources=lax quiet splash vt.handoff=1
Build Date: 25 October 2018 04:11:27PM
xorg-server 2:1.19.6-1ubuntu4.2 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Fri Feb 8 12:44:48 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.


I've tried installing lightdm (and toggling desktop environment between ubuntu and ubuntu with wayland) both don't work. With gdm3 unity works (but I want what I had before). I tried purging and installing ubuntu-desktop but that doesn't fix it either :(










share|improve this question
















Per other threads I've verified that .Xauthority and .ICEauthoriy belong to my user, that I have free space on disk, and that /tmp is permissioned correctly



ls -lA
-rw------- 1 eights eights 51 Feb 8 12:31 .Xauthority


drwxrwxrwt  13 root root    602112 Feb  8 12:38 tmp


I looked at .xsession-errors it's just a bunch of setting lines



dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/eights/.Xauthority
...


I can login via SSH and TTY2, I've tried purging all nvidia packages and rebooting (login fails) then re-installing nvidia-384 and rebooting (login still fails).



I looked at Xorg.1.log and didn't see anything interesting (no EE, no WW)



https://pastebin.com/rwapVqqT



sudo startx fails but without useful information



X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-138-generic x86_64 Ubuntu
Current Operating System: Linux eights 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=93d06854-e049-4ccd-b9de-bdb2fe89b6ae ro acpi_enforce_resources=lax quiet splash vt.handoff=1
Build Date: 25 October 2018 04:11:27PM
xorg-server 2:1.19.6-1ubuntu4.2 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Fri Feb 8 12:44:48 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.


I've tried installing lightdm (and toggling desktop environment between ubuntu and ubuntu with wayland) both don't work. With gdm3 unity works (but I want what I had before). I tried purging and installing ubuntu-desktop but that doesn't fix it either :(







xorg login






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 10 at 8:11







Seth

















asked Feb 8 at 20:47









SethSeth

214




214








  • 1





    This isn't a forum! Please do not post a solution in the question itself (or add "solved"). Please remove the edit and post it as an answer that you can later accept and receive points for it.

    – GabrielaGarcia
    Feb 9 at 2:38














  • 1





    This isn't a forum! Please do not post a solution in the question itself (or add "solved"). Please remove the edit and post it as an answer that you can later accept and receive points for it.

    – GabrielaGarcia
    Feb 9 at 2:38








1




1





This isn't a forum! Please do not post a solution in the question itself (or add "solved"). Please remove the edit and post it as an answer that you can later accept and receive points for it.

– GabrielaGarcia
Feb 9 at 2:38





This isn't a forum! Please do not post a solution in the question itself (or add "solved"). Please remove the edit and post it as an answer that you can later accept and receive points for it.

– GabrielaGarcia
Feb 9 at 2:38










1 Answer
1






active

oldest

votes


















0














It turned out one of my gnome-shell extensions was broken. I had tried gnome-shell-extensions-tool -d <NAME> which claims it disabled the extension but I had to move the folder out of the directory to fix it.






share|improve this answer























    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116780%2f18-04-stuck-in-login-loop-startx-fails%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    It turned out one of my gnome-shell extensions was broken. I had tried gnome-shell-extensions-tool -d <NAME> which claims it disabled the extension but I had to move the folder out of the directory to fix it.






    share|improve this answer




























      0














      It turned out one of my gnome-shell extensions was broken. I had tried gnome-shell-extensions-tool -d <NAME> which claims it disabled the extension but I had to move the folder out of the directory to fix it.






      share|improve this answer


























        0












        0








        0







        It turned out one of my gnome-shell extensions was broken. I had tried gnome-shell-extensions-tool -d <NAME> which claims it disabled the extension but I had to move the folder out of the directory to fix it.






        share|improve this answer













        It turned out one of my gnome-shell extensions was broken. I had tried gnome-shell-extensions-tool -d <NAME> which claims it disabled the extension but I had to move the folder out of the directory to fix it.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 10 at 8:12









        SethSeth

        214




        214






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116780%2f18-04-stuck-in-login-loop-startx-fails%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

            is 'sed' thread safe

            How to make a Squid Proxy server?