Using XRDP without local VNC server

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











up vote
4
down vote

favorite
1












According to xrdp docs it should be possible to connect remotely without using a local VNC server:




xrdp can connect to a locally created X.org session
with the xorgxrdp drivers [my emphasis], to a VNC X11 server, and forward to
another RDP server.




I can connect with RDP from Windows:



enter image description here



Then I select Xorg session and supply username and password. After some timeout an error pops up about an unknown connection problem.



enter image description here



This is tail /var/log/xrdp.log and tail /var/log/xrdp-sesman.log output:



[DEBUG] Closed socket 17 (AF_UNIX) 
... 
[DEBUG] Closed socket 17 (AF_UNIX) 
[DEBUG] xrdp_wm_log_msg: some problem 
[DEBUG] xrdp_mm_module_cleanup 
[DEBUG] Closed socket 16 (AF_INET6 ::1 port 38094)


enter image description here



dmesg doesn't show any problems nor references to Xorg or similar. ps -A | grep rdp shows xrdp and xrdp-sesman processes running. Tried connecting with Windows 7 to Debian: same problem. xrdp.ini and sasman.ini:





In sesman.ini the AlwaysGroupCheck=false. The startwm.sh:



startwm.sh



Any ideas? Running on a virtualized minimal, clean Debian 9.1 installation. Only only lxde-core and xrdp installed with apt-get. (No errors during installation.) xorgxrdp drivers installed (since they depend on xrdp).






debian lxde xrdp







share|improve this question























  • Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging. xrdp.ini and sesman.ini using default settings? What about var/log/xrdp-sesman.log Strange error in xrdp log "some problem"... Does dmesg have any useful info?
    – jc__
    Aug 29 '17 at 14:40










  • @jc__, I didn't compile. I first installed lxde-core. Then, once logged in, installed xrdp which has a dependency on xorgxrdp. I'll update the question with other logs.
    – Davor Josipovic
    Aug 29 '17 at 15:27










  • Lets do some background checking: Verify the services are running ps -A | grep rdp. You should see both xrdp and xrdp-sesman. You are using the selection Xorg, so check the Xorg in xrdp.ini. Should be libxup.so library, ip=127.0.0.1 port=-1 then check the Xorg section in sesman.ini these are the parameters passed to Xorg. Note the log name. param=.xorgxrdp.%s.log. see your home directory for that log.
    – jc__
    Aug 29 '17 at 17:44










  • In sesman.ini verify the AlwaysGroupCheck= if false the login user does not need to be in the group assigned by TerminalServerUsers=
    – jc__
    Aug 29 '17 at 17:46










  • Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the --enable-painter option to make work with Win10.
    – jc__
    Aug 29 '17 at 17:53














up vote
4
down vote

favorite
1












According to xrdp docs it should be possible to connect remotely without using a local VNC server:




xrdp can connect to a locally created X.org session
with the xorgxrdp drivers [my emphasis], to a VNC X11 server, and forward to
another RDP server.




I can connect with RDP from Windows:



enter image description here



Then I select Xorg session and supply username and password. After some timeout an error pops up about an unknown connection problem.



enter image description here



This is tail /var/log/xrdp.log and tail /var/log/xrdp-sesman.log output:



[DEBUG] Closed socket 17 (AF_UNIX) 
... 
[DEBUG] Closed socket 17 (AF_UNIX) 
[DEBUG] xrdp_wm_log_msg: some problem 
[DEBUG] xrdp_mm_module_cleanup 
[DEBUG] Closed socket 16 (AF_INET6 ::1 port 38094)


enter image description here



dmesg doesn't show any problems nor references to Xorg or similar. ps -A | grep rdp shows xrdp and xrdp-sesman processes running. Tried connecting with Windows 7 to Debian: same problem. xrdp.ini and sasman.ini:





In sesman.ini the AlwaysGroupCheck=false. The startwm.sh:



startwm.sh



Any ideas? Running on a virtualized minimal, clean Debian 9.1 installation. Only only lxde-core and xrdp installed with apt-get. (No errors during installation.) xorgxrdp drivers installed (since they depend on xrdp).






debian lxde xrdp







share|improve this question























  • Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging. xrdp.ini and sesman.ini using default settings? What about var/log/xrdp-sesman.log Strange error in xrdp log "some problem"... Does dmesg have any useful info?
    – jc__
    Aug 29 '17 at 14:40










  • @jc__, I didn't compile. I first installed lxde-core. Then, once logged in, installed xrdp which has a dependency on xorgxrdp. I'll update the question with other logs.
    – Davor Josipovic
    Aug 29 '17 at 15:27










  • Lets do some background checking: Verify the services are running ps -A | grep rdp. You should see both xrdp and xrdp-sesman. You are using the selection Xorg, so check the Xorg in xrdp.ini. Should be libxup.so library, ip=127.0.0.1 port=-1 then check the Xorg section in sesman.ini these are the parameters passed to Xorg. Note the log name. param=.xorgxrdp.%s.log. see your home directory for that log.
    – jc__
    Aug 29 '17 at 17:44










  • In sesman.ini verify the AlwaysGroupCheck= if false the login user does not need to be in the group assigned by TerminalServerUsers=
    – jc__
    Aug 29 '17 at 17:46










  • Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the --enable-painter option to make work with Win10.
    – jc__
    Aug 29 '17 at 17:53












