8

I'm using X2GO to connect to a remote VM from my Windows 10 OS, but clipboard breaks after I try to copy/paste something from my local machine to the remote. It initially works after I start the session, but it stops working after few times of copy/paste.

The things is that when it happens, Windows clipboard stops functioning also.

Only after I restart the session, clipboard works again until it breaks.

There is no much on this issue in the internet. I tried few options suggested by some people, but it didn't help.

The remote machine is CentOS 7.7.1908.

I'm using latest X2GO Client/Server:

Client v. 4.1.2.2

Server v. 3.5.99.25

Any suggestion for workaround?

farid g.
  • 519
  • 3
  • 11

2 Answers2

19

Just after I published my question, I was hit by "eureka" discovery and found the solution.

Follow these steps:

  • Open X2GO Client application
  • Click "Options" menu --> Settings
  • Select "X. Org Server Settings" tab
  • Select "do not use primary clipboard" (make sure its CHECKED!)
  • Click OK
  • !!! RESTART X2GO CLIENT !!!
farid g.
  • 519
  • 3
  • 11
4

Unfortunately, sometimes clipboard breaks even with these settings:

Click "Options" menu --> Settings
Select "X. Org Server Settings" tab
Select "do not use primary clipboard" (make sure its CHECKED!)

I use following workaround when this happened. I copy any text on the remote machine and than copy on my local. After that, clipboard is fine (not for long)

mr NAE
  • 3,144
  • 1
  • 15
  • 35
  • yes, even with these settings it happens, but rarely. in my case, its stable enough. I suggest to restart the session if it happens to you – farid g. Dec 29 '21 at 13:17
  • IMHO those changes do not really make a difference. It works... Until a certain moment. Then it is broken. Then I suspend the session and resume again and it is okay again. – Paul Praet Sep 07 '22 at 11:16
  • The "copy from remote to local" trick usually fixes copying from local to remote for me. I just have to randomly copy in both directions to keep it working. No amount of restarting x2go fixes it. – Mike Miller Jul 14 '23 at 18:01