At our company we run a Remote Desktop Gateway with RemoteApps Does anyone have a good and easy way to connect and use these from within Linux Mint 18.3? Been trying different things and a work around is an openVPN server and just connect directly to the Domain Controller and Remote Desktop Server. It would how ever be very neat to be able to just launch the RemoteApp instead.

I want to install TigerVNC on my freshly installed CentOS 7 server, version centos-release-7-4.1708.el7.centos.x86_64. So besides other tutorials I've tried already, I followed the Red Hat guide. However with variable error messages depending on the tutorial I never got the service to start. The following is exactly what I did on a new installation of CentOS 7: yum install tigervnc-server cp /usr/lib/systemd/system/vncserver@.service /etc/systemd/system/vncserver@.service vi /etc/systemd/system/vncserver@.service initial file content: [Unit] Description=Remote desktop service (VNC) After=syslog.target network.target [Service] Type=forking User= # Clean any existing files in /tmp/.X11-unix environment ExecStartPre=-/usr/bin/vncserver -kill %i ExecStart=/usr/bin/vncserver %i PIDFile=/home//.vnc/%H%i.pid ExecStop=-/usr/bin/vncserver -kill %i [Install] WantedBy=multi-user.target file content after edit: [Unit] Description=Remote desktop service (VNC) After=syslog.target network.target [Service] Type=forking User=root # Clean any existing files in /tmp/.X11-unix environment ExecStartPre=-/usr/bin/vncserver -kill %i ExecStart=/usr/bin/vncserver %i PIDFile=/home/root/.vnc/%H%i.pid ExecStop=-/usr/bin/vncserver -kill %i [Install] WantedBy=multi-user.target Instructions after file edit: systemctl daemon-reload su - root vncpasswd systemctl start vncserver@:1.service Job for vncserver@:1.service failed because a timeout was exceeded. See "systemctl status vncserver@:1.service" and "journalctl -xe" for details. [root@localhost ~]# systemctl status vncserver@:1.service ● vncserver@:1.service - Remote desktop service (VNC) Loaded: loaded (/etc/systemd/system/vncserver@.service; disabled; vendor preset: disabled) Active: failed (Result: timeout) since Wed 2018-01-03 09:00:17 UTC; 22s ago Process: 2045 ExecStart=/usr/bin/vncserver %i (code=exited, status=0/SUCCESS) Process: 2040 ExecStartPre=/usr/bin/vncserver -kill %i (code=exited, status=2) Jan 03 08:58:50 localhost vncserver: New 'localhost:1 (root)' desktop is localhost:1 Jan 03 08:58:50 localhost vncserver: Creating default startup script /root/.vnc/xstartup Jan 03 08:58:50 localhost vncserver: Creating default config /root/.vnc/config Jan 03 08:58:50 localhost vncserver: Starting applications specified in /root/.vnc/xstartup Jan 03 08:58:50 localhost vncserver: Log file is /root/.vnc/localhost:1.log Jan 03 08:58:50 localhost systemd[1] : PID file /home/root/.vnc/localhost:1.pid not readable (y...art. Jan 03 09:00:17 localhost systemd[1] : vncserver@:1.service start operation timed out. Terminating. Jan 03 09:00:17 localhost systemd[1] : Failed to start Remote desktop service (VNC). Jan 03 09:00:17 localhost systemd[1] : Unit vncserver@:1.service entered failed state. Jan 03 09:00:17 localhost systemd[1] : vncserver@:1.service failed. Hint: Some lines were ellipsized, use -l to show in full. Does anyone have a clue how I can solve this?

