Now that's something I did not expect to work, neverthrless it worked. Thank you!
pt., 20 wrz 2019, 12:12 użytkownik Bernhard Miklautz < bernhard.mikla...@shacknet.at> napisał: > Hi Michał, > > On Tue, Sep 03, 2019 at 04:43:53PM +0200, Michał Romaszko via > FreeRDP-devel wrote: > > On Windows, I was using mstsc command and it worked flawlessly, but > since I > > aim for it to be usable on Linux as well, I've started to look for an > > alternative and that's how I stumbled upon FreeRDP. I've downloaded > > wfreerdp and after initial tests it turned out that the connection is not > > really being established while on a locked screen and I end up with > > following errors: > > > > [ERROR][com.freerdp.channels.cliprdr.client] - MonitorReady failed with > > error 1359! > > [ERROR][com.freerdp.channels.cliprdr.client] - > > cliprdr_process_monitor_ready failed with error 1359! > > [ERROR][com.freerdp.channels.cliprdr.client] - cliprdr_order_recv failed > > with error 1359! > > [ERROR][com.freerdp.core] - cliprdr_virtual_channel_client_thread > reported > > an error. Error was 1359 > > [ERROR][com.freerdp.core] - checkChannelErrorEvent() failed - 0 > > > > That leads me to following questions: > > - is such thing possible, but bugged or is it something that FreeRDP was > > not designed for? > > - if it is possible and should work, what should I do to make it work? > the errors are clipboard related. Did you try with clipboard disabled > (parameter -clipboard)? > > Best regards, > Bernhard > _______________________________________________ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
