Arch Linux

trippycamper

Member

Registered: 2025-09-22

Posts: 3

X2Go issues with KDE Plasma (wayland)

Having issues running the x2go client on my laptop, every time I launch the connection to the client I get the following error message:

The connection with the remote server was shut down.
Please check the state of your network connection.

I've been following fix instructions on AUR here:
https://wiki.archlinux.org/title/X2Go#X … ut_down%22

It leads me to this page, instructing me to edit the desktop entries: https://wiki.archlinux.org/title/Deskto … _variables

I'm stuck here because I can't find any files with the .desktop suffix relating to X2Go or related programs. Is this a file I would need to create myself? Alternatively, how can I switch to xorg graphics from wayland? Ive been following the linked guide for that but I must've setup something I forgot about because I never reach a login page on startup and when I lock or sign out the switch option is not there.
https://www.siberoloji.com/how-to-switc … rch-linux/

TIA for any advice

Device information:

KDE Plasma Version: 6.4.5
KDE Frameworks Version 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.12.51-1-lts (64-bit)
Graphics Platform: Wayland

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 13,018

Website

Re: X2Go issues with KDE Plasma (wayland)

Mod note: Moving to AUR Issues.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

twelveeighty

Member

Registered: 2011-09-04

Posts: 1,387

Re: X2Go issues with KDE Plasma (wayland)

To check if `x2goclient` installed a .desktop, use pacman -Ql (as a regular user) and grep its output: `pacman -Ql x2goclient | grep desktop`. If there isn't one, you can create it yourself and put it in ~/.local/share/applications/, but before you go down that path, let's first make sure setting QT_QPA_PLATFORM will fix your problem; I'd recommend just running the client from a terminal after setting the QT_QPA_PLATFORM=xcb environment variable:

$ export QT_QPA_PLATFORM=xcb
$ x2goclient

(you can do this all on one line, this just makes it easier to see what's happening).

The benefit of doing it this way is that you may see more useful debug/errors that get echoed back to the terminal in case this isn't the actual problem and it's still failing.