[Documentation](https://wiki.archlinux.org/index.php/X2go#Start_X2Go_server_daemon) and various internet answers suggest x2goserver will have a service on systemd systems which can be started (or stopped, etc) with systemctl start x2goserver. However, there is no such service on my system (Fedora 30 MATE): > Unit x2goserver.service could not be found. There is also no process by this name except for x2gocleansessions: $ pgrep -la x2go 1808 /usr/bin/perl /usr/sbin/x2gocleansessions Yet, X2Go is working. Has its process or service been named something else now? How can X2Go be turned off or on?

I would like to start a new Xorg server on a **remote** host. At first, I tought this would be as easy as it is on the local host: $ xinit /usr/bin/startxfce4 -- :4 On a _local_ host, this command typed into a (non-graphic) login shell (vt/tty) will start _another_ Xorg server, i.e. I will have a xfce4 desktop after this - and this desktop is _additional_ to my normal desktop started from login from the desktop manager (e.g. sddm). However, if I try that on a _remote_ (fedora) system from the ssh console: X.Org X Server 1.20.6 X Protocol Version 11, Revision 0 Build Operating System: 5.0.6-200.fc29.x86_64 Current Operating System: Linux noah.siteos-lokal.de 5.5.10-200.fc31.x86_64 #1 SMP Wed Mar 18 14:21:38 UTC 2020 x86_64 Kernel command line: BOOT_IMAGE=(hd0,msdos3)/vmlinuz-5.5.10-200.fc31.x86_64 root=/dev/mapper/vg_sdd-root ro rd.luks.uuid=luks-a9eba963-ff2e-499b-a298-0659c5e29359 rd.lvm.lv=vg_sdd/root rd.lvm.lv=vg_sdd/swap rhgb quiet resume=/dev/disk/by-uuid/73299393-6bdb-4230-a1ca-096e5ee32396 splash=silent quiet video.use_native_backlight=1 Build Date: 25 November 2019 12:00:00AM Build ID: xorg-x11-server 1.20.6-1.fc31 Current version of pixman: 0.38.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/home/tpasch/.local/share/xorg/Xorg.4.log", Time: Fri Apr 3 19:38:52 2020 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied) (EE) (EE) Please consult the Fedora Project support at http://wiki.x.org for help. (EE) Please also check the log file at "/home/tpasch/.local/share/xorg/Xorg.4.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error I wonder why it is possible to start _another_ Xorg on the _local_ host but I get this error on a _remote_ host. I'm _not_ expecting to 'see' the new desktop from my ssh terminal. But I would expect that I could ‘export’ the new Xorg rendered desktop with e.g. x11vnc. It there easy way to get this running? The bounty is for: * Showing how to start _another_ Xorg server on a _remote_ fedora machine from a ssh terminal session. The following answers will not be considered: * Using Xvfb, Xvnc or the like. * Using some kind of remote desktop technology (RDP, VNC, Spice, TeamViewer, ...)

I need to access a remote machine via a high latency, slow connection. It uses x11vnc and I want it to broadcast video in much lower quality than what's actually on the screen. First thing that comes to mind is to use less colours (e.g. 8 bit), but it can be anything, as long as the remote machine is responsive even though it may, for example, show a large rich-colour desktop image (which I don't need to see anyway). Something [like this](https://superuser.com/questions/411058/setting-up-tightvnc-for-8-bit-pixels) , except for x11vnc. I will, however, appreciate keeping all the text sharp because, I work with the terminal. Here's what I tried: - use -notruecolor, found here http://www.karlrunge.com/x11vnc/x11vnc_opts.html - use -speeds dsl, found here https://ubuntuforums.org/showthread.php?t=1331555 - try setting 8 bit video using -rawfb, found here https://linux.die.net/man/1/x11vnc - enable -ncache 10 as per https://feeding.cloud.geek.nz/posts/high-latency-vnc-tech-support/ , but got [this issue](https://github.com/novnc/noVNC/issues/525) I'm using the built-in Screen Sharing app, which [seems to be almost the only option](http://web.archive.org/web/20180324015551/http://www.davidtheexpert.com/post.php?id=5) on Mac OS. I'm out of ideas. Please help.

I would like to run an Ubuntu (18.0.4) desktop with no monitor/keyboard attached, and access it via VNC (or Remote Desktop) from a Windows 10 Pro machine. I have installed VNC Viewer on Windows and enabled remote access from Linux. It all works, but not until I log on to the Linux box from an actual keyboard - which defeats the purpose. In other words, Linux will let me log in remotely only after I am logged in physically. I followed instructions to set up Linux for remote access , including the bit about "allowing unencrypted connections", but then I realized that those are instructions for allowing an external user to view/control *the same session* as a logged-on user, as opposed to allowing an external user to start their own session. What do I need to do to have the Linux-side start up and be ready for connections without the need to attach a physical keyboard? For instance, perhaps I need to make sure that VNC Server starts as soon as the Linux machine boots, etc. It does not need to be VNC. I can work in the Windows remote desktop window as well. I just want to access this Linux machine without attaching a keyboard/mouse/monitor.

I followed the directions to install xRDP from this site (http://ajmatson.net/wordpress/2014/01/install-xrdp-remote-desktop-to-centos-6-5/) When I RDP from Windows -> Linux, I successfully enter username/password, but then I get an empty desktop. It shows the desktop wallpaper (not actually my wallpaper either -- looks like the default wallpaper for XFCE/CentOS) I'm not sure what I should be seeing at this point. It doesn't matter if I am already logged in interactively or not. (BTW -- Should I be seeing a new desktop or the same one that I'm logged in with? I imagine that is configurable anyhow.) **UPDATE:** I confirmed that I am indeed seeing Gnome (The gnome-session command is running) when I login to XRDP instead of startxfce4. From some searching around , this may be realated to to be a bug in Centos 6.5 wherein CentOS had some code changed that normally would have read from the user's .xsession or .Xclients file. However, I compared the 6.4 and the 6.5 file and I'm not seeing a difference. Furthermore, this doesn't entirely explain everything. It's probably OK if Gnome runs instead of XFCE, but why no panels, menus, can't right click, etc? I experimented with making adjustments to files like the startwm.sh file and the scripts in xinit. This yielded some fruit -- I was able to see a new XFCE desktop, but the adjustments I made seem to be incomplete because the .bashrc file and related scripts failed to execute and it feels hacky.

I am using Centos 8 and I am using the Vinagre Remote Desktop Viewer to access Windows 10 computer. Is there a way for me to share the copy/paste clipboard between the two? So I can just copy text,images,etc from Centos side and paste it immediately in Windows 10 side.

How to launch a GUI application on a BeagleBone that is running Linux (Debian 7.4) remotely? Notes: 1. putty is being used for the remote access. 1. The task is to have the GUI launched and displayed on the BeagleBone itself (i.e., no X11 forwarding)

I have a PC with two monitors, running X11. I'm using xpra in shadow mode to export the session. Here's how I launch the server:

xpra shadow :0  --bind-tcp=0.0.0.0:14600,auth=file,filename=$HOME/.xpra/password.txt --html=on --daemon=no

From the server logs, xpra detects my dual-monitor setup correctly:

2025-03-20 12:49:26,378  on display 'X11 display :0' of size 3840x1080
2025-03-20 12:49:26,378  with 2 monitors:
2025-03-20 12:49:26,378   HDMI-1           1920x1080 at    0,0   
2025-03-20 12:49:26,378   HDMI-2           1920x1080 at 1920,0

On the **client side**, I run:

xpra attach tcp://max:*******@localhost:14600 --opengl=no --desktop-fullscreen=no

client log also report dual-monitor setup on server:

2025-03-20 12:44:49,426 Xpra GTK3 X11 client version 6.2.5-r0
2025-03-20 12:44:49,465  running on Linux Ubuntu 24.10 oracular
2025-03-20 12:44:49,465  cpython 3.12
2025-03-20 12:44:49,466  window manager is 'Xfwm4'
2025-03-20 12:44:49,854 GStreamer version 1.24.8
2025-03-20 12:44:49,894 created unix domain sockets:
2025-03-20 12:44:49,894  '/run/user/1000/xpra/clients/jarvis-27499'
2025-03-20 12:44:50,361 Using existing mmap file '/run/user/1000/xpra/xpra.p4k1739z.mmap': 512MB
2025-03-20 12:44:50,545  keyboard settings: rules=evdev, model=pc105, layout=us
2025-03-20 12:44:50,761  desktop size is 3840x2160:
2025-03-20 12:44:50,761   :0.0 (702x392 mm - DPI: 139x140) workarea: 3840x2127 at    0x33  
2025-03-20 12:44:50,761     SAM HDMI-0       (697x392 mm - DPI: 140x140)
2025-03-20 12:44:51,092 enabled remote logging
2025-03-20 12:44:51,092 Xpra X11 shadow server version 6.2
2025-03-20 12:44:51,093  remote desktop size is 3840x1080
2025-03-20 12:44:51,093   :0.0 (1016x285 mm - DPI: 96x96) workarea: 3840x1059 at    0x21  
2025-03-20 12:44:51,093     BNQ HDMI-1       1920x1080 at    0x0    (531x299 mm - DPI: 92x92) workarea: 1920x1059 at    0x21
2025-03-20 12:44:51,093     BNQ HDMI-2       1920x1080 at 1920x0    (531x298 mm - DPI: 92x92) workarea: 1920x1080 at 1920x0
2025-03-20 12:44:51,188 Attached to xpra server at tcp://max@localhost:14600/

when the client connect to server, the tatter log:

2025-03-20 12:56:25,565 New tcp connection received
2025-03-20 12:56:25,565  from '127.0.0.1:41694'
2025-03-20 12:56:25,566  on '0.0.0.0:14600'
2025-03-20 12:56:25,574 Authentication required by password file authenticator module
2025-03-20 12:56:25,574  sending challenge using 'hmac+sha512' digest over tcp connection
2025-03-20 12:56:26,101 Handshake complete; enabling connection
2025-03-20 12:56:26,111 Python/GTK3 Linux Ubuntu 24.10 oracular X11 client version 6.2
2025-03-20 12:56:26,111  connected as 'max'
2025-03-20 12:56:26,111  OpenGL is disabled
2025-03-20 12:56:26,116 shadow server: setting default keymap translation
2025-03-20 12:56:26,136  client root window size is 3840x2160
2025-03-20 12:56:26,927  automatic picture encoding enabled, also available:
2025-03-20 12:56:26,927   h264, vp9, vp8, png, png/P, png/L, webp, avif, rgb24, rgb32, jpeg, jpega, av1, scroll
2025-03-20 12:56:26,957 found GPU accelerated encoders for: h264
2025-03-20 12:56:26,957 switching to 'stream' encoding for 'desktop' window 1
2025-03-20 12:56:26,957 using 'gstreamer' stream mode
2025-03-20 12:56:26,961 found GPU accelerated encoders for: h264
2025-03-20 12:56:26,962 switching to 'stream' encoding for 'desktop' window 2
2025-03-20 12:56:26,962 using 'gstreamer' stream mode
2025-03-20 12:56:27,002 client   1 @02.466 Xpra X11 shadow server version 6.2
2025-03-20 12:56:27,024 client   1 @02.466  remote desktop size is 3840x1080
2025-03-20 12:56:27,025 client   1 @02.466   :0.0 (1016x285 mm - DPI: 96x96) workarea: 3840x1059 at    0x21  
2025-03-20 12:56:27,025 client   1 @02.466     BNQ HDMI-1       1920x1080 at    0x0    (531x299 mm - DPI: 92x92) workarea: 1920x1059 at    0x21
2025-03-20 12:56:27,025 client   1 @02.466     BNQ HDMI-2       1920x1080 at 1920x0    (531x298 mm - DPI: 92x92) workarea: 1920x1080 at 1920x0
2025-03-20 12:56:27,105 client   1 @02.562 Attached to xpra server at tcp://max@localhost:14600/
2025-03-20 12:56:27,105 client   1 @02.562  (press Control-C to detach)
2025-03-20 12:56:27,475 shadow server: setting default keymap translation
2025-03-20 12:56:27,530 using monitor of default sink: USB Audio Device
/usr/lib/python3/dist-packages/xpra/server/shadow/gtk_shadow_server_base.py:341: DeprecationWarning: Gdk.Window.get_pointer is deprecated
  return self.root.get_pointer()[-3:-1]
2025-03-20 12:56:28,165 audio capture using 'opus' audio codec
2025-03-20 12:56:28,994 client   1 @04.441 running, 2 windows
2025-03-20 12:56:29,071 client   1 @04.532 Warning: image bigger than expected
2025-03-20 12:56:29,071 client   1 @04.533  3840x1080 instead of 1920x1080
2025-03-20 12:56:29,203 client   1 @04.625 Warning: image bigger than expected

### What happens - Xpra opens two windows, one for **HDMI-1** and one for **HDMI-2**. - Both windows display **the exact same content**, instead of each showing its portion of the desktop. - Only one of the two windows is interactive (receives input events). ### From the logs

Warning: image bigger than expected
  3840x1080 instead of 1920x1080

This warning repeats frequently.
It seems like xpra is sending the entire 3840x1080 desktop to both windows. --- ### What I'm trying to achieve: - Each client window should show **only the corresponding screen**, e.g. HDMI-1 shows the one screen, HDMI-2 the other. - Both windows should be responsive to events as if they were independent displays. ### What I've tried: - Read the xpra documentation regarding **shadow servers** and **multi-monitor setups**. - Tested with different --desktop-scaling and --opengl options. --- ### Question: How can I make xpra **split the view correctly** between the two windows, and make both windows interactive, with input routed to the correct area? --- ### Environment: - **Xpra version 6.2.5-r0** on both client and server - Server: Xubuntu 24.04, X11, Xfwm4 window manager, dual monitors (HDMI-1, HDMI-2) - Client: Xubuntu 24.10, Xfwm4 window manager

When I set up my home server, I installed Fedora 39 Server on it, and I set up remote access with xrdp, which worked great. Then after I upgraded to Fedora 40 and tried to remotely connect, I would get the login screen, enter my password and I'd immediately be kicked out. I can still connect in the terminal using PuTTY, I uninstalled and reinstalled the desktop (KDE), I reinstalled xrdp, but to no avail. When I run systemctl status xrdp, everything looks normal, except the session closes immeidately: I've looked online and maybe a remote session file would be left behind and inaccessible, but the solutions suggested there did not work either. Since the error doesn't seem very specific to me though, maybe I'm not looking in the right place. Any help is much appreciated.

I have an Ubuntu VM running in HyperV on a Windows 10 machine. When I connect to the VM using the HyperV Virtual Machine Connection window everything looks and functions just fine except for the fact that the resolution is locked at 1024x768 as well as the fact that by default I am not able to copy/paste into and from the VM to the host Windows machine. I have previously set up a Fedora VM in HyperV and have been able to do everything I need to do by connecting to the VM using Remote Desktop by having xrdp being set up on the VM, so I'm trying to set up an Ubuntu VM the same way but am coming across an issue with the performance and the display of the VM. Here's the setup: Host Machine: - Windows 10 Enterprise version 22H2 - OS Build 19045.5131 - Windows Feature Experience Pack 1000.19060.1000.0 - HyperV manager version 10.0.19041.1 VM: - Ubuntu 24.04.1 LTS x86_64 - Kernel 6.8.0-49-generic - Desktop environment: Gnome 46.0 - Shell: Bash 5.2.21 - Window manager: Mutter - Window manager theme: Adwaita - Theme: Yaru [GTK2/3] - Icons: Yaru [GTK2/3] - Terminal: gnome-terminal - xrdp version 0.9.24 The way I get on the VM via the HyperV Virtual Machine Connection window is by going to the HyperV manager, right clicking on the VM and clicking "Connect" which then brings up the HyperV Virtual Machine Connection window where I click "Start" and the VM starts up and looks as I expect it to. HyperV Manager connection window: Virtual Machine connection window: The way I get on the VM via Remote Desktop is by going to the HyperV manager, right clicking on the VM and clicking "Start" which then starts up the VM but does not bring up the HyperV Virtual Machine Connection window. I then open Remote Desktop where I enter the IP address of the VM in the "Computer" text box and click the "Connect" button which then brings up the xrdp login window where I enter the login credentials for the VM and then click *OK* which then opens the Remote Desktop window displaying the desktop for the VM. HyperV Manager start VM: Remote Desktop login: xrdp login: The main issue is that when I connect to the VM using Remote Desktop the display is very different and the performance is very slow (applications take quite a while to open, internet is slow, etc). For clarification, here's a screenshot of what it looks like when using the HyperV viewer (desktop displays with default settings, surrounding black area is due to small resolution): and here's a screenshot of what I see when connecting to the VM via Remote Desktop (desktop is just blue, this shot is the view after pressing the command button to illustrate that the desktop is just blue): When I run neofetch, the only things that are different from running it in the session via Remote Desktop is that the resolution is different as well as the values listed for the memory. In the spirit of being thorough, here are screenshots of both of them: Remote Desktop: HyperV: Another thing I've found is that the output from running xrandr displays differently between the two Remote Desktop: HyperV: I know that I can personalize the desktop appearance for the Remote Desktop instance, but the fact that by default it looks different from how it looks when booted up from the HyperV along with the fact that the performance is worse leads me to believe that there is something not configured properly to allow Remote Desktop session to look and behave just like the HyperV session when the VM is booted. So, the question is what do I need to change or configure differently to make it so that when I start the VM via Remote Desktop the VM session looks like it should and also performs as expected (which is how the VM looks and performs when opened via HyperV)?

I am on KDE Plasma, Kwin (Wayland), Arch based distro (Endeavour). I use tty1, and want my friend to login to e.g. tty2, start up plasmashell, and then remote-in/stream specifically tty2 to e.g their laptop. This way I can use my computer in my tty1, and they can simultaneously e.g. watch videos/play games on their tty2 using my system's resources. Normally, I would try something with X servers or tigervnc perhaps, but that's not available on wayland systems. I tried moonlight/sunshine but that seems to stream the current display, and the control is shared (e.g. current on screen mouse always moves). Is this functionality even presently possible, and if so, how could one achieve this?

The network structure in my room. Optical Network Unit(192.168.1.1) -->pc1(192.168.1.3) -->home router(192.168.31.1)-->pc2(192.168.31.203) I try to access remote desktop from pc1 (wan) to pc2(lan) with the rdesktop command: rdesktop -u user -p password 192.168.31.203:3389 It can't work,how can use remote desktop from wan to lan?

after ssh to a machine, I got the following message, xrdb: Resource temporarily unavailable xrdb: Can't open display 'localhost:10.0' What does it mean?

When using RemotePC to remote-desktoping from Win 11 to Linux Ubuntu 22.04 over the web, the keyboard isn't working well, and, in particular, Ctrl-key commands and the like don't work. Despite being officially cross-platform, RemotePC doesn't seem to have a native feature to enable it for Win to Linux. Is there any simple solution that allows using the keyboard properly, incl. sending Ctrl-keys and the like? I've seen resembling questions answered for other RD software such as Remmina, but so far found no solution for RemotePC. I'd like to use RemotePC as it ticks off a few boxes in terms of simple setup & basic features that I've so far not seen all ticked by other RD software (unless some which are even much more expensive than RemotePC).

I am trying to profile a program that uses CUDA on Alma Linux 9. I've installed Nvidia's nsight compute tool and when I start to try and profile my program, I get an error:

==ERROR== ERR_NVGPUCTRPERM - The user does not have permission to access NVIDIA GPU Performance Counters on the target device 0. For instructions on enabling permissions and to get more information see https://developer.nvidia.com/ERR_NVGPUCTRPERM 

When I try running the program as root though, I get another error:

################# ERROR: CrashReporter #################
CrashReporter

Qt initialization failed

Failed to load Qt platform plugin: "xcb"
 - Library path: /usr/local/NVIDIA-Nsight-Compute-2024.3/host/linux-desktop-glibc_2_11_3-x64/Plugins/platforms/libqxcb.so
Application is going to abort
No protocol specified
Error: Can't open display: :10.0
/usr/local/NVIDIA-Nsight-Compute-2024.3/host/linux-desktop-glibc_2_11_3-x64/ncu-ui: line 26: 2032536 Aborted                 (core dumped) "$NV_AGORA_PATH/CrashReporter" "NVIDIA Nsight Compute" "NVIDIA Nsight Compute" "2024.3.2.0 (build 34861637) (public-release)" "$NV_AGORA_PATH/ncu-ui.bin" "$@"

That library is there, however I am using xrdp to access the machine, could that be why this failure happens?

Apparently Fedora 25, even if in alpha state (not for long, beta coming soon) is doing extremely well with Wayland enable by default. Is there any graphical/easy-to-setup solution out there for remote desktop management (under another Linux machine) that will work with Wayland? Or is it too early?

So my team is building a few Autodesk Flame systems using Rocky Linux 9.3 that we would like to be able to access using VNC. We installed x11VNC but are only able to access it remotely if we start and enable the vnc app after it has turned on using a local monitor and keyboard, defeating the purpose. How do we configure the x11vnc.service in order to be able to access it with VNC without having to first go and start the app manually and locally? Would also like to be able to 'log off' the Rocky Linux 9.3 system and still see its login screen in order to switch users while connected through VNC remotely. Here is my x11vnc.service file: [Unit] Description=VNC server for the current X11 session After=display-manager.service [Service] ExecStart=/usr/bin/x11vnc -auth guess -cursor arrow -display :0 -forever -loop -noallinput -nobell -nodpms -noipv6 -nomodtweak -nopw -norc -nossl -noxdamage -noxfixes -noxkb -noxrecord -o /var/log/x11vnc.log -reopen -repeat -rfbauth /root/.vnc/x11vnc.passwd -rfbport 5900 -rfbversion 3.8 -shared Restart=on-failure RestartSec=3 [Install] WantedBy=graphical.target Thank you soo much for anybody who can help me solve this issue. Ill be forever in your debt.

I have been a user of Windows Remote Desktop for quite long by now. When I replicate the same setup to remotely access my Ubuntu desktop, no matter what solution I try, I find it lacking one way or the other. Specifically, I am looking for the following features: 1. **Dynamic update of host resolution based on client's**: The remote host's resolution should adjust seamlessly depending on the client's. It should not matter if I am accessing the remote host from a laptop or a desktop with a widescreen monitor. Note that only scaling it not enough, as it either stretches, or shrinks, or makes scrollbars appear around the remote desktop's window. 2. **Remote host will stay locked and screen turned off during remote access**: Otherwise, it is a privacy issue and/or drains power. 3. **Logged in session on remote host can be accessed remotely**: The remote desktop solution should not spin up a brand new virtual session. The local session that is logged on to the remote host can be accessed remotely. In other words, if I start working at office, lock the computer, come back home, access it remotely, I should be dropped to the same session and resume work from where I left off. 4. **Access entire desktop, not specific applications**: The client machine acts as a thin client. Remote host does the heavy lifting. Here's the feature matrix of the Ubuntu remote access solutions I tried so far: | Solution | Feature-1 | Feature-2 | Feature-3 | Feature-4 | | -------- | :----: | :----: | :----: | :----: | | Ubuntu 22.04 Remote Desktop | **No** | **No** | Yes | Yes | | xrdp | **No** | Yes | **No** | Yes | | VNC | **No** | Yes | **No** | Yes | | SSH X-forwarding | **No** | Yes | **No** | **No** | I find it unbelievable that it's 2024 and I cannot find a Linux/Ubuntu-based remote desktop solution that checks all the boxes. Windows RDP does, which is a life saver. Am I missing something? Is there any hack that turns one of these solutions to my dream one? Or, is there something promising that I have not explored yet?