X: user not authorized to run the X server, aborting

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












After I login to a server using ssh and try to initiate X11 I got the below error message:



$startx
X: user not authorized to run the X server, aborting.
xinit: giving up
xinit: server error


by checking the /etc/X11/Xwrapper.config, it shows



allowed_users=console


I am wondering how to fix this issue. I also don't have the root privilege for some setting changes.










share|improve this question























  • did you try changing the word console to anybody yet ?
    – MelBurslan
    Aug 18 '16 at 18:17










  • It turns out I don't have root privilege to make that change. It seems also not suggested for security reasons.
    – Dadong Zhang
    Aug 18 '16 at 18:33














up vote
0
down vote

favorite












After I login to a server using ssh and try to initiate X11 I got the below error message:



$startx
X: user not authorized to run the X server, aborting.
xinit: giving up
xinit: server error


by checking the /etc/X11/Xwrapper.config, it shows



allowed_users=console


I am wondering how to fix this issue. I also don't have the root privilege for some setting changes.










share|improve this question























  • did you try changing the word console to anybody yet ?
    – MelBurslan
    Aug 18 '16 at 18:17










  • It turns out I don't have root privilege to make that change. It seems also not suggested for security reasons.
    – Dadong Zhang
    Aug 18 '16 at 18:33












up vote
0
down vote

favorite









up vote
0
down vote

favorite











After I login to a server using ssh and try to initiate X11 I got the below error message:



$startx
X: user not authorized to run the X server, aborting.
xinit: giving up
xinit: server error


by checking the /etc/X11/Xwrapper.config, it shows



allowed_users=console


I am wondering how to fix this issue. I also don't have the root privilege for some setting changes.










share|improve this question















After I login to a server using ssh and try to initiate X11 I got the below error message:



$startx
X: user not authorized to run the X server, aborting.
xinit: giving up
xinit: server error


by checking the /etc/X11/Xwrapper.config, it shows



allowed_users=console


I am wondering how to fix this issue. I also don't have the root privilege for some setting changes.







x11 login privileges






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 18 '16 at 21:46









Gilles

515k12210241554




515k12210241554










asked Aug 18 '16 at 18:10









Dadong Zhang

282158




282158











  • did you try changing the word console to anybody yet ?
    – MelBurslan
    Aug 18 '16 at 18:17










  • It turns out I don't have root privilege to make that change. It seems also not suggested for security reasons.
    – Dadong Zhang
    Aug 18 '16 at 18:33
















  • did you try changing the word console to anybody yet ?
    – MelBurslan
    Aug 18 '16 at 18:17










  • It turns out I don't have root privilege to make that change. It seems also not suggested for security reasons.
    – Dadong Zhang
    Aug 18 '16 at 18:33















did you try changing the word console to anybody yet ?
– MelBurslan
Aug 18 '16 at 18:17




did you try changing the word console to anybody yet ?
– MelBurslan
Aug 18 '16 at 18:17












It turns out I don't have root privilege to make that change. It seems also not suggested for security reasons.
– Dadong Zhang
Aug 18 '16 at 18:33




It turns out I don't have root privilege to make that change. It seems also not suggested for security reasons.
– Dadong Zhang
Aug 18 '16 at 18:33










3 Answers
3






active

oldest

votes

















up vote
1
down vote













It depends on what you are trying to do:



  • if you had permissions, at best you would get X running, using the console of the computer which you connected to for its display. You wouldn't get X running on the local machine from which you ran ssh.

  • if you logged in on the console, you would have permissions to startx — still on that display.

  • if you are trying to run an X application on the server, displaying on your local machine, the way to do this is to have X running on the local machine, and using X forwarding (establishing an authorized connection) run the application via ssh, displaying on your local machine. You do not have to startx on the remote machine for that.

Further reading:



  • X Over SSH2 - A Tutorial

  • How to forward X over SSH from Ubuntu machine?





