Tigervnc fedora
![tigervnc fedora tigervnc fedora](https://www.unixmen.com/wp-content/uploads/2015/07/Thunderbir-38.png)
![tigervnc fedora tigervnc fedora](https://www.linuxidc.com/upload/2018_10/18102921013550.png)
If you don’t have such option, make sure you have installed gnome-remote-desktop, because I’m not sure whether it’s installed by default. There you should see this window when you click on Screen Sharing: Go and open gnome-control-center ( Settings) and there go to Sharing section. However, you need to enable remote desktop (if you want to). You don’t seem to do any additional step in order to make screen sharing work. Enabling screen sharing and remote desktop in Gnome PipeWire should be automatically installed on your system, the package name is pipewire and it provides socket-based activation so you shouldn’t need to worry if it’s running or not. This is done throught a PipeWire stream shared between the compositor and application. PipeWire is the core technology used for screen content delivery from the compositor to applications. The second important dependency is PipeWire. For example you don’t get a gtk dialog to open a file in KDE Plasma session or you want a backend communicating with specific compositor (like in our case with Mutter). The reason why portals consist from two services is that there can be multiple backends, each one providing native dialogs for your desktop. Both are DBus activatable, which means they are automatically started whenever application calls them. In Fedora you should have portals automatically installed, they are represented by two separate packages, first is xdg-desktop-portal, which is the portal service communicating with sandboxed applications and with a backend implementation of portals, and the second package is the backend implementation, in our case xdg-desktop-portal-gtk. Flatpak) to get access to system (like files or printing) outside the sandbox, their design perfectly fits for Wayland usage too.
![tigervnc fedora tigervnc fedora](https://www.capehut.com/1735-large_default/tiger-party-fedora-hat-c1119rzx7af.jpg)
While portals were primarily meant to be used by sandboxed applications (e.g. Dependenciesīoth screen sharing and remote desktop work almost identically on Wayland, they both use portals as a communication tool between applications and compositor (in this case Mutter) to start the process of sharing and setup PipeWire stream (see below). This tutorial targets Fedora, but it can be probably used by any other distribution. While most of the dependencies are automatically installed and services automatically activated, there still might be situations when this is not true, for example when switching from another desktop so it’s better to cover it all. There are also dependencies which need to be installed and services which need to be running. Problem is that unlike in old XServer sessions, there are certain things which need to be enabled first. I recently got an email from a user asking me how to make all this work on Fedora.