Kubuntu 18.04 not login from SDDM but from tty












0















I have installed Kubuntu 18.04 on my laptop (OMEN HP [17-w033dx
]) and today, just after enabling VT on the BIOS Setup and rebooting, Kubuntu not login from visual (SDDM) as usual. I disabled VT but the issue persist.



If I switch to an alternative tty and start the X Server with the startx command, all works fine.



What would be the solution for this issue?



If you need some extra information, like logs or anything to deep on, just say the log file or command and I will post and edit of the post.



EDIT



Complete .xsession-errors log file:
.xsession-errors






kubuntu login tty session sddm







share|improve this question

























  • Maybe the output of tail ~/.xsession-errors?

    – steeldriver
    Feb 19 at 2:59











  • I've updated the question with a link to the .xsession-errors file content.

    – Yulio Aleman Jimenez
    Feb 19 at 16:02
















0















I have installed Kubuntu 18.04 on my laptop (OMEN HP [17-w033dx
]) and today, just after enabling VT on the BIOS Setup and rebooting, Kubuntu not login from visual (SDDM) as usual. I disabled VT but the issue persist.



If I switch to an alternative tty and start the X Server with the startx command, all works fine.



What would be the solution for this issue?



If you need some extra information, like logs or anything to deep on, just say the log file or command and I will post and edit of the post.



EDIT



Complete .xsession-errors log file:
.xsession-errors






kubuntu login tty session sddm







share|improve this question

























  • Maybe the output of tail ~/.xsession-errors?

    – steeldriver
    Feb 19 at 2:59











  • I've updated the question with a link to the .xsession-errors file content.

    – Yulio Aleman Jimenez
    Feb 19 at 16:02














0












0








0








I have installed Kubuntu 18.04 on my laptop (OMEN HP [17-w033dx
]) and today, just after enabling VT on the BIOS Setup and rebooting, Kubuntu not login from visual (SDDM) as usual. I disabled VT but the issue persist.



If I switch to an alternative tty and start the X Server with the startx command, all works fine.



What would be the solution for this issue?



If you need some extra information, like logs or anything to deep on, just say the log file or command and I will post and edit of the post.



EDIT



Complete .xsession-errors log file:
.xsession-errors






kubuntu login tty session sddm







share|improve this question
















I have installed Kubuntu 18.04 on my laptop (OMEN HP [17-w033dx
]) and today, just after enabling VT on the BIOS Setup and rebooting, Kubuntu not login from visual (SDDM) as usual. I disabled VT but the issue persist.



If I switch to an alternative tty and start the X Server with the startx command, all works fine.



What would be the solution for this issue?



If you need some extra information, like logs or anything to deep on, just say the log file or command and I will post and edit of the post.



EDIT



Complete .xsession-errors log file:
.xsession-errors






kubuntu login tty session sddm




kubuntu login tty session sddm






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 19 at 15:57







Yulio Aleman Jimenez

















asked Feb 18 at 23:31









Yulio Aleman JimenezYulio Aleman Jimenez

1066




1066













  • Maybe the output of tail ~/.xsession-errors?

    – steeldriver
    Feb 19 at 2:59











  • I've updated the question with a link to the .xsession-errors file content.

    – Yulio Aleman Jimenez
    Feb 19 at 16:02



















  • Maybe the output of tail ~/.xsession-errors?

    – steeldriver
    Feb 19 at 2:59











  • I've updated the question with a link to the .xsession-errors file content.

    – Yulio Aleman Jimenez
    Feb 19 at 16:02

















Maybe the output of tail ~/.xsession-errors?

– steeldriver
Feb 19 at 2:59





Maybe the output of tail ~/.xsession-errors?

– steeldriver
Feb 19 at 2:59













I've updated the question with a link to the .xsession-errors file content.

– Yulio Aleman Jimenez
Feb 19 at 16:02





I've updated the question with a link to the .xsession-errors file content.

– Yulio Aleman Jimenez
Feb 19 at 16:02










1 Answer
1






active

oldest

votes


















0














After review carefully several log files, I realize that the SDDM were putting its logs into the /var/log/syslog, so reviewing carefully this file, and after try several options, this lines were came up in front of me:



systemd[1613]: /usr/lib/environment.d/99-environment.conf:16: invalid variable name "export ANDROID_HOME", ignoring.

