Hi Everyone,

I've been testing out x2go (https://wiki.x2go.org/) with KDE Neon. I have Neon running in a VM and am connecting to it from the host. The x2go server and client were installed from the PPA following the instructions at: https://fabianlee.org/2019/02/03/ubuntu ... op-access/

It seems to work pretty well, though there are a few rough edges that I'm working through. The biggest of these is that I am unable to suspend the session, whenever I try it seems to get terminated. I turned the server logs up to debug and watched them when attempting to suspend the session. It looks like there is some issue with systemd and/or dbus:

Code: Select all

Jan 27 21:08:06 neon-vm x2gochangestatus: db_changestatus called, session ID: rob-50-1580165959_stDstartplasma-x11_dp24, new status: S
Jan 27 21:08:07 neon-vm /usr/bin/x2gocmdexitmessage: x2gocmdexitmessage called with options: rob-50-1580165959_stDstartplasma-x11_dp24
Jan 27 21:08:07 neon-vm /usr/bin/x2gocmdexitmessage: command output starts with: exec startplasma-x11 Loading profile from /etc/profile Loading profile from /home/rob/.profile dbus-daemon[9460]: [session uid=1000 pid=9460] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=9508 comm="dbus-update-activation-environment --verbose --sys" label="unconfined") dbus-daemon[9460]: [session uid=1000 pid=9460] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9286 (x2goagent) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9331 (x2goruncommand) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9459 (dbus-run-sessio) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9460 (dbus-daemon) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9461 (startplasma-x11) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9529 (start_kdeinit) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9531 (kdeinit5) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9542 (klauncher) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9546 (kded5) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9552 (kaccess) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9555 (kactivitymanage) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9564 (plasma_session) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9568 (ksmserver) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9574 (kglobalaccel5) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9579 (dconf-service) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9594 (kscreen_backend) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9595 (kwin_x11) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9597 (xembedsniproxy) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9599 (plasmashell) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9601 (polkit-kde-auth) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9607 (baloo_file) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9612 (kdeconnectd) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9618 (gmenudbusmenupr) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9628 (DiscoverNotifie) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9649 (agent) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9650 (spice-vdagent) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9654 (at-spi-bus-laun) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9657 (org_kde_powerde) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9662 (distro-release-) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9667 (dbus-daemon) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9744 (obexd) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9745 (file.so) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9789 (baloorunner) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9819 (konsole) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 9830 (bash) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: session-10.scope: Killing process 10073 (file.so) with signal SIGTERM.
Jan 27 21:08:07 neon-vm systemd[1]: Stopping Session 10 of user rob.

Googling the error message turns up something about dbus.service (https://github.com/systemd/systemd/issues/5247). However, I don't seem to have a dbus.service file on my Neon machine:

Code: Select all

rob@neon-vm:~$ systemctl --user status dbus.service
Unit dbus.service could not be found.

Does anyone have any idea what is going on?

Thanks in advance.