I am on a Windows machine VPN'ed into an internal network, then RDP'd into my Kubuntu work machine. I can copy+paste into a terminal just fine using Ctrl+Shift C and Ctrl+Shift V. However, when I SSH into a Centos server, both stop working. Not only that, but right clicking the window and clicking "Copy" also doesn't work. Ideas?

Running RDP on my Win10 box against my Raspbian distro on an R4 with xrdp. My keyboard layout was not corresponding to my Norwegian keyboard. I followed the advice in https://unix.stackexchange.com/questions/99085/save-setxkbmap-settings to get the keyboard (Norwegian). setxkbmap no in a terminal fixes it. I also followed the advice and added that to ~/profile. Problem is my keyboard layout seems to be reset when the connection is broken (for what ever reason, network glitch, rebooting router after fiddling with some settings etc) or simply being inactive for a while even without the connection being broken. Any takers? Quick question. What's the difference between setxkbmap no and setxkbmap -layout no? Both seems to do the trick but both suffers from the same lack of permanency.

I have a Ubuntu installation where multiple users have desktop sessions at the same time, some over XRDP and another directly on VT7. How can I find out which of these users initiated a shutdown or reboot, e.g by the XRDP mechanism or by the systray popup menu? For example: Like in Windows system in event viewer I can see which user did restart or shutdown by that the user click on button in each session even in RDP so the same I search to do for Linux system None of the users will use the command-line to perform shutdown or restart.

Does there is any possibility to have this combination? Podman container with: - Alpine Linux - Wayland - xRDP with multiuser support - any window compositor I have found there are some limitation of multiuser support in Gnome-remote-desktop. Should I use xRDP with xwayland as only way? Does there has been anyone successful with Wayland over RDP (ideally without X interconnection)? Thanks for advice.

