Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Aug 2018 08:48:38 -0700
From:      David Newman <dnewman@networktest.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: xrdp configuration and xfce4
Message-ID:  <f46c4d3a-9e9a-3e17-ceac-a28eb706045d@networktest.com>
In-Reply-To: <0101016521032eb2-f262b8e9-b49d-4698-b7fa-b164846438d8-000000@us-west-2.amazonses.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> <010101651cc2eaf1-3b1f8145-18bd-4665-bdf9-767470f85a3d-000000@us-west-2.amazonses.com> <ae825563-6242-d7d9-9458-3003fde1b4f3@networktest.com> <0101016521032eb2-f262b8e9-b49d-4698-b7fa-b164846438d8-000000@us-west-2.amazonses.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 8/9/18 4:26 PM, Koichiro IWAO wrote:
>=20
>>> Again, in xrdp context, ~/.xinitrc or ~/.xsession doesn't affect. For=
get
>>> it and
>>> see /usr/local/etc/xrdp/startwm.sh or ~/startwm.sh.
>>
>> Partial success! xfce4 now starts automatically with a local startwm.s=
h
>> file.
>=20
> Which did you try? ~/startwm.sh?=20

Yes. xfce4 starts up with ~/startwm.sh in place, using the contents and
permissions you described.

> If you got success with ~/startwm.sh,
> there might be a bug of xrdp. Some people reported similar issue to you=
rs.

OK. That is a separate issue, but a big one for me, as it makes remote
management difficult.

Where is the appropriate place to report the clipboard issue?

> Let me break down the issue and help us improve xrdp before looking at
> clipboard issue.
>=20
> 1. remove ~/startwm.sh
> 2. confirm /usr/local/etc/xrdp/startwm.sh starts startxfce4
> 3. login via xrdp
> 4. you'll see xterm
> 5. see /var/log/xrdp-sesman.log
> 6. you'll see the log like this
>=20
> [20180710-23:08:24] [CORE ] waiting for window manager (pid 41266) to e=
xit
> [20180710-23:08:24] [CORE ] error starting default wm for user meta -
> pid 41266
> [20180710-23:08:25] [DEBUG] errno: 2, description: No such file or
> directory
> [20180710-23:08:25] [DEBUG] execlp3 parameter list:
> [20180710-23:08:25] [DEBUG]=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 argv[0] =3D startwm.sh
> [20180710-23:08:25] [DEBUG]=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 argv[1] =3D startwm.sh
>=20
> If you see the log like this, xrdp is failing to find
> /usr/local/etc/xrdp/startwm.sh.
> If you specify the full path to startwm.sh in sesman.ini, it should
> work. Try it.
> Don't forget to restart xrdp-sesman after you edited sesman.ini.
>=20
> ```
> DefaultWindowManager=3D/usr/local/etc/xrdp/startwm.sh
> ```
>=20
> Thank you for your cooperation.

Thank YOU, Iwao-san, for your help with this.

The behavior is exactly as you described, but only if we replace the
startwm.sh script supplied with the pkg with the two-line version you
suggested:

#!/bin/sh
startxfce4

The startwm.sh script supplied with the package has three different
cases for Linux distributions (lines 66-88) but nothing for xfce4 on
FreeBSD.

Thanks again for your help with the startup issue, and in advance for
pointers on debugging the clipboard issue.

dn




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?f46c4d3a-9e9a-3e17-ceac-a28eb706045d>