systemd[1613]: /usr/lib/environment.d/99-environment.conf:17: invalid variable name "export PATH", ignoring.

systemd[1613]: /usr/lib/environment.d/99-environment.conf:18: invalid variable name "export PATH", ignoring.

systemd[1613]: /usr/lib/environment.d/99-environment.conf:19: invalid variable name "export PATH", ignoring.

systemd[1613]: /usr/lib/environment.d/99-environment.conf:20: invalid variable name "export PATH", ignoring.


So, I commented these lines inside the /etc/environment and everything went ok.



export ANDROID_HOME=/media/my-user/ANDROID/SDK/sdk-linux

export PATH=$PATH:$ANDROID_HOME/emulator

export PATH=$PATH:$ANDROID_HOME/tools

export PATH=$PATH:$ANDROID_HOME/tools/bin

export PATH=$PATH:$ANDROID_HOME/platform-tools


Finally I cut these configuration from the /etc/environment and pasted it inside the /home/my-user/.profile for a better configuration.



Just a few lines in a wrong config file of the system caused this disaster, :(






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%2f1119363%2fkubuntu-18-04-not-login-from-sddm-but-from-tty%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














    After review carefully several log files, I realize that the SDDM were putting its logs into the /var/log/syslog, so reviewing carefully this file, and after try several options, this lines were came up in front of me:



    systemd[1613]: /usr/lib/environment.d/99-environment.conf:16: invalid variable name "export ANDROID_HOME", ignoring.
    
systemd[1613]: /usr/lib/environment.d/99-environment.conf:17: invalid variable name "export PATH", ignoring.
    
systemd[1613]: /usr/lib/environment.d/99-environment.conf:18: invalid variable name "export PATH", ignoring.
    
systemd[1613]: /usr/lib/environment.d/99-environment.conf:19: invalid variable name "export PATH", ignoring.
    
systemd[1613]: /usr/lib/environment.d/99-environment.conf:20: invalid variable name "export PATH", ignoring.


    So, I commented these lines inside the /etc/environment and everything went ok.



    export ANDROID_HOME=/media/my-user/ANDROID/SDK/sdk-linux
    
export PATH=$PATH:$ANDROID_HOME/emulator
    
export PATH=$PATH:$ANDROID_HOME/tools
    
export PATH=$PATH:$ANDROID_HOME/tools/bin
    
export PATH=$PATH:$ANDROID_HOME/platform-tools


    Finally I cut these configuration from the /etc/environment and pasted it inside the /home/my-user/.profile for a better configuration.



    Just a few lines in a wrong config file of the system caused this disaster, :(






    share|improve this answer




























      0














      After review carefully several log files, I realize that the SDDM were putting its logs into the /var/log/syslog, so reviewing carefully this file, and after try several options, this lines were came up in front of me:



      systemd[1613]: /usr/lib/environment.d/99-environment.conf:16: invalid variable name "export ANDROID_HOME", ignoring.
      
systemd[1613]: /usr/lib/environment.d/99-environment.conf:17: invalid variable name "export PATH", ignoring.
      
systemd[1613]: /usr/lib/environment.d/99-environment.conf:18: invalid variable name "export PATH", ignoring.
      
systemd[1613]: /usr/lib/environment.d/99-environment.conf:19: invalid variable name "export PATH", ignoring.
      
systemd[1613]: /usr/lib/environment.d/99-environment.conf:20: invalid variable name "export PATH", ignoring.


      So, I commented these lines inside the /etc/environment and everything went ok.



      export ANDROID_HOME=/media/my-user/ANDROID/SDK/sdk-linux
      
export PATH=$PATH:$ANDROID_HOME/emulator
      
export PATH=$PATH:$ANDROID_HOME/tools
      
export PATH=$PATH:$ANDROID_HOME/tools/bin
      
export PATH=$PATH:$ANDROID_HOME/platform-tools


      Finally I cut these configuration from the /etc/environment and pasted it inside the /home/my-user/.profile for a better configuration.



      Just a few lines in a wrong config file of the system caused this disaster, :(






      share|improve this answer


























        0












        0








        0







        After review carefully several log files, I realize that the SDDM were putting its logs into the /var/log/syslog, so reviewing carefully this file, and after try several options, this lines were came up in front of me:



        systemd[1613]: /usr/lib/environment.d/99-environment.conf:16: invalid variable name "export ANDROID_HOME", ignoring.
        
systemd[1613]: /usr/lib/environment.d/99-environment.conf:17: invalid variable name "export PATH", ignoring.
        
systemd[1613]: /usr/lib/environment.d/99-environment.conf:18: invalid variable name "export PATH", ignoring.
        
systemd[1613]: /usr/lib/environment.d/99-environment.conf:19: invalid variable name "export PATH", ignoring.
        
systemd[1613]: /usr/lib/environment.d/99-environment.conf:20: invalid variable name "export PATH", ignoring.


        So, I commented these lines inside the /etc/environment and everything went ok.



        export ANDROID_HOME=/media/my-user/ANDROID/SDK/sdk-linux
        
export PATH=$PATH:$ANDROID_HOME/emulator
        
export PATH=$PATH:$ANDROID_HOME/tools
        
export PATH=$PATH:$ANDROID_HOME/tools/bin
        
export PATH=$PATH:$ANDROID_HOME/platform-tools


        Finally I cut these configuration from the /etc/environment and pasted it inside the /home/my-user/.profile for a better configuration.



        Just a few lines in a wrong config file of the system caused this disaster, :(






        share|improve this answer













        After review carefully several log files, I realize that the SDDM were putting its logs into the /var/log/syslog, so reviewing carefully this file, and after try several options, this lines were came up in front of me:



        systemd[1613]: /usr/lib/environment.d/99-environment.conf:16: invalid variable name "export ANDROID_HOME", ignoring.
        
systemd[1613]: /usr/lib/environment.d/99-environment.conf:17: invalid variable name "export PATH", ignoring.
        
systemd[1613]: /usr/lib/environment.d/99-environment.conf:18: invalid variable name "export PATH", ignoring.
        
systemd[1613]: /usr/lib/environment.d/99-environment.conf:19: invalid variable name "export PATH", ignoring.
        
systemd[1613]: /usr/lib/environment.d/99-environment.conf:20: invalid variable name "export PATH", ignoring.


        So, I commented these lines inside the /etc/environment and everything went ok.



        export ANDROID_HOME=/media/my-user/ANDROID/SDK/sdk-linux
        
export PATH=$PATH:$ANDROID_HOME/emulator
        
export PATH=$PATH:$ANDROID_HOME/tools
        
export PATH=$PATH:$ANDROID_HOME/tools/bin
        
export PATH=$PATH:$ANDROID_HOME/platform-tools


        Finally I cut these configuration from the /etc/environment and pasted it inside the /home/my-user/.profile for a better configuration.



        Just a few lines in a wrong config file of the system caused this disaster, :(







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 13 at 20:05









        Yulio Aleman JimenezYulio Aleman Jimenez

        1066




        1066






























            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%2f1119363%2fkubuntu-18-04-not-login-from-sddm-but-from-tty%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...

            Image
            0 I am having trouble trying to reconfigure my DTR container to try and use a CEPH FS mount we created to act as a storage backend for our image repository. The Docs are very vague on this and nothing exactly explains on how to do it. Has anyone yet connected the dots? linux filesystems mount storage docker share | improve this question asked Feb 1 at 6:40 jRapp3r jRapp3r 1 1 add a comment  | 
            Read more

            is 'sed' thread safe

            Image
            2 If I have a shell/python script that uses sed to modify a file in place based on user inputs, and then two users run the same script at the same time or approx. same time, is 'sed' thread safe ? Or perhaps it is not an issue because the file_descripor that was opened by the first thread will be used to lock the file anyway ? thx linux sed python share | improve this question edited 7 hours ago Jeff Schaller 42.9k 11 59 137 asked 7 hours ago terreys terreys
            Read more

            How to make a Squid Proxy server?

            Image
            1 I want to set up squid proxy server for monitoring user activity in a network and Internet Web URL filtering for user. I also want to configure the user login, user log, user access group, and block unwanted web sites in my network. Please help me and guide me the full process to do this. server proxy squid share | improve this question edited Jul 31 '12 at 14:45 Jorge Castro 37.1k 107 422 617 asked Jul 31 '12 at 5:16 Goivind Tiwari Goivind Tiwari
            Read more