Might be because of backports being enabled giving me a newer version of
something:
deb http://packages.linuxmint.com sylvia main upstream import backport
enabled giving me a newer version of something? Or maybe my apt database is corrupted somehow. This has been upgraded in place many times, not a fresh 18.3 install.
deb http://archive.ubuntu.com/ubuntu xenial main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu xenial-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu xenial-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ xenial-security main restricted universe multiverse deb http://archive.canonical.com/ubuntu/ xenial partner deb http://ppa.launchpad.net/x2go/stable/ubuntu artful main #deb-src http://ppa.launchpad.net/x2go/stable/ubuntu xenial main
These, apart from the X2Go repositories, seem to be the default values in my fresh VM (i.e., backport enabled).
So that's not it either.
Btw, to clear up some confusion here:
The following packages have unmet dependencies: x2goserver : Depends: x2goserver-x2goagent (>= 4.1.0.0-0~1517~ubuntu16.04.1) but it is not going to be installed Depends: x2goserver-x2goagent (< 4.1.0.0-0~1517~ubuntu16.04.1.1~) but it is not going to be installed E: Unable to correct problems, you have held broken packages.
I do not undersatnd how it can depend upon a version both less than and
greater than the current version available.
It's depending on a version greater or equal to 4.1.0.0-0~1517~ubuntu16.04.1 and less than 4.1.0.0-0~1517~ubuntu16.04.1.1~ (the tilde in Debian packaging always sorts before everything else, so any additional strings will make the version higher.)
Anyway, the point here is the *additional* .1 at the end.
That's to make sure that version bumps, like 4.1.0.0-0~1517~ubuntu16.04.2 also satisfy the dependency.
We're not really actively using that, but it's a pretty common versioning scheme.
Not explaining your error, though.
dpkg -l | grep -i x2go
from that machine please.
Mihai