Description of problem: Freerdp does not connect to Weston with RDP backend. Version-Release number of selected component (if applicable): freerdp-2.0.0-50.20190517gitb907324.fc30.x86_64 How reproducible: xfreerdp -v:192.168.10.203 Steps to Reproduce: 1. Weston with RDP backend on PC with IP 192.168.10.203 2. Try to connect with FreeRDP: xfreerdp -v:192.168.10.203 3. Disappointment Actual results: [zim@marcel-nb-toradex-int ~]$ xfreerdp -v:192.168.10.203 [11:27:04:231] [28943:28944] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr [11:27:04:231] [28943:28944] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd [11:27:04:231] [28943:28944] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [11:27:04:231] [28943:28944] [INFO][com.freerdp.client.x11] - No user name set. - Using login name: zim [11:27:04:287] [28943:28944] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32 [11:27:04:287] [28943:28944] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16 [11:27:04:308] [28943:28944] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem [11:27:04:309] [28943:28954] [INFO][com.freerdp.channels.rdpsnd.client] - Loaded fake backend for rdpsnd [11:27:04:327] [28943:28944] [ERROR][com.freerdp.core.rdp] - rdp_recv_tpkt_pdu: rdp_recv_deactivate_all() fail [11:27:04:327] [28943:28944] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 [11:27:04:327] [28943:28944] [ERROR][com.freerdp.core] - freerdp_check_fds() failed - 0 [11:27:04:327] [28943:28944] [INFO][com.freerdp.client.common] - Network disconnect! [11:27:04:327] [28943:28944] [ERROR][com.freerdp.client.x11] - Failed to check FreeRDP file descriptor And no RDP session! Expected results: E.g. with hand built 2.0.0-rc4. [zim@marcel-nb-toradex-int FreeRDP.git]$ ./client/X11/xfreerdp -v:192.168.10.203 [11:29:21:214] [3679:3680] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [11:29:21:214] [3679:3680] [INFO][com.freerdp.client.x11] - No user name set. - Using login name: zim [11:29:21:263] [3679:3680] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32 [11:29:21:263] [3679:3680] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16 [11:29:21:287] [3679:3680] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem And working RDP session, hurray! Additional info: Git bisect points to heartbeat feature being at fault. [zim@marcel-nb-toradex-int FreeRDP.git]$ git bisect good 753b9c7ce9af549995d691425f8c50c7dcceea85 is the first bad commit commit 753b9c7ce9af549995d691425f8c50c7dcceea85 Author: Armin Novak <armin.novak> Date: Fri Dec 14 12:40:18 2018 +0100 Enable server heartbeat PDU by default. :040000 040000 6e1f801c34c6424cce0eff9fc0764add934be74b 8ce408e295a296cdb317f8d4360b3e9e589a24d4 M client :040000 040000 8134654205f856b935bcb8407c7d680fd38959ed 5b61f4d50405ee6d8b479233a0ed1ff75be875bc M libfreerdp
Seems to be related to the following: Client does not handle DesktopResize if heartbeat is enabled #5437 https://github.com/FreeRDP/FreeRDP/issues/5437
FEDORA-2020-2404c9ff3b has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2404c9ff3b
freerdp-2.0.0-56.20200207git245fc60.fc31, guacamole-server-1.1.0-5.fc31, remmina-1.3.10-1.fc31, vinagre-3.22.0-17.fc31, weston-7.0.0-3.fc31, wlroots-0.6.0-3.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-483cbdf643
freerdp-2.0.0-56.20200207git245fc60.fc30, guacamole-server-1.1.0-5.fc30, remmina-1.3.10-1.fc30, vinagre-3.22.0-16.fc30, weston-6.0.1-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-2404c9ff3b
freerdp-2.0.0-56.20200207git245fc60.fc31, guacamole-server-1.1.0-5.fc31, remmina-1.3.10-1.fc31, vinagre-3.22.0-17.fc31, weston-7.0.0-3.fc31, wlroots-0.6.0-3.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
freerdp-2.0.0-56.20200207git245fc60.fc30, guacamole-server-1.1.0-5.fc30, remmina-1.3.10-1.fc30, vinagre-3.22.0-16.fc30, weston-6.0.1-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Unfortunately, the issue remains even with freerdp-2.0.0-56.20200207git245fc60.fc31.x86_64. Only manually disabling -heartbeat makes it work. Unfortunately, none of them graphical front-ends will do that so none of them works! [zim@marcel-nb-toradex-int ~]$ xfreerdp /v:192.168.10.151 [17:01:02:822] [135688:135689] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state [17:01:02:822] [135688:135689] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr [17:01:02:826] [135688:135689] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd [17:01:02:826] [135688:135689] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [17:01:02:826] [135688:135689] [INFO][com.freerdp.client.x11] - No user name set. - Using login name: zim [17:01:02:138] [135688:135689] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized [17:01:02:140] [135688:135689] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state [17:01:02:140] [135688:135689] [INFO][com.freerdp.core] - freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state [17:01:02:194] [135688:135689] [WARN][com.freerdp.crypto] - Certificate verification failure 'self signed certificate (18)' at stack position 0 [17:01:02:194] [135688:135689] [WARN][com.freerdp.crypto] - C = CH, ST = Luzern, L = Luzern, O = Toradex, CN = (none) [17:01:02:194] [135688:135689] [ERROR][com.freerdp.crypto] - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [17:01:02:194] [135688:135689] [ERROR][com.freerdp.crypto] - @ WARNING: CERTIFICATE NAME MISMATCH! @ [17:01:02:194] [135688:135689] [ERROR][com.freerdp.crypto] - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [17:01:02:194] [135688:135689] [ERROR][com.freerdp.crypto] - The hostname used for this connection (192.168.10.151:3389) [17:01:02:194] [135688:135689] [ERROR][com.freerdp.crypto] - does not match the name given in the certificate: [17:01:02:194] [135688:135689] [ERROR][com.freerdp.crypto] - Common Name (CN): [17:01:02:194] [135688:135689] [ERROR][com.freerdp.crypto] - (none) [17:01:02:194] [135688:135689] [ERROR][com.freerdp.crypto] - A valid certificate for the wrong name should NOT be trusted! Certificate details for 192.168.10.151:3389 (RDP-Server): Common Name: (none) Subject: C = CH, ST = Luzern, L = Luzern, O = Toradex, CN = (none) Issuer: C = CH, ST = Luzern, L = Luzern, O = Toradex, CN = (none) Thumbprint: 5f:28:09:5a:78:d7:7b:bb:4b:46:06:14:61:37:60:cc:1c:94:d6:86 The above X.509 certificate could not be verified, possibly because you do not have the CA certificate in your certificate store, or the certificate has expired. Please look at the OpenSSL documentation on how to add a private CA to the store. Do you trust the above certificate? (Y/T/N) y [17:01:05:580] [135688:135689] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32 [17:01:05:580] [135688:135689] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16 [17:01:05:624] [135688:135689] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem [17:01:05:626] [135688:135689] [INFO][com.freerdp.channels.rdpsnd.client] - Loaded fake backend for rdpsnd [17:01:05:627] [135688:135689] [ERROR][com.freerdp.core.rdp] - rdp_recv_tpkt_pdu: rdp_recv_deactivate_all() fail [17:01:05:627] [135688:135689] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 [17:01:05:627] [135688:135689] [ERROR][com.freerdp.core] - freerdp_check_fds() failed - 0 [17:01:05:627] [135688:135689] [INFO][com.freerdp.client.common] - Network disconnect! [17:01:05:627] [135688:135689] [ERROR][com.freerdp.client.x11] - Failed to check FreeRDP file descriptor
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.