Date: Wed, 8 Aug 2018 18:32:38 +0200 From: Oleg Cherkasov <o1e9.cherkasov@yandex.com> To: freebsd-questions@freebsd.org Subject: Re: xrdp configuration and xfce4 Message-ID: <b30465dd-4a7e-a9fc-6bf1-ae41b8da3a93@yandex.com> In-Reply-To: <3d2a1aa3-94de-e4e7-bb1d-a54ff7a92f94@networktest.com> References: <d3534b9a-4061-5f6b-e94c-68646700f194@networktest.com> <caf921f910fe2dec5d4a6ed19e682cef@freebsd.org> <7d12e2d7-e8e6-53d0-3c62-d3ca8868f9be@networktest.com> <20180808013151.sia5lgegjcxu2pr3@icepick.vmeta.jp> <3d2a1aa3-94de-e4e7-bb1d-a54ff7a92f94@networktest.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08. aug. 2018 04:10, David Newman wrote: > On 8/7/18 6:31 PM, Koichiro Iwao wrote: >> On Tue, Aug 07, 2018 at 06:24:15PM -0700, David Newman wrote: >>> Not sure what changes I would make in startxm.sh to automate this. The >>> existing script has file locations for X on Linux distros. >> >> Really? >> >> ``` >> #!/bin/sh >> startxfce4 >> ``` >> >> That's all. > > Sorry, no go. > > A startwm.sh script with just these two lines produces a black screen > with one xterm and doesn't start xfce, let alone deal with the > copy/paste problem. > > Also tried with '/usr/local/bin/xfce4-session' but got the same results. > > Either of these is exactly the same outcome as using the default > startxm.sh script supplied with xrdp from the pkg repo. > > I am restarting the xrdp service and exiting the xterm after each attempt. > > If you have this working successfully with a similar environment -- > Microsoft RDP client on a Mac connecting to xrdp 0.9.x on FreeBSD 11.2 > -- are you able to share your xrdp.ini and startwm.sh files? Have you tried to make ~/.xsession file with: #! /bin/sh startxfce4
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b30465dd-4a7e-a9fc-6bf1-ae41b8da3a93>