Hi Stefan,

I get this error:

root@moop:~# apt update
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://dl.google.com/linux/chrome/deb stable Release
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:6 http://archive.canonical.com/ubuntu xenial InRelease
Hit:7 http://security.ubuntu.com/ubuntu xenial-security InRelease
Ign:8 http://ppa.launchpad.net/freenx-team/xenial/ubuntu xenial InRelease
Hit:9 http://ppa.launchpad.net/x2go/stable/ubuntu xenial InRelease
Err:10 http://ppa.launchpad.net/freenx-team/xenial/ubuntu xenial Release
  403  Forbidden
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/freenx-team/xenial/ubuntu xenial Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.



On 3/21/2018 2:17 PM, Stefan Baur wrote:
Hi Norm,

looks like you should run: apt update && apt upgrade && apt dist-upgrade

(confirm with "y" where appropriate and safe; abort if anything looks off)

If that doesn't pull in 4.1.x.x packages, we need to look at your
/etc/apt/sources.list and /etc/apt/sources.list.d/* entries.

Kind Regards,
Stefan Baur

Am 21.03.2018 um 22:01 schrieb Norm Green:
Hi Stefan,

Here's what I have:

normg@moop> apt list --installed |grep -i x2go
x2goagent/now 2:3.5.0.32-0~668~ubuntu16.04.1 all [installed,upgradable
to: 2:3.5.0.33-0~710~ubuntu16.04.1]
x2goserver/now 4.0.1.20-0~1125~ubuntu16.04.1 amd64 [installed,upgradable
to: 4.0.1.22-0~1197~ubuntu16.04.1]
x2goserver-extensions/now 4.0.1.20-0~1125~ubuntu16.04.1 all
[installed,upgradable to: 4.0.1.22-0~1197~ubuntu16.04.1]
x2goserver-xsession/now 4.0.1.20-0~1125~ubuntu16.04.1 all
[installed,upgradable to: 4.0.1.22-0~1197~ubuntu16.04.1]


normg@moop> apt list --installed |grep -i nx
inxi/xenial,xenial,now 2.2.35-0ubuntu1 all [installed,automatic]
libnx-x11-6/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
libnx-xcomposite1/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
libnx-xdamage1/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
libnx-xdmcp6/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
libnx-xext6/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
libnx-xfixes3/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
libnx-xinerama1/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
libnx-xpm4/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
libnx-xrandr2/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
libnx-xrender1/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
libnx-xtst6/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
nx-x11-common/now 2:3.5.0.32-0~668~ubuntu16.04.1 all
[installed,upgradable to: 2:3.5.0.33-0~710~ubuntu16.04.1]
nxagent/now 2:3.5.0.32-0~668~ubuntu16.04.1 amd64 [installed,upgradable
to: 2:3.5.0.33-0~710~ubuntu16.04.1]


Norm


On 3/21/2018 1:54 PM, Stefan Baur wrote:
Am 21.03.2018 um 21:45 schrieb Norm Green:
Hello List,

I find that the clipboard stops working after a period of time.
Specifically, copying from the windows desktop to the x2go window
doesn't work because x2go thinks the clipboard is empty.
I am copying from emacs on Windows to emacs on Linux.
It doesn't matter how many times I select and copy on windows, x2go does
not pass the clipboard contents to emacs on Linux.
But if I disconnect from the server and reconnect, it works, using the
same emacs windows.

This is with x2go client 4.1.1.1 running on Win7, but it also happened
on previous x2go client versions (4.0.x) .
  x2go server 4.0.1.20 is running on Ubuntu 16.04

Is this a known bug?  Any way to fix it?
This is/was actually a server issue rather than a client issue, so it
would be helpful if you posted x2go-/nx-related package versions of your
server.  My gut feeling is you might be running an older version of
NX-Libs, and thus you're still seeing that bug.

Kind Regards,
Stefan Baur



_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user




_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Reply via email to