RDP connections don't work and consume all RAM with version 3.30.0
Boxes 3.30 is in theory capable to connect to remote windows machines using the rdp protocol. However, when I try to connect to any of the windows machines in our network (which all work fine with both remmina/freeRDP and rdesktop), I get the "I'm doing something circle" in the boxes window and tons of console output:
[06:38:20:370] [8489:8593] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[06:38:20:370] [8489:8593] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
[06:38:20:386] [8489:8593] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_LOGON_FAILURE [0x00020014]
[06:38:20:386] [8489:8593] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[06:38:20:386] [8489:8593] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
[06:38:20:403] [8489:8593] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_LOGON_FAILURE [0x00020014]
[06:38:20:403] [8489:8593] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[06:38:20:403] [8489:8593] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
[06:38:20:421] [8489:8593] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_LOGON_FAILURE [0x00020014]
[06:38:20:421] [8489:8593] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[06:38:20:421] [8489:8593] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
This repeats over and over again.
On these machines, I have to logon with my username and password. I've tried with username and domain\username but the issue is the same.
What's even more critical is that boxes then starts up consuming all my RAM (16GB) within minutes which results in a complete system lockup if I cannot manage to kill it beforehand.
I'm attaching the journalctl log the seconds before all memory has been consumed and I had to do a hard shutdown.