I'm trying to use xrdp to RDP from my windows machine to my linux box(specifically xorg xrdp as mentioned in the Arch Linux wiki for setting up RDP). I'm having an issue with what I believe to be my desktop environment (xfce4) causing my RDP connection to be terminated. I have provided the snippets from XRDP and XRDP-Sesman below. I ssh'd in and decided to see what was happening on the linux box whenever I tried to connect with my Windows RDP client. I do get a login box, and the login seems to succeed. I have tried a lot of different solutions involving making sure: - .xsessions features the line xfce4-session - Xwrapper is setup to allow any user to connect - that my .xinitrc executes startxfce4 - set a keep alive timer within the .ini file **xrdp.log** [20190730-18:33:02] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20190730-18:33:02] [ERROR] xrdp_mm_connect_chansrv: error in trans_connect chan [20190730-18:33:02] [DEBUG] Closed socket 18 (AF_INET 127.0.0.1:51792) [20190730-18:33:02] [DEBUG] Closed socket 12 (AF_INET 10.64.5.120:3389) [20190730-18:33:02] [DEBUG] xrdp_mm_module_cleanup [20190730-18:33:02] [DEBUG] Closed socket 19 (AF_UNIX) [20190730-18:33:02] [DEBUG] Closed socket 20 (AF_UNIX) [20190730-18:33:23] [INFO ] Socket 12: AF_INET connection received from 10.64.27.2 port 33394 [20190730-18:33:23] [DEBUG] Closed socket 12 (AF_INET 10.64.5.120:3389) [20190730-18:33:23] [DEBUG] Closed socket 11 (AF_INET 0.0.0.0:3389) [20190730-18:33:23] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem [20190730-18:33:23] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem [20190730-18:33:23] [DEBUG] TLSv1.2 enabled [20190730-18:33:23] [DEBUG] TLSv1.1 enabled [20190730-18:33:23] [DEBUG] TLSv1 enabled [20190730-18:33:23] [DEBUG] Security layer: requested 11, selected 1 [20190730-18:33:23] [DEBUG] Closed socket 12 (AF_INET 10.64.5.120:3389) [20190730-18:33:25] [INFO ] Socket 12: AF_INET connection received from 10.64.27.2 port 45509 [20190730-18:33:25] [DEBUG] Closed socket 12 (AF_INET 10.64.5.120:3389) [20190730-18:33:25] [DEBUG] Closed socket 11 (AF_INET 0.0.0.0:3389) [20190730-18:33:25] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem [20190730-18:33:25] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem [20190730-18:33:25] [DEBUG] TLSv1.2 enabled [20190730-18:33:25] [DEBUG] TLSv1.1 enabled [20190730-18:33:25] [DEBUG] TLSv1 enabled [20190730-18:33:25] [DEBUG] Security layer: requested 11, selected 1 [20190730-18:33:25] [INFO ] connected client computer name: DESKTOP-0C7KOCP [20190730-18:33:25] [INFO ] adding channel item name rdpdr chan_id 1004 flags 0x80800000 [20190730-18:33:25] [INFO ] adding channel item name rdpsnd chan_id 1005 flags 0xc0000000 [20190730-18:33:25] [INFO ] adding channel item name cliprdr chan_id 1006 flags 0xc0a00000 [20190730-18:33:25] [INFO ] adding channel item name drdynvc chan_id 1007 flags 0xc0800000 [20190730-18:33:25] [INFO ] TLS connection established from 10.64.27.2 port 45509: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 [20190730-18:33:25] [DEBUG] xrdp_00002b80_wm_login_mode_event_00000001 [20190730-18:33:25] [INFO ] Loading keymap file /etc/xrdp/km-00000809.ini [20190730-18:33:25] [WARN ] local keymap file for 0x00000809 found and doesn't match built in keymap, using local keymap file [20190730-18:33:31] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350 [20190730-18:33:31] [INFO ] xrdp_wm_log_msg: sesman connect ok [20190730-18:33:31] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait... [20190730-18:33:31] [DEBUG] return value from xrdp_mm_connect 0 [20190730-18:33:31] [INFO ] xrdp_wm_log_msg: login successful for display 10 [20190730-18:33:31] [DEBUG] xrdp_wm_log_msg: started connecting [20190730-18:33:32] [INFO ] lib_mod_log_peer: xrdp_pid=11136 connected to X11rdp_pid=11141 X11rdp_uid=1008 X11rdp_gid=1009 client_ip=10.64.27.2 client_port=45509 [20190730-18:33:32] [DEBUG] xrdp_wm_log_msg: connected ok [20190730-18:33:36] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20190730-18:33:36] [DEBUG] Closed socket 20 (AF_UNIX) [20190730-18:33:40] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20190730-18:33:40] [DEBUG] Closed socket 20 (AF_UNIX) [20190730-18:33:44] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20190730-18:33:44] [DEBUG] Closed socket 20 (AF_UNIX) [20190730-18:33:48] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20190730-18:33:48] [ERROR] xrdp_mm_connect_chansrv: error in trans_connect chan [20190730-18:33:48] [DEBUG] Closed socket 18 (AF_INET 127.0.0.1:52154) [20190730-18:33:48] [DEBUG] Closed socket 12 (AF_INET 10.64.5.120:3389) [20190730-18:33:48] [DEBUG] xrdp_mm_module_cleanup [20190730-18:33:48] [DEBUG] Closed socket 19 (AF_UNIX) [20190730-18:33:48] [DEBUG] Closed socket 20 (AF_UNIX) **xrdp-sesman.log** [20190730-18:32:31] [DEBUG] Closed socket 1 (AF_INET 127.0.0.1:3350) [20190730-18:32:31] [INFO ] starting xrdp-sesman with pid 11093 [20190730-18:32:31] [INFO ] listening to port 3350 on 127.0.0.1 [20190730-18:32:46] [INFO ] A connection received from 127.0.0.1 port 51792 [20190730-18:32:46] [INFO ] ++ created session (access granted): username walker, ip 10.64.27.2:57868 - socket: 12 [20190730-18:32:46] [INFO ] starting Xorg session... [20190730-18:32:46] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:5910) [20190730-18:32:46] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6010) [20190730-18:32:46] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6210) [20190730-18:32:46] [DEBUG] Closed socket 8 (AF_INET 127.0.0.1:3350) [20190730-18:32:46] [INFO ] calling auth_start_session from pid 11099 [20190730-18:32:46] [DEBUG] Closed socket 7 (AF_INET 127.0.0.1:3350) [20190730-18:32:46] [DEBUG] Closed socket 8 (AF_INET 127.0.0.1:3350) [20190730-18:32:46] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log [20190730-18:32:46] [CORE ] waiting for window manager (pid 11100) to exit [20190730-18:32:46] [CORE ] window manager (pid 11100) did exit, cleaning up session [20190730-18:32:46] [INFO ] calling auth_stop_session and auth_end from pid 11099 [20190730-18:32:46] [DEBUG] cleanup_sockets: [20190730-18:32:46] [DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdp_chansrv_socket_10 [20190730-18:32:46] [DEBUG] cleanup_sockets: failed to delete /tmp/.xrdp/xrdp_chansrv_socket_10 [20190730-18:32:46] [INFO ] ++ terminated session: username walker, display :10.0, session_pid 11099, ip 10.64.27.2:57868 - socket: 12 [20190730-18:33:31] [INFO ] A connection received from 127.0.0.1 port 52154 [20190730-18:33:31] [INFO ] ++ created session (access granted): username walker, ip 10.64.27.2:45509 - socket: 12 [20190730-18:33:31] [INFO ] starting Xorg session... [20190730-18:33:31] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:5910) [20190730-18:33:31] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6010) [20190730-18:33:31] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6210) [20190730-18:33:31] [DEBUG] Closed socket 8 (AF_INET 127.0.0.1:3350) [20190730-18:33:31] [INFO ] calling auth_start_session from pid 11139 [20190730-18:33:32] [DEBUG] Closed socket 7 (AF_INET 127.0.0.1:3350) [20190730-18:33:32] [DEBUG] Closed socket 8 (AF_INET 127.0.0.1:3350) [20190730-18:33:32] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log [20190730-18:33:32] [CORE ] waiting for window manager (pid 11140) to exit [20190730-18:33:32] [CORE ] window manager (pid 11140) did exit, cleaning up session [20190730-18:33:32] [INFO ] calling auth_stop_session and auth_end from pid 11139 [20190730-18:33:32] [DEBUG] cleanup_sockets: [20190730-18:33:32] [DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdp_chansrv_socket_10 [20190730-18:33:32] [DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdpapi_10 [20190730-18:33:32] [DEBUG] cleanup_sockets: failed to delete /tmp/.xrdp/xrdpapi_10 [20190730-18:33:32] [INFO ] ++ terminated session: username walker, display :10.0, session_pid 11139, ip 10.64.27.2:45509 - socket: 12 Any advice that can point me towards a solution would be awesome thanks!

I recently found how to make Remmina forward my Dvorak keyboard layout, but for some reason control-key combinations are not forwarded and the remote machine mapping is being used instead. That is quite annoying when using Bash@putty with no ability to access Bash reverse-i-search shortcut (Ctrl+R). __How are we supposed to make Remmina also forward Ctrl+KEY?__

I recently upgraded my Ubuntu to 18.04, and now my Remmina cannot connect to a windows server we use at work. Now I am getting a popup about certificates. It asks if I want to accept the certificate, I click OK and then get a message saying unable to connect. I am getting this error on the command line: [14:49:19:412] [7223:7537] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [14:49:19:412] [7223:7537] [INFO][com.freerdp.client.common.cmdline] - loading channelEx drdynvc [14:49:19:909] [7223:7537] [ERROR][com.freerdp.crypto] - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [14:49:19:909] [7223:7537] [ERROR][com.freerdp.crypto] - @ WARNING: CERTIFICATE NAME MISMATCH! @ [14:49:19:909] [7223:7537] [ERROR][com.freerdp.crypto] - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [14:49:19:909] [7223:7537] [ERROR][com.freerdp.crypto] - The hostname used for this connection (xxxxx:3389) [14:49:19:909] [7223:7537] [ERROR][com.freerdp.crypto] - does not match the name given in the certificate: [14:49:19:909] [7223:7537] [ERROR][com.freerdp.crypto] - Common Name (CN): [14:49:19:909] [7223:7537] [ERROR][com.freerdp.crypto] - EC2AMAZ-FM25IO2 [14:49:19:909] [7223:7537] [ERROR][com.freerdp.crypto] - A valid certificate for the wrong name should NOT be trusted! [14:50:38:624] [7223:7537] [ERROR][com.freerdp.crypto] - certificate not trusted, aborting. [14:50:38:624] [7223:7537] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_CONNECT_CANCELLED [0x0002000B] [14:50:38:624] [7223:7537] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure 0002000B 00000003 Now this is an internal vpn server so I don't care at all about certificates. Is there a way to add this certificate to a list that it's ok? How do I get around this? And as an aside, this was working before the upgrade just fine. I don't know why it cares now?

On ubuntu 22.04, I want to login remotely to it using RDP after boot up, the machine is not connected any display. RDP is not started and Wayland (Gnome session) is not unlocked without physical interaction of user with keyboard and mouse. Although Autologin is successful, gnome session is locked with keyring on ubuntu 22.04. When I try to unlock manually by connecting with HDMI display, the RDP password is randomly changed. Needs. 1. Bypass the keyring prompt to unlock automatically. 2. Must not be randomly changed RDP login password. How to solve it. Thanks.

I'm having the most infuriating problem with Remmina. It never connected every time but worked fine once connected. Don't know if this was a hint of things to come but I signed up to a new VPS and everything was fine yesterday but today after changing nothing it suddenly wouldn't connect. I started out simple and restarted remmina and the computer, then removed and re-entered the profiles then uninstalled and reinstalled Remmina. I then tried to access it on a live parrot OS (I use Parrot OS) thinking some change I wasn't aware of caused the issue but to no avail. I then discovered that I could still connect to another VPS using the same setup. I've tried all options of security protocols (auto, rdp, NLA, TLS) with no luck. Some tell me to check the protocol setting, some just dont connect and some get caught in a loop continually asking for user/pass/domain. I've looked around the net for similar problems and found some info about perhaps deleting known_hosts files etc but it's for different versions and distros so paths aren't the same and I don't want to screw something up I don't completely understand. Anyway I am at my wits end with this and am desperate for any help. TIA Also below are logs of the issue, one in auto and the other in RDP protocol.

┌─[mark@parrot]─[~]
└──╼ $remmina
** Message: 09:20:08.830: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=all" as an environment variable.
More info available on the Remmina wiki at:
https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging 
Load modules from /usr/lib/x86_64-linux-gnu/remmina/plugins
Remmina plugin glibsecret (type=Secret) has been registered, but is not yet initialized/activated. The initialization order is 2000.
The glibsecret secret plugin has been initialized and it will be your default secret plugin
Warning: Remmina is running with a secrecy plugin, but it cannot connect to a secrecy service.

(org.remmina.Remmina:13391): Gtk-WARNING **: 09:20:08.904: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem
[09:20:16:883] [13391:13410] [WARN][com.freerdp.crypto] - Certificate verification failure 'self-signed certificate (18)' at stack position 0
[09:20:16:883] [13391:13410] [WARN][com.freerdp.crypto] - CN = gpu-server
[09:20:17:388] [13391:13410] [WARN][com.freerdp.core.nla] - SPNEGO received NTSTATUS: STATUS_LOGON_FAILURE [0xC000006D] from server
[09:20:17:388] [13391:13410] [ERROR][com.freerdp.core] - nla_recv_pdu:freerdp_set_last_error_ex ERRCONNECT_LOGON_FAILURE [0x00020014]
[09:20:17:388] [13391:13410] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[09:20:17:388] [13391:13410] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
[09:20:25:520] [13391:13410] [WARN][com.freerdp.core.nla] - SPNEGO received NTSTATUS: STATUS_LOGON_FAILURE [0xC000006D] from server
[09:20:25:520] [13391:13410] [ERROR][com.freerdp.core] - nla_recv_pdu:freerdp_set_last_error_ex ERRCONNECT_LOGON_FAILURE [0x00020014]
[09:20:25:520] [13391:13410] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[09:20:25:520] [13391:13410] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
[09:20:30:454] [13391:13410] [WARN][com.freerdp.core.nla] - SPNEGO received NTSTATUS: STATUS_LOGON_FAILURE [0xC000006D] from server
[09:20:30:454] [13391:13410] [ERROR][com.freerdp.core] - nla_recv_pdu:freerdp_set_last_error_ex ERRCONNECT_LOGON_FAILURE [0x00020014]
[09:20:30:454] [13391:13410] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[09:20:30:454] [13391:13410] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
[09:20:37:548] [13391:13410] [ERROR][com.freerdp.core] - nla_client_init:freerdp_set_last_error_ex ERRCONNECT_NO_OR_MISSING_CREDENTIALS [0x0002001B]
[09:20:37:548] [13391:13410] [ERROR][com.freerdp.core.transport] - NLA begin failed
^C
┌─[✗]─[mark@parrot]─[~]
└──╼ $

┌─[mark@parrot]─[~]
└──╼ $remmina
** Message: 09:23:08.235: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=all" as an environment variable.
More info available on the Remmina wiki at:
https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging 
Load modules from /usr/lib/x86_64-linux-gnu/remmina/plugins
Remmina plugin glibsecret (type=Secret) has been registered, but is not yet initialized/activated. The initialization order is 2000.
The glibsecret secret plugin has been initialized and it will be your default secret plugin
Warning: Remmina is running with a secrecy plugin, but it cannot connect to a secrecy service.

(org.remmina.Remmina:13753): Gtk-WARNING **: 09:23:08.324: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem

(org.remmina.Remmina:13753): Gdk-CRITICAL **: 09:23:08.595: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
[09:23:27:198] [13753:13789] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 11: Resource temporarily unavailable
[09:23:27:198] [13753:13789] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
[09:23:28:238] [13753:13789] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 11: Resource temporarily unavailable
[09:23:28:238] [13753:13789] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
[09:23:28:238] [13753:13789] [ERROR][com.freerdp.core] - freerdp_post_connect failed
libfreerdp returned code is 0002000D
^C
┌─[✗]─[mark@parrot]─[~]
└──╼ $

I am trying to configure XRDP on my **Xubuntu 24.04** machine to allow remote connections from another Xubuntu 24.10 Linux machine (via VPN, same network). My goal is to **create a new XFCE session through XRDP**, which provides **the same desktop experience as my local session**, without interfering with any user that might be physically present at the machine. --- ### What I am trying to achieve - I want to **connect remotely** and start a **new session**, not take over the existing local session. - This **new session** should offer the **same XFCE environment as my local desktop**, including: - Panels and launchers in the same positions. - Desktop layout and configurations as I’ve set them locally. - The same user profile experience as when logging in physically at the console. - I need this remote session to **start even if nobody is logged in locally**. > **Note:** On standard **Ubuntu 24.04 (GNOME)**, there is **built-in support for remote desktop** via RDP (GNOME Remote Desktop). > It allows remote users to connect through RDP and either **share the existing session** or **create a new one**, depending on the setup. > I would like to achieve a **similar behavior** on **Xubuntu**, where I can create a **new remote session**, with my **XFCE desktop environment**, that mirrors the experience I have when logged in locally. --- ### What I have tried - **VPN access** is working fine. It's like I'm on the local network. - XRDP is installed and running. - Packages installed: - xorgxrdp - dbus-x11 - xfce4 and xfce4-goodies - /etc/X11/Xwrapper.config:

allowed_users=anybody
   needs_root_rights=no

- /etc/xrdp/startwm.sh contains:

#!/bin/sh

    if [ -r /etc/default/locale ]; then
        . /etc/default/locale
        export LANG LANGUAGE
    fi

    exec startxfce4

- I also tried adding export DISPLAY=:10 in startwm.sh. - I created executable ~/.xsession and ~/.Xclients with exec startxfce4. - .Xauthority has correct ownership and permissions. --- ### What happens - XRDP successfully establishes a connection, creating a new session on display :10. - Xorg seems to start fine, but startxfce4 exits immediately. - On the client side (Remmina RDP), I see a **black screen** for a few seconds and then the connection closes. - xrdp-sesman.log reports:

Window manager exited quickly

- .xorgxrdp.10.log shows the X server terminating cleanly without errors. --- ### What works (as an alternative) **NoMachine Free** works, but it only connects to the **local physical session**, which I do not want, because it disturbs any local user, in addition, there may be no active session (PC just turned on). --- ### The core question **How can I configure XRDP on Xubuntu 24.04 to start a new XFCE session that loads my full user environment (panels, launchers, desktop layout), providing the same experience as logging in locally, without disturbing local users, or without having any active session?** --- ### Notes - I do **not** need multiple concurrent remote sessions. - I only need **one remote session**, separate from the physical console. - I prefer a solution that allows me to replicate the **same user experience** I have locally.

I have a pretty generic Kubuntu install and cannot RDP into it. I installed xrdp and created the .xsession file and can connect successfully from my Mac. I get the KDE logo with the spinning gear, and then the screen goes black with an "X" cursor that I can move around the empty screen. That's it. I am using stock SDDM as a display manager. If I switch to lightdm, xrdp works great, but I can't log into the machine the regular way so that's a fail. I need to stick with SDDM to use my machine normally. Can someone help?

I am using a Windows 11 machine as a thin client (B) to RDP to another machine running Ubuntu 22.04 Desktop (A). I enabled [GNOME Remote Desktop](https://wiki.gnome.org/Projects/Mutter/RemoteDesktop) over RDP as instructed [here]. Now, the issue is that the Ubuntu machine is connected to a widescreen monitor with higher resolution, while the Windows 11 laptop has a much lower resolution. As a result, scrollbars appear inside the RDP window on the Windows client side, even in the full screen mode. This is not only annoying, but also makes the setup unusable. I tried tweaking with the display resolution slider under the "Display" tab of the Windows RDP client. Unfortunately, that just affects the window size, but not the actual resolution. I cannot use xRDP, because I need to connect to an existing GNOME session on A from B. As far as I understand, xRDP requires all other sessions to be logged out, and it can only connect to existing X-Windows sessions (if configured accordingly). On a related note, I also connect to another Windows 10 desktop (C) connected to a lower resolution monitor from another Windows 11 desktop (D) client connected to the same widescreen monitor. This setup works flawlessly, i.e., the RDP window on D goes both full-screen and automatically resizes C's desktop. In other words, the same Windows 11 RDP client works fine with Windows 10's RDP server, but not with Ubuntu 22.04's embedded FreeRDP server. Looking for ideas to dynamically scale the display resolution according to connecting RDP client's (B's) resolution with the GNOME Remote Desktop server on A.

I have the latest version of Ubuntu at the moment 24.04.1 LTS with gnome remote desktop. When booting the computer, I can log into the remote desktop, this can be done several times in a row and the connection behaves stably. But if some time passes, an error occurs connecting to the gnome desktop, without any description of the error on the client side. Restarting the service does not solve the problem and you have to completely reboot the computer. This situation was there from the very beginning and installing the latest updates did not change anything. I look at the logs like this journalctl -f -u gnome-remote-desktop.service But I don't find anything useful for myself. I tried to search for errors from logs, but I found old bugs that were promised to be fixed 2-3 years ago and I think the fixes have already been made. Does anyone have any ideas on how to solve this problem or in what direction to look? some logs: сен 02 21:47:11 john-vServer gnome-remote-de: [RDP] Network or intentional disconnect, stopping session сен 02 21:47:37 john-vServer gnome-remote-desktop-daemon: [21:47:37:201] [1102:00037b09] [ERROR][com.freerdp.core.peer] - [peer_recv_callback_internal]: CONNECTION_STATE_NEGO - rdp_server_accept_nego() fail сен 02 21:47:37 john-vServer gnome-remote-desktop-daemon: [21:47:37:201] [1102:00037b09] [ERROR][com.freerdp.core.transport] - [transport_check_fds]: transport_check_fds: transport->ReceiveCallback() - STATE_RUN_FAILED [-1] сен 02 21:47:37 john-vServer gnome-remote-de: [RDP] Network or intentional disconnect, stopping session сен 02 21:47:39 john-vServer gnome-remote-desktop-daemon: [21:47:39:937] [1102:00037b25] [ERROR][com.freerdp.core.peer] - [peer_recv_callback_internal]: CONNECTION_STATE_NEGO - rdp_server_accept_nego() fail сен 02 21:47:39 john-vServer gnome-remote-desktop-daemon: [21:47:39:937] [1102:00037b25] [ERROR][com.freerdp.core.transport] - [transport_check_fds]: transport_check_fds: transport->ReceiveCallback() - STATE_RUN_FAILED [-1] сен 02 21:47:39 john-vServer gnome-remote-de: [RDP] Network or intentional disconnect, stopping session сен 02 21:47:39 john-vServer gnome-remote-desktop-daemon: [21:47:39:221] [1102:00037b2b] [ERROR][com.freerdp.core.peer] - [peer_recv_callback_internal]: CONNECTION_STATE_NEGO - rdp_server_accept_nego() fail сен 02 21:47:39 john-vServer gnome-remote-desktop-daemon: [21:47:39:221] [1102:00037b2b] [ERROR][com.freerdp.core.transport] - [transport_check_fds]: transport_check_fds: transport->ReceiveCallback() - STATE_RUN_FAILED [-1] сен 02 21:47:39 john-vServer gnome-remote-de: [RDP] Network or intentional disconnect, stopping session

I have Remmina working nicely with various remote machines (RDP, VNC). One feature I use a lot is the "Grab all keyboard events" toggle: This setting allows the host to pass the ⊞ Win key directly into the remote machine, rather than the host capturing it. Is there a way to start a session with the "grab" setting ON to begin with? I have to toggle it ON each time I start a session, and really have no reason to ever turn it off.

just bought a small thinkcenter and installed debian on it. I'm trying to get RDP working from my Windows desktop but whenever I connect with RDP I get a black screen. I'm confident the connection is working because if I type the wrong password I get refused, and when I do the right it connects. I also get logs in the xrdp logs. All the firewall stuff, etc is working I'm using Cinnamon On the actual machine, I am not signed into the account that I'm trying to RDP with security_layer=rdp in xrdp.ini I tried putting cinnamon-session in the .xsession file The remote connection just sits on black screen until I quit it. I think it is in fact connecting. It's just not rendering anything?

Hopefully this is a simple fix. I have Debian Bookworm with KDE Plasma on a 4K monitor. So just like with Win10 I must use scaling or else everything is just tiny. However, in KDE/Plasma, with that scaling active, also my RDP sessions are scaled up. Where that is not desirable at all. Win10 was smart enough to know not to scale up RDP sessions so as to keep the desired RDP screen resolution. Im using Remmina but not stuck on them. Is there a way to obtain this also with KDE on a 4K?

I migrate from Windows to Linux but have to continue to use Microsoft Outlook. I do not trust the reliability of Wine and do not want to use a web UI. An interesting possibility would be to run Outlook in a Linux-hosted Windows VM. A workable UX would however require Outlook to appear on the Linux desktop without an RDP window around it. This is sometimes called "application streaming" or "seamless mode". I know that Windows Server comes with Remote Desktop Services (RDS) that supposedly can be used in a RemoteApp mode. What should I do to publish Outlook as a RemoteApp and consume it on Linux?

Im currently providing a physical ubuntu machine which should be used as a remote machine. I don't have any problems connection to it from a windows machine, but for others user the login mask ends up in a blue screen after putting in the credentials. The setup was really basic - was configured as in written in most guides. Downloaded following packages: sudo apt-get install xrdp sudo apt-get install xfce4 Added the window manager to the starting file echo xfce4-session > ~/.xsession Allowed any connection to the port: sudo ufw allow 3389 In addition i created a group with all the users, and in the xrdp config file marked that at every login the group needs to be checked -> sesman.ini AllowRootLogin=true TerminalServersUsers= TerminalServersAdminss= AlwaysGroupCheck=true Where I need to look for solving this problem? Do I need to add more to a certain config file? Has anyone a similar issue and could help me? Thanks in advance!

I usually use Ubuntu via Screen Share (RDP) in another building and sometimes I need to reboot. But 1st thing after a reboot is a box asking to authorise the keychain/keyring which I can't type into remotely. I do not wish to root/sudo the whole OS in order to get around this as others have suggested. As another example, I also use my iMac remotely via Screen Share in a similar fashion. If I reboot the machine, I can still Screenshare into the login screen and type my password after a reboot. There is no need to disable any passwords or security features. So how can I reboot a Screen Shared Ubuntu OS and get to the desktop again If I can't physically type things into the keyboard?

I'm trying out the RDP functionality of Gnome 45 and I noticed that the local session is not locked automatically when a remote session is active the way it is on Windows. Is it possible to have this behavior? I'm using Arch Linux with the X display server.