up vote
4
down vote

favorite
1









up vote
4
down vote

favorite
1






1





According to xrdp docs it should be possible to connect remotely without using a local VNC server:




xrdp can connect to a locally created X.org session
with the xorgxrdp drivers [my emphasis], to a VNC X11 server, and forward to
another RDP server.




I can connect with RDP from Windows:



enter image description here



Then I select Xorg session and supply username and password. After some timeout an error pops up about an unknown connection problem.



enter image description here



This is tail /var/log/xrdp.log and tail /var/log/xrdp-sesman.log output:



[DEBUG] Closed socket 17 (AF_UNIX) 
... 
[DEBUG] Closed socket 17 (AF_UNIX) 
[DEBUG] xrdp_wm_log_msg: some problem 
[DEBUG] xrdp_mm_module_cleanup 
[DEBUG] Closed socket 16 (AF_INET6 ::1 port 38094)


enter image description here



dmesg doesn't show any problems nor references to Xorg or similar. ps -A | grep rdp shows xrdp and xrdp-sesman processes running. Tried connecting with Windows 7 to Debian: same problem. xrdp.ini and sasman.ini:





In sesman.ini the AlwaysGroupCheck=false. The startwm.sh:



startwm.sh



Any ideas? Running on a virtualized minimal, clean Debian 9.1 installation. Only only lxde-core and xrdp installed with apt-get. (No errors during installation.) xorgxrdp drivers installed (since they depend on xrdp).






debian lxde xrdp







share|improve this question















According to xrdp docs it should be possible to connect remotely without using a local VNC server:




xrdp can connect to a locally created X.org session
with the xorgxrdp drivers [my emphasis], to a VNC X11 server, and forward to
another RDP server.




I can connect with RDP from Windows:



enter image description here



Then I select Xorg session and supply username and password. After some timeout an error pops up about an unknown connection problem.



enter image description here



This is tail /var/log/xrdp.log and tail /var/log/xrdp-sesman.log output:



[DEBUG] Closed socket 17 (AF_UNIX) 
... 
[DEBUG] Closed socket 17 (AF_UNIX) 
[DEBUG] xrdp_wm_log_msg: some problem 
[DEBUG] xrdp_mm_module_cleanup 
[DEBUG] Closed socket 16 (AF_INET6 ::1 port 38094)


enter image description here



dmesg doesn't show any problems nor references to Xorg or similar. ps -A | grep rdp shows xrdp and xrdp-sesman processes running. Tried connecting with Windows 7 to Debian: same problem. xrdp.ini and sasman.ini:





In sesman.ini the AlwaysGroupCheck=false. The startwm.sh:



startwm.sh



Any ideas? Running on a virtualized minimal, clean Debian 9.1 installation. Only only lxde-core and xrdp installed with apt-get. (No errors during installation.) xorgxrdp drivers installed (since they depend on xrdp).






debian lxde xrdp




debian lxde xrdp






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 29 '17 at 21:13

























asked Aug 29 '17 at 8:11









Davor Josipovic

206210




