2 Trying to start an X2Go session in Remmina in a Wayland session will pop up a dialog like this:
4 ![screen-gtksockot-not-avail-error-dialog](uploads/b319220cd824ca9c47b6570f30af7bdc/screen-gtksockot-not-avail-error-dialog.png)
6 The _`GtkSocket`_ feature has been deprecated for a while now, and is no longer supported in GTK4.
7 It uses the X11-only feature _`XEmbed`_, meaning **it can't be used under _`Wayland`_ natively.**
11 **Don't worry! There is a possible solution if you want to use Remmina in a _Wayland_ session instead of an _X11_ session.**
13 You can force Remmina to start as an _`X client`_ instead of a native _`Wayland client`_ (see illustration below) by setting an _`environment variable`_ before starting Remmina.
15 Try to start Remmina like this:
17 - First open a _`terminal emulator`_. (like QTerminal, GNOME Terminal, Mate Terminal, Alacritty, XTerm…)
18 More than likely you don't have to install one yourself, since most distributions come with a terminal emulator preinstalled.
19 - Type in the following and press the enter key:
22 GDK_BACKEND=x11 remmina
25 - Remmina should start and everything should **just work** ;)
27 ![grafik](uploads/a54409f2be46d271996e6ef6bf74eed3/grafik.png)
29 [Source: wayland.freedesktop.org](https://wayland.freedesktop.org/architecture.html)
33 A significant change for the better would be to **removing the X11-only** _`XEmbed`_ feature dependency from the architecture of the X2Go plugin.
35 This does requires a lot of work though.
36 If you can imagine funding this heavy-lifting work, please get in touch with the Remmina project maintainers over some virtual coffee.