xrdp with KDE plasma session: kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__10) failed: : Connection refused Description of problem: I'm trying to use my (KDE plasma) fedora from a win10 machine with xrdp. Version-Release number of selected component (if applicable): plasma-workspace-5.6.5-2.fc24.x86_64 How reproducible: Always Steps to Reproduce: I basically followed https://gist.github.com/bcambl/ff17eae67863eda34c24 . From http://bullcreekstudio.com/commentary/start-remote-xrdp-session-mate-debi... it seems to be clear that starting a KDE session is only a matter of $ ls -l ~/.Xclients -rwx--x--x. 1 tpasch tpasch 9 12. Jul 12:53 .Xclients $ cat ~/.Xclients startkde However, when logging in I see a KDE load screen, but the connection is aborted before the real plasma desktop. Actual results: On the remote machine, I find the following in ~/.xsession-errors: $ cat .xsession-errors startkde: Starting up... kdeinit5: Communication error with launcher. Exiting! kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__10) failed: : Connection refused startkde: Shutting down... kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__10) failed: : Connection refused Error: Can not contact kdeinit5! startkde: Done. kwin_x11: FATAL ERROR while trying to open display :10.0 Expected results: KDE session should start. Additional info: In the meantime, I escaped to the following work-around: * dnf install @xfce-desktop * Use 'startxfce4' instead of 'startkde' in ~/.Xclients With this changes, the problem disappears (but I now log in into a xfce desktop, of course), i.e. I could log in with a remote rdp client. Because of this, I still thinks it is a kind of KDE issue. Perhaps selinux has its finger in the pie?
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.