Bug 1820270 - xrdp with KDE plasma session: kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__10) failed: : Connection refused
Summary: xrdp with KDE plasma session: kdeinit5_wrapper: Warning: connect(/run/user/10...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xrdp
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Itamar Reis Peixoto
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-02 16:02 UTC by aannoaanno
Modified: 2020-11-24 16:40 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-24 16:40:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description aannoaanno 2020-04-02 16:02:12 UTC
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 
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments
kdeinit5: Communication error with launcher. Exiting!
OpenGL vendor string:                   VMware, Inc.
OpenGL renderer string:                 llvmpipe (LLVM 9.0, 256 bits)
OpenGL version string:                  3.1 Mesa 19.2.8
OpenGL shading language version string: 1.40
Driver:                                 LLVMpipe
GPU class:                              Unknown
OpenGL version:                         3.1
GLSL version:                           1.40
Mesa version:                           19.2.8
X server version:                       1.20.6
Linux kernel version:                   5.5.11
Requires strict binding:                yes
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no


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 is a bug report against Fedora 31. The first time I reported it against Fedora 24 (!!!): https://bugzilla.redhat.com/show_bug.cgi?id=1356546

Comment 1 Bojan Smojver 2020-04-03 09:16:28 UTC
It's possible selinux is involved. Check that xrdp-selinux package is installed. Or turn off enforcement with setenforce 0. Then check audit log for denials.

Comment 2 Ben Cotton 2020-11-03 16:33:38 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-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 '31'.

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 31 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.

Comment 3 Ben Cotton 2020-11-24 16:40:23 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.


Note You need to log in before you can comment on or make changes to this bug.