206210











  • Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging. xrdp.ini and sesman.ini using default settings? What about var/log/xrdp-sesman.log Strange error in xrdp log "some problem"... Does dmesg have any useful info?
    – jc__
    Aug 29 '17 at 14:40










  • @jc__, I didn't compile. I first installed lxde-core. Then, once logged in, installed xrdp which has a dependency on xorgxrdp. I'll update the question with other logs.
    – Davor Josipovic
    Aug 29 '17 at 15:27










  • Lets do some background checking: Verify the services are running ps -A | grep rdp. You should see both xrdp and xrdp-sesman. You are using the selection Xorg, so check the Xorg in xrdp.ini. Should be libxup.so library, ip=127.0.0.1 port=-1 then check the Xorg section in sesman.ini these are the parameters passed to Xorg. Note the log name. param=.xorgxrdp.%s.log. see your home directory for that log.
    – jc__
    Aug 29 '17 at 17:44










  • In sesman.ini verify the AlwaysGroupCheck= if false the login user does not need to be in the group assigned by TerminalServerUsers=
    – jc__
    Aug 29 '17 at 17:46










  • Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the --enable-painter option to make work with Win10.
    – jc__
    Aug 29 '17 at 17:53
















  • Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging. xrdp.ini and sesman.ini using default settings? What about var/log/xrdp-sesman.log Strange error in xrdp log "some problem"... Does dmesg have any useful info?
    – jc__
    Aug 29 '17 at 14:40










  • @jc__, I didn't compile. I first installed lxde-core. Then, once logged in, installed xrdp which has a dependency on xorgxrdp. I'll update the question with other logs.
    – Davor Josipovic
    Aug 29 '17 at 15:27










  • Lets do some background checking: Verify the services are running ps -A | grep rdp. You should see both xrdp and xrdp-sesman. You are using the selection Xorg, so check the Xorg in xrdp.ini. Should be libxup.so library, ip=127.0.0.1 port=-1 then check the Xorg section in sesman.ini these are the parameters passed to Xorg. Note the log name. param=.xorgxrdp.%s.log. see your home directory for that log.
    – jc__
    Aug 29 '17 at 17:44










  • In sesman.ini verify the AlwaysGroupCheck= if false the login user does not need to be in the group assigned by TerminalServerUsers=
    – jc__
    Aug 29 '17 at 17:46










  • Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the --enable-painter option to make work with Win10.
    – jc__
    Aug 29 '17 at 17:53















Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging. xrdp.ini and sesman.ini using default settings? What about var/log/xrdp-sesman.log Strange error in xrdp log "some problem"... Does dmesg have any useful info?
– jc__
Aug 29 '17 at 14:40




Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging. xrdp.ini and sesman.ini using default settings? What about var/log/xrdp-sesman.log Strange error in xrdp log "some problem"... Does dmesg have any useful info?
– jc__
Aug 29 '17 at 14:40












@jc__, I didn't compile. I first installed lxde-core. Then, once logged in, installed xrdp which has a dependency on xorgxrdp. I'll update the question with other logs.
– Davor Josipovic
Aug 29 '17 at 15:27




@jc__, I didn't compile. I first installed lxde-core. Then, once logged in, installed xrdp which has a dependency on xorgxrdp. I'll update the question with other logs.
– Davor Josipovic
Aug 29 '17 at 15:27












Lets do some background checking: Verify the services are running ps -A | grep rdp. You should see both xrdp and xrdp-sesman. You are using the selection Xorg, so check the Xorg in xrdp.ini. Should be libxup.so library, ip=127.0.0.1 port=-1 then check the Xorg section in sesman.ini these are the parameters passed to Xorg. Note the log name. param=.xorgxrdp.%s.log. see your home directory for that log.
– jc__
Aug 29 '17 at 17:44




Lets do some background checking: Verify the services are running ps -A | grep rdp. You should see both xrdp and xrdp-sesman. You are using the selection Xorg, so check the Xorg in xrdp.ini. Should be libxup.so library, ip=127.0.0.1 port=-1 then check the Xorg section in sesman.ini these are the parameters passed to Xorg. Note the log name. param=.xorgxrdp.%s.log. see your home directory for that log.
– jc__
Aug 29 '17 at 17:44












In sesman.ini verify the AlwaysGroupCheck= if false the login user does not need to be in the group assigned by TerminalServerUsers=
– jc__
Aug 29 '17 at 17:46




In sesman.ini verify the AlwaysGroupCheck= if false the login user does not need to be in the group assigned by TerminalServerUsers=
– jc__
Aug 29 '17 at 17:46












Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the --enable-painter option to make work with Win10.
– jc__
Aug 29 '17 at 17:53




Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the --enable-painter option to make work with Win10.
– jc__
Aug 29 '17 at 17:53










2 Answers
2






active

oldest

votes

















up vote
6
down vote



accepted










This bug report has the same symptoms as described in the question. Seems xserver-xorg-legacy package is the culprit. So to make it work, it boils down to the following two commands:



apt-get purge xserver-xorg-legacy
apt-get install xrdp


The required services are started automatically after install. No need to reboot. Connecting and authenticating should automatically show the desktop.



I do not know though what the consequences are of removing xserver-xorg-legacy. In the bug report it is mentioned to remove if not needed.






