I use VNC on my FC 40 system daily. Tiger VNC does not support remote Wayland sessions. It is necessary to use X11 as the transport.
I followed the instructions in the vncserver.service file: # The vncserver service unit file # # Quick HowTo: # 1. Add a user mapping to /etc/tigervnc/vncserver.users. # 2. Adjust the global or user configuration. See the # vncsession(8) manpage for details. (OPTIONAL) # 3. Run `systemctl enable vncserver@:<display>.service` # 4. Run `systemctl start vncserver@:<display>.service` I'm trying to remember if I had to manually install some form of X11 packages: xorg-x11-server-common-1.20.14-35.fc40.x86_64 xorg-x11-server-Xorg-1.20.14-35.fc40.x86_64 xorg-x11-drv-libinput-1.4.0-2.fc40.x86_64 qt5-qtx11extras-5.15.14-1.fc40.x86_64 xorg-x11-server-Xwayland-24.1.1-1.fc40.x86_64 I believe I tracked all of this down in the greater interwebs. Sadly I didn't keep a record of where. On Mon, Jul 29, 2024 at 9:37 PM Ben Koenig <[email protected]> wrote: > The Arch wiki has a few links to follow. Adjust as needed for your > preferred setup. > > Looks like VNC backends for wayland compositors are generally a > compile-time option, so if you run through the steps and nothing happens, > it could be that support was not compiled in. > > https://wiki.archlinux.org/title/Wayland#Remote_display > > > As an amusing sidenote, not long ago I was embroiled in a wayland vs X > flamewar where some fanboys went out of their way to claim that wayland is > ready and has all the same features X does. So an instance of a real-world > user attempting to perform an end-usery task on wayland and then reaching > the conclusion that it is impossible makes me chuckle. > > Regardless of such nonsense the Arch wiki has information that suggests > that VNC can work with wayland. Their documentation is usually pretty solid > and sticks with matter-of-fact descriptions of what does/doesn't work. > -Ben > > > On Monday, July 29th, 2024 at 7:53 PM, Tomas Kuchta < > [email protected]> wrote: > > > Anyone has a success story about deploying persistent multiuser VNC or > RDP > > setup on headless server running Wayland? > > > > I used to use classic VNC and RDP (tigerVNC and Xrdpd respectively) to > run > > persistent desktop multi user, multi DE sessions. I need it for both home > > lab and work. > > > > This seems to be currently impossible to do with Wayland. When reaching > out > > to RH/Fedora/SuSE folks - I only hear childish, immature responses > > suggesting that only newbies, windows people or idiots would need full > > desktop session and even worse - persistent one. > > > > At work, we use it for accessing long running interactive CAD sessions > and > > general workspaces on headless servers located in some caraway colo - > from > > laptops. We are connecting and disconnecting multiple times a day as we > > roam between office cubicles, conference rooms, remote work locations. My > > old X based session is 226 days on a host with 43 other KDE, Gnome, Mint > > and Xfce sessions. At home, it is similar, except with fewer users. > > > > In my previous job, we used self service, per user VMs. That is too > wildly > > progressive for our IT gatekeepers, so I am looking for traditional VNC > or > > RDP solution. And also for home use, so that I could move on from X on a > > headless servers. > > > > Anybody there who could help with good advice about how to go about it on > > recent Fedora, openSuSE, Ubuntu LTS? > > > > Thanks, Tomas >
