Date: Wed, 8 May 2019 16:00:52 -0600 From: "Janky Jay, III" <jankyj@unfs.us> To: Koichiro Iwao <meta@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: net/xrdp: Issue(s) with Channels/Clipboard. Message-ID: <18ef06f5-076b-9941-e951-4eb3c47570b5@unfs.us> In-Reply-To: <0c964258-8f24-74a4-b592-d4132128bdf0@unfs.us> References: <f95c8c0d-ce65-f98f-c65e-f7a6b98d3391@unfs.us> <20190217013706.nzqj3zlhmgtusbnl@icepick.vmeta.jp> <0c964258-8f24-74a4-b592-d4132128bdf0@unfs.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Koichiro, =C2=A0=C2=A0=C2=A0 Is there any update to this? I've since upgraded both = systems to FBSD 12.0-RELEASE-p3 and there have also been (I think) two (2) xrdp port/pkg updates as well but the problem still remains the same. Connections to chansrv work 100% of the time on one system and 0% of the time on the other. =C2=A0=C2=A0=C2=A0 Also, can you please provide a link to the GH post/rep= ort that you created? I'd like to take a look and follow that as well if I can. Thanks again! Regards, Janky Jay, III On 2019-02-17 12:23, Janky Jay, III wrote: > Hello Meta, > > On 2/16/19 6:37 PM, Koichiro Iwao wrote: >> On Fri, Feb 15, 2019 at 11:31:36AM -0700, Janky Jay, III wrote: >>> This also causes the connection to take 16 seconds to open XFCE4 onc= e >>> it finally gives up on channels. I see 4 errors so I'm guessing there= 's >>> a 4 second timeout between attempts. Something similar to the >>> issue/recommendation reported at >>> https://github.com/neutrinolabs/xrdp/issues/1288. I've tried the >>> recommended disallowing of channels to see if it would connect faster= >>> but it does nothing. Still attempts the connections to "chansrv" and >>> takes 16 seconds. >> I don't think that is recommended in the upstream issue. Just he repor= ter >> tried as workaround. Who recommended? As commented in the ticket, disa= bling >> all channels don't stop connecting to chansrv. That's why *not to >> connect when all channels disabled* feature is suggedted. >> =20 > =C2=A0=C2=A0=C2=A0 I should have worded that differently. I suppose "re= commended" was > incorrect. It was just a thought to see whether or not > disable/re-enabling might give me more insight into what was happening > via the logs (I tried adding the DEBUG log line to sesman.ini as well > but there was no relevant information). > >> I know some people have the same issue and already recoeded to upstrea= m >> GH issue. Hang tight. If I need to know more detail of reproduction, >> I might ask you help. >> >> I also reproduce the issue but not 100%. >> > =C2=A0=C2=A0=C2=A0 Sounds good! I can reproduce 100% of the time on one= system right > now so if there is anything I can do to help, I will certainly do that.= > Thank you! > > Regards, > Janky Jay, III > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18ef06f5-076b-9941-e951-4eb3c47570b5>