My apologies for this arbitrary addition, but it appears this no longer works in the latest release of Solus 4.0 Fortitude. On attempting to remotely log into the machine through RDP after following the above steps yields the following in the journal:

Aug 01 17:52:21 dwt-lenovo-solus xrdp[2241]: (2241)(140642634756864)[INFO ] xrdp_wm_log_msg: login successful for display 10
Aug 01 17:52:21 dwt-lenovo-solus xrdp-sesman[2220]: (2220)(140305131460416)[DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
Aug 01 17:52:21 dwt-lenovo-solus xrdp-sesman[2242]: (2242)(140305131460416)[INFO ] calling auth_start_session from pid 2242
Aug 01 17:52:21 dwt-lenovo-solus xrdp[2241]: (2241)(140642634756864)[DEBUG] xrdp_wm_log_msg: started connecting
Aug 01 17:52:21 dwt-lenovo-solus xrdp-sesman[2242]: pam_unix(xrdp-sesman:session): session opened for user dave by (uid=0)
Aug 01 17:52:21 dwt-lenovo-solus xrdp-sesman[2242]: gkr-pam: unable to locate daemon control file
Aug 01 17:52:21 dwt-lenovo-solus systemd-logind[620]: New session 3 of user dave.
Aug 01 17:52:21 dwt-lenovo-solus systemd[1]: Started Session 3 of user dave.
Aug 01 17:52:21 dwt-lenovo-solus xrdp-sesman[2242]: (2242)(140305131460416)[DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
Aug 01 17:52:21 dwt-lenovo-solus xrdp-sesman[2242]: (2242)(140305131460416)[DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
Aug 01 17:52:21 dwt-lenovo-solus xrdp-sesman[2249]: (2249)(140305131460416)[INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
Aug 01 17:52:21 dwt-lenovo-solus dbus-daemon[848]: [session uid=1000 pid=848] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.56' (uid=1000 pid=1068>
Aug 01 17:52:21 dwt-lenovo-solus systemd[836]: Starting Tracker metadata database store and lookup manager...
Aug 01 17:52:21 dwt-lenovo-solus dbus-daemon[848]: [session uid=1000 pid=848] Successfully activated service 'org.freedesktop.Tracker1'
Aug 01 17:52:21 dwt-lenovo-solus systemd[836]: Started Tracker metadata database store and lookup manager.
Aug 01 17:52:22 dwt-lenovo-solus xrdp-sesman[2242]: (2242)(140305131460416)[CORE ] waiting for window manager (pid 2248) to exit
Aug 01 17:52:22 dwt-lenovo-solus xrdp-sesman[2242]: (2242)(140305131460416)[CORE ] window manager (pid 2248) did exit, cleaning up session

It's the messages such as gkr-pam: unable to locate daemon control file which appear to be killing the login.

I sincerely apologise if this is in the incorrect place and please correct me if it is; I just wanted to point this out.

Thanks.

@davewthompson It still works, I use it every day. A few things:

• Package and install using this diff, not the source or from the repository. Otherwise, install from repository and manually follow the guide I posted to Reddit here
• Make sure you have xorgxrdp installed as well
• I removed it from this diff, but make sure you create the Xwrapper.config at /etc/X11/Xwrapper.config, containing allowed_users=anybody
• If you have remmina installed, and are using this diff, it will pickup the .desktop file installed by that package instead of budgie.desktop and fail to launch

I followed all the steps mentioned in the Reddit guide or in your above post @tarkah, but it is still failing for me. Could you please elaborate on your last point about the .desktop file?

I do have Remmina installed (on the client only), and when I try to connect to the server with it, it seems to authenticate correctly (no error prompt), but will end up on a black screen. "Relax Order Checks" and "Glyph Cache" are checked.

If I try to connect using xfreerdp with xfreerdp /w:1024 /v:solus-manips.local /u:mathieu /relax-order-checks +glyph-cache, I do get a login GUI, but then end up on a blue screen with no possible interaction.

I suppose it fails to start the DE in both cases, but I am not sure what I am missing if it does work for you.

@Matf Were you ever able to get this working? Sorry for my delayed response. My reference to the .desktop file was related to the various files installed to /usr/share/xsessions/ for each DE you may have installed on your machine. If you are using this diff with my changes to the startwm.sh file, it tries to extract the Exec= command from the first file in that folder and exec that (most people will usually only have a single DE installed so it will just pick it up from that file and this package will work dynamically regardless of DE being used). When you install Remmina on your machine, it apparently installs a .desktop file to that path, and unfortunately is picked up before the budgie-desktop.desktop. If you are using budgie, just hard code exec /usr/bin/budgie-desktop into your startwm.sh file.

If that's not the issue, no idea what else it could be. I have had xrdp working ever since 4.0 was released without any issues, outside the Reminna issue just mentioned. I mostly connect from Windows 10, maybe try a windows client just to rule out it isn't a client issue?

That's definitely cleaner and simpler, I think we should take that route. Though it's more of an edge case, how would file collisions be handled if someone had multiple DE's and tried to install the "budgie" and "mate" integration packages? There's no concept of mutually exclusive packages, right?

Overall, it seems the best thing would be to have a new article published to the help center to cover setup and hazards for users wanting to use XRDP. If you'd prefer the integration package approach, I can work on creating those and eventually submit a PR to the help docs for a new page aligned with this approach.

@tarkah I'd rather have conflicting packages that only allow one DE to support remote access than a script that breaks as soon as two or more DEs are installed at the same time. Ortherwise, we still need a better approach than has been presented so far.

I see how patterns would work to have another package just ship startwm.sh. But how would this work with 4 different packages shipping the same file / pattern?

No worries! I'll go ahead and revive D8667, adding a conflicts section. And then submit a few more for Mate, Gnome and Plasma.

I've added the integration package for Plasma: D8868

Mate Integration package D8869

Gnome Integration package D8870

Sweet, got them all added. Once you give this the green light, I'll go ahead and submit a PR for the help center docs. Should be as simple as installing the correct integration package and adding the /etc/X11/Xwrapper.config line allowed_users=anybody