Markus Koller wrote, On 07/09/2010 02:46 PM:
> On Fri, Jul 09, 2010 at 02:27:20PM +0200, Mads Kiilerich wrote:
>> AFAICS xfreerdp doesn't crash. It is redirected to some other
>> server, but it can't connect to whatever it is redirected to.
> Hmm okay, I'll have to take a closer look at my configuration, I just
> remembered that I'm using "token redirection" which I think was required
> for RD Gateway to work correctly with the Connection Broker.
> There's also IP address redirection which might work with xfreerdp.
I have implemented the connection broker functionality but know nothing
about TS/RD, so please let me know exactly what doesn't work.
>>> I've attached the full output and also an strace.
>> No attachments arrived here. Perhaps because the stupid SF list ate
>> it. Please forward them directly to me.
> Actually I just forgot to attach them, here they are...
Notice that the strace doesn't follow the thread where all the
interesting things happens. I'm however not sure it would help that
much. Could you try to configure with --with-debug instead?
The debugging is further complicated by the plugins/channels and other
command line options you use. Can you try to reproduce without - and
perhaps find out what triggers the problem?
(It seems a bit like the remote server just hangs up even before getting
to the session broker phase, probably because it considers some package
> It would be great if you could use a "proper" bug tracker ;-)
I agree. But I think that without a formalized workflow for managing
issues in a bug tracker then plain communication on a proper mailing
list is better.