share|improve this answer



























    up vote
    0
    down vote













    You can refer to the question!




    Attention: you need to use dpkg-reconfigure xserver-xorg-legacy command to change the setting in debian 9.






    share








    New contributor




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

















      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%2f389005%2fusing-xrdp-without-local-vnc-server%23new-answer', 'question_page');

      );

      Post as a guest

















      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      6
      down vote



      accepted










      This bug report has the same symptoms as described in the question. Seems xserver-xorg-legacy package is the culprit. So to make it work, it boils down to the following two commands:



      apt-get purge xserver-xorg-legacy
      apt-get install xrdp


      The required services are started automatically after install. No need to reboot. Connecting and authenticating should automatically show the desktop.



      I do not know though what the consequences are of removing xserver-xorg-legacy. In the bug report it is mentioned to remove if not needed.






      share|improve this answer
























        up vote
        6
        down vote



        accepted










        This bug report has the same symptoms as described in the question. Seems xserver-xorg-legacy package is the culprit. So to make it work, it boils down to the following two commands:



        apt-get purge xserver-xorg-legacy
        apt-get install xrdp


        The required services are started automatically after install. No need to reboot. Connecting and authenticating should automatically show the desktop.



        I do not know though what the consequences are of removing xserver-xorg-legacy. In the bug report it is mentioned to remove if not needed.






        share|improve this answer






















          up vote
          6
          down vote



          accepted







          up vote
          6
          down vote



          accepted






          This bug report has the same symptoms as described in the question. Seems xserver-xorg-legacy package is the culprit. So to make it work, it boils down to the following two commands:



          apt-get purge xserver-xorg-legacy
          apt-get install xrdp


          The required services are started automatically after install. No need to reboot. Connecting and authenticating should automatically show the desktop.



          I do not know though what the consequences are of removing xserver-xorg-legacy. In the bug report it is mentioned to remove if not needed.






          share|improve this answer












          This bug report has the same symptoms as described in the question. Seems xserver-xorg-legacy package is the culprit. So to make it work, it boils down to the following two commands:



          apt-get purge xserver-xorg-legacy
          apt-get install xrdp


          The required services are started automatically after install. No need to reboot. Connecting and authenticating should automatically show the desktop.



          I do not know though what the consequences are of removing xserver-xorg-legacy. In the bug report it is mentioned to remove if not needed.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 29 '17 at 21:10









          Davor Josipovic

          206210




          206210






















              up vote
              0
              down vote













              You can refer to the question!




              Attention: you need to use dpkg-reconfigure xserver-xorg-legacy command to change the setting in debian 9.






              share








              New contributor




              li1234yun 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













                You can refer to the question!




                Attention: you need to use dpkg-reconfigure xserver-xorg-legacy command to change the setting in debian 9.






                share








                New contributor




                li1234yun 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









                  You can refer to the question!




                  Attention: you need to use dpkg-reconfigure xserver-xorg-legacy command to change the setting in debian 9.






                  share








                  New contributor




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









                  You can refer to the question!




                  Attention: you need to use dpkg-reconfigure xserver-xorg-legacy command to change the setting in debian 9.







                  share








                  New contributor




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








                  share


                  share






                  New contributor




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









                  answered 3 mins ago









                  li1234yun

                  1




                  1




                  New contributor




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





                  New contributor





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






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



























                       

                      draft saved


                      draft discarded















































                       


                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f389005%2fusing-xrdp-without-local-vnc-server%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?

                      Image
                      Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
                      Read more

                      Running qemu-guest-agent on windows server 2008

                      Image
                      Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I know how I need to configure any linux guestvm in order to make qemu-guest-agent work. This is because there is a lot of documentation on it available, this is not the same with a windows guest. I wanted to know what steps I need to take to make qemu-GA work with a windows guest. I know I need to specify a channel type in the xml file of my windows vm, but further than that?? Does somebody has some more experience with this? Thanks. Running system: Debian 9 (on VMware) 3GB ram & 100GB DISK Running libvirt Daemon Several other guest vms running in background Windows guest: Windows server 2012 512MB RAM & 32GB DISK Virtio drivers working windows virtual-machine kvm qemu libvirtd share | improve this question asked Jan 13 at 0:02 codenerd123 1 1 add a comment  |  up vote 0 down vote favorite I know how I need to configure any linux guestvm in...
                      Read more

                      Christian Cage

                      Image
                      Christian Cage Christian in March 2015 Birth name William Jason Reso Born ( 1973-11-30 ) November 30, 1973 (age 45) Kitchener, Ontario, Canada Residence Tampa, Florida, United States Spouse(s) Denise Hartmann ( m.   2001 ) Children 1 Professional wrestling career Ring name(s) Christian [1] Christian Cage [2] Conquistador Dos [3] Male Nurse [4] Billed height 6 ft 1 in (1.85 m) [1] Billed weight 212 lb (96 kg) [1] Billed from Tampa, Florida (WM18, TNA) Toronto, Ontario, Canada [1] Trained by Dory Funk Jr. [2] Ron Hutchison [5] Debut 1995 [5] Retired 2014 [6] William Jason Reso (born November 30, 1973) is a Canadian actor, podcaster and retired professional wrestler best known for his time in WWE under the ring name Christian , a shortened version of his original ring name Christian Cage that was also used during his tenure in Total Nonstop Action Wrestling (TNA). Reso was trained by former professional wrestlers Ron Hutchison and Dory Funk Jr. and m...
                      Read more