share|improve this answer





























    up vote
    0
    down vote













    For my debian jessie, no session manager, only x11, xorg and mwm (motif window manager), I got this problem only after copying my home folder from another debian jessie host. Turns out that when I moved the ~/.Xsession to a temporary ~/old folder, it corrected the issue.



    mv ~/.Xsession ~/old



    In addition, I found out that gnu-screen would generate "X: user not authorized to run the x server, aborting." – aanhouden 1 min ago edit



    Hope this helps others.






    share|improve this answer










    New contributor




    aanhouden is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.
























      up vote
      -1
      down vote













      dpkg-reconfigure x11-common


      This will work.






      share|improve this answer






















      • How will it work? What does it do?
        – Zv_oDD
        Jul 21 at 6:20










      Your Answer







      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "106"
      ;
      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',
      convertImagesToLinks: false,
      noModals: false,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













       

      draft saved


      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f304302%2fx-user-not-authorized-to-run-the-x-server-aborting%23new-answer', 'question_page');

      );

      Post as a guest






























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      1
      down vote













      It depends on what you are trying to do:



      • if you had permissions, at best you would get X running, using the console of the computer which you connected to for its display. You wouldn't get X running on the local machine from which you ran ssh.

      • if you logged in on the console, you would have permissions to startx — still on that display.

      • if you are trying to run an X application on the server, displaying on your local machine, the way to do this is to have X running on the local machine, and using X forwarding (establishing an authorized connection) run the application via ssh, displaying on your local machine. You do not have to startx on the remote machine for that.

      Further reading:



      • X Over SSH2 - A Tutorial

      • How to forward X over SSH from Ubuntu machine?





      share|improve this answer


























        up vote
        1
        down vote













        It depends on what you are trying to do:



        • if you had permissions, at best you would get X running, using the console of the computer which you connected to for its display. You wouldn't get X running on the local machine from which you ran ssh.

        • if you logged in on the console, you would have permissions to startx — still on that display.

        • if you are trying to run an X application on the server, displaying on your local machine, the way to do this is to have X running on the local machine, and using X forwarding (establishing an authorized connection) run the application via ssh, displaying on your local machine. You do not have to startx on the remote machine for that.

        Further reading:



        • X Over SSH2 - A Tutorial

        • How to forward X over SSH from Ubuntu machine?





        share|improve this answer
























          up vote
          1
          down vote










          up vote
          1
          down vote









          It depends on what you are trying to do:



          • if you had permissions, at best you would get X running, using the console of the computer which you connected to for its display. You wouldn't get X running on the local machine from which you ran ssh.

          • if you logged in on the console, you would have permissions to startx — still on that display.

          • if you are trying to run an X application on the server, displaying on your local machine, the way to do this is to have X running on the local machine, and using X forwarding (establishing an authorized connection) run the application via ssh, displaying on your local machine. You do not have to startx on the remote machine for that.

          Further reading:



          • X Over SSH2 - A Tutorial

          • How to forward X over SSH from Ubuntu machine?





          share|improve this answer














          It depends on what you are trying to do:



          • if you had permissions, at best you would get X running, using the console of the computer which you connected to for its display. You wouldn't get X running on the local machine from which you ran ssh.

          • if you logged in on the console, you would have permissions to startx — still on that display.

          • if you are trying to run an X application on the server, displaying on your local machine, the way to do this is to have X running on the local machine, and using X forwarding (establishing an authorized connection) run the application via ssh, displaying on your local machine. You do not have to startx on the remote machine for that.

          Further reading:



          • X Over SSH2 - A Tutorial

          • How to forward X over SSH from Ubuntu machine?






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Apr 13 '17 at 12:36









          Community♦

          1




          1










          answered Aug 18 '16 at 21:57









          Thomas Dickey

          50.6k588160




          50.6k588160






















              up vote
              0
              down vote













              For my debian jessie, no session manager, only x11, xorg and mwm (motif window manager), I got this problem only after copying my home folder from another debian jessie host. Turns out that when I moved the ~/.Xsession to a temporary ~/old folder, it corrected the issue.



              mv ~/.Xsession ~/old



              In addition, I found out that gnu-screen would generate "X: user not authorized to run the x server, aborting." – aanhouden 1 min ago edit



              Hope this helps others.






              share|improve this answer










              New contributor




              aanhouden is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.





















                up vote
                0
                down vote













                For my debian jessie, no session manager, only x11, xorg and mwm (motif window manager), I got this problem only after copying my home folder from another debian jessie host. Turns out that when I moved the ~/.Xsession to a temporary ~/old folder, it corrected the issue.



                mv ~/.Xsession ~/old



                In addition, I found out that gnu-screen would generate "X: user not authorized to run the x server, aborting." – aanhouden 1 min ago edit



                Hope this helps others.






                share|improve this answer










                New contributor




                aanhouden is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.



















                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  For my debian jessie, no session manager, only x11, xorg and mwm (motif window manager), I got this problem only after copying my home folder from another debian jessie host. Turns out that when I moved the ~/.Xsession to a temporary ~/old folder, it corrected the issue.



                  mv ~/.Xsession ~/old



                  In addition, I found out that gnu-screen would generate "X: user not authorized to run the x server, aborting." – aanhouden 1 min ago edit



                  Hope this helps others.






                  share|improve this answer










                  New contributor




                  aanhouden is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  For my debian jessie, no session manager, only x11, xorg and mwm (motif window manager), I got this problem only after copying my home folder from another debian jessie host. Turns out that when I moved the ~/.Xsession to a temporary ~/old folder, it corrected the issue.



                  mv ~/.Xsession ~/old



                  In addition, I found out that gnu-screen would generate "X: user not authorized to run the x server, aborting." – aanhouden 1 min ago edit



                  Hope this helps others.







                  share|improve this answer










                  New contributor




                  aanhouden is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  share|improve this answer



                  share|improve this answer








                  edited 14 secs ago





















                  New contributor




                  aanhouden is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 11 mins ago









                  aanhouden

                  1




                  1




                  New contributor




                  aanhouden is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  aanhouden is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  aanhouden is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.




















                      up vote
                      -1
                      down vote













                      dpkg-reconfigure x11-common


                      This will work.






                      share|improve this answer






















                      • How will it work? What does it do?
                        – Zv_oDD
                        Jul 21 at 6:20














                      up vote
                      -1
                      down vote













                      dpkg-reconfigure x11-common


                      This will work.






                      share|improve this answer






















                      • How will it work? What does it do?
                        – Zv_oDD
                        Jul 21 at 6:20












                      up vote
                      -1
                      down vote










                      up vote
                      -1
                      down vote









                      dpkg-reconfigure x11-common


                      This will work.






                      share|improve this answer














                      dpkg-reconfigure x11-common


                      This will work.







                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Apr 26 '17 at 19:39









                      Stephen Rauch

                      3,268101328




                      3,268101328










                      answered Apr 26 '17 at 19:19









                      shubham

                      1




                      1











                      • How will it work? What does it do?
                        – Zv_oDD
                        Jul 21 at 6:20
















                      • How will it work? What does it do?
                        – Zv_oDD
                        Jul 21 at 6:20















                      How will it work? What does it do?
                      – Zv_oDD
                      Jul 21 at 6:20




                      How will it work? What does it do?
                      – Zv_oDD
                      Jul 21 at 6:20

















                       

                      draft saved


                      draft discarded















































                       


                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f304302%2fx-user-not-authorized-to-run-the-x-server-aborting%23new-answer', 'question_page');

                      );

                      Post as a guest













































































                      Popular posts from this blog

                      How to check contact read email or not when send email to Individual?

                      Displaying single band from multi-band raster using QGIS

                      How many registers does an x86_64 CPU actually have?