Description of problem: KRDC does not connect to Windows RDP servers. Version-Release number of selected component (if applicable): - krdc-17.12.1-1.fc27 - freerdp-39.20180314gitf8baeb7.fc27 - Steps to Reproduce: 1. Try xfreerdp on the command line 2. Try KRDC using rdp:// to the same host Actual results: xfreerdp can connect to the host, but KRDC can not. It flickers briefly, but there are no error messages. So far, I can only reproduce this problem on FreeIPA clients.
see also bug #1537040 and bug #1537082 and update, https://bodhi.fedoraproject.org/updates/FEDORA-2018-f754a46985 Feel free to re-open if the freerpd update does not fix your issue. *** This bug has been marked as a duplicate of bug 1537040 ***
This was not really a duplicate. The other bugs were specifically for patched Windows servers or GSSAPI authentication. These are fixed by the newer versions. This is something new though. I just found out the reason. On all the profiles where KRDC did not connect, I had put something in the 'Share Media' field for the host configuration. Share Media: /run/media This was done in order to connect USB storage. When such storage is not present, the path does not exist, KRDC 'flickers' briefly and does not connect. Previously, KRDC did not mind and USB storage could be connected afterwards. What makes these type of problems hard to find is that KRDC does not throw errors, but just flickers, leaving the user to guess what was wrong.
ok, re-opening, adjusting summary per your description
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.