remote desktop screen sharing does not work

Bug #1995201 reported by Wolfgang Fahl
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
remmina (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

https://www.omgubuntu.co.uk/2022/06/use-ipad-as-second-monitor-ubuntu-22-04 and

https://www.reddit.com/r/gnome/comments/uz5as7/gnome_has_made_it_super_simple_to_extend_your/

https://ubuntuhandbook.org/index.php/2022/04/ubuntu-22-04-remote-desktop-control/

advertise screen sharing via rdp on Ubuntu 22.04 and I hoped to be able to use it.

Unfortunately on multiple machines i was not able to get it working and it seems for various reasons. On the other hand i couldn't find proper bug reports yet.

There are quite a few stackexhange questons out there related to 22.04 remote desktop sharing such as
* https://askubuntu.com/questions/1407444/ubuntu-22-04-remote-deskop-headless
* https://askubuntu.com/questions/1403943/22-04-remote-desktop-sharing-authentication-password-changes-every-reboot
* https://askubuntu.com/questions/1406292/remote-desktop-via-vnc-is-black-mouse-keyboard-works
* https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl
* https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl

I'd expect that the remote desktop sharing works out of the box and needs no further configuration and fiddling. Especially it should work if already logged in. There seem to be so many parts involved in this that
there is IMHO a need to have a look at this from an overarching enduser viewpoint instead of assuming that users have to take a sysadmin course to use Ubuntu 22.04 LTS remote desktop sharing. After all this is version 22 of the system and not trying to implement bug #1 of Ubuntu.

Let's start with the machine where i think things are getting close to working and the message in /var/log/syslog is:
```
Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Timed out waiting for X server on display 11 to startup
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session started successfully for user wf on display 11
Oct 30 11:02:57 capri xrdp-sesman[102029]: [INFO ] Starting the xrdp channel server for display 11
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session in progress on display 11, waiting until the window manager (pid 101543) exits to end the session
Oct 30 11:02:57 capri xrdp-sesman[101543]: [WARN ] Timed out waiting for X server on display 11 to startup
Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] There is no X server active on display 11
Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] A fatal error has occured attempting to start the window manager on display 11, aborting connection
Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Window manager (pid 101543, display 11) exited quickly (0 secs). This could indicate a window manager config problem
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Calling auth_stop_session and auth_end from pid 101542
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating X server (pid 101544) on display 11
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating the xrdp channel server (pid 102029) on display 11
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] X server on display 11 (pid 101544) returned exit code 1 and signal number 0
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] xrdp channel server for display 11 (pid 102029) exit code 0 and signal number 0
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] cleanup_sockets:
Oct 30 11:02:57 capri xrdp-sesman[1287]: [INFO ] ++ terminated session: username wf, display :11.0, session_pid 101542, ip ::ffff:2.0.0.10:59651 - socket: 12
```

And i get a black screen in the rdp client on my mac os machine from which i try to connect with Microsoft Remote Desktop

Tags: bot-comment
description: updated
description: updated
Revision history for this message
Wolfgang Fahl (wf-bitplan) wrote :

https://c-nergy.be/blog/?p=13708 shows one of the problems.
Even whether install xrdp or not is necessary is not explained properly.

On one of my machines i seem to get more mileage if i install xrdp while the other seemed to have no need for the installation.

Revision history for this message
Wolfgang Fahl (wf-bitplan) wrote :
Revision history for this message
Wolfgang Fahl (wf-bitplan) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1995201/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → remmina (Ubuntu)
Revision history for this message
Wolfgang Fahl (wf-bitplan) wrote :

This bug is indeed overlapping multiple packages which i think should not be an obstacle to improving ubuntu.

Revision history for this message
Wolfgang Fahl (wf-bitplan) wrote :

Out of three Ubuntu 22.04 LTS target machines i got remote desktop working so far on just one.

I had to switch the configuration to wayland as explained in https://linuxconfig.org/how-to-enable-disable-wayland-on-ubuntu-22-04-desktop and fix the login keyring by removing it as described in https://forums.linuxmint.com/viewtopic.php?t=348117

This issue is about avoiding such strange procedures and get a working remote desktop experience "out of the box".

Revision history for this message
Pascal Nowack (pnowack) wrote (last edit ):

Screen sharing with RDP was indeed advertised with the Ubuntu 22.04 release, because it is part of GNOME 42 (see the release notes).
This uses the RDP backend in GNOME Remote Desktop (g-r-d) and has nothing to do with xrdp, which you apparently installed additionally.

With the extra installation of xrdp, you basically fucked up your system, since both g-r-d and xrdp are RDP servers and they are fighting over the RDP port (3389).
Screen sharing with g-r-d is literally a one-click-experience, meaning it just needs to be turned on in g-c-c. g-r-d is also not limited to x11 and works in Wayland too.

What you did here was mixing g-r-d with xrdp (same with the links you posted) and blaming this on Ubuntu. This is a classic example of a PICNIC issue (Problem In Chair, Not In Computer).

I suggest you to look up what the RDP protocol is (you apparently don't know (protocol vs implementation(s))), and look into the respective Ubuntu help, as it tells how to connect to an RDP server (and especially g-r-d) with an RDP client.

Changed in remmina (Ubuntu):
status: New → Invalid
Revision history for this message
Wolfgang Fahl (wf-bitplan) wrote :

Thank you for your reply. Indeed i think the documentation needs much improvement.

The reason i tried xrdp was that the "it just needs to be turned on in g-c-c" did not work. https://askubuntu.com/questions/1422263/rdp-on-ubuntu-desktop-22-04 was one of the hint i followed which led into the wrong direction. In the meantime i got things working on 2 of my 4 systems see https://askubuntu.com/a/1438504/129227 and i explicitly mentioned that the links i followed might be misleading (which is part of the problem).

I might not be alone in misconfiguring the system due to it not working out of the box so it's probably better to change the status of this bug and do something about it instead of getting more frustrated people out there.

Still two of my systems do not work properly and the messages from /var/syslog and other logs IMHO need much improvement in giving hints what to do.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.