You are not logged in.
Hi, I have been trying to set up x2goserver, but I have run into an error. After I login to the remote host and the black x2go window appears, I get this error:
Could not connect to session bus: Failed to connect to socket /tmp/dbus-oaRtKt4T3n: Connection refused
I can get xeyes to run using X forwarding, but terminator gives this error:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
systemctl shows that Dbus is running:
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
Active: active (running) since Thu 2017-05-25 19:12:54 EEST; 1h 12min ago
Docs: man:dbus-daemon(1)
Main PID: 524 (dbus-daemon)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/dbus.service
└─524 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activationMay 25 19:12:54 stavros-pc systemd[1]: Started D-Bus System Message Bus.
May 25 19:12:54 stavros-pc dbus[524]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
May 25 19:12:55 stavros-pc dbus[524]: [system] Successfully activated service 'org.freedesktop.hostname1'
May 25 19:12:56 stavros-pc dbus[524]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
May 25 19:12:56 stavros-pc dbus[524]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service not found.
May 25 19:12:58 stavros-pc dbus[524]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
May 25 19:12:59 stavros-pc dbus[524]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
May 25 19:13:02 stavros-pc dbus[524]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
May 25 19:13:02 stavros-pc dbus[524]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
How can I get x2goserver to work? Also, is this an x2go-specific error, or just a misconfigured Dbus/systemd?
Thanks in advance.
EDIT:
Running systemctl --user gives:
stavros@stavros-pc ~> systemctl --user
Failed to connect to bus: No such file or directory
The systemd service user@1000 does not start automatically. But even when started manually, the same errors appear.
This is the journalctl --user log right after trying to connect via x2go:
stavros@stavros-pc /v/l/j/8a9ddc0561eb45ee8c5c6fea03c547d4> journalctl --user
-- Logs begin at Fri 2017-05-26 01:37:16 EEST, end at Fri 2017-05-26 01:37:33 EEST. --
May 26 01:37:16 stavros-pc /usr/bin/x2gostartagent[3421]: successfully started X2Go agent session with ID stavros-51-1495751834_stDCINNAMON_dp24
May 26 01:37:21 stavros-pc /usr/bin/x2gomountdirs[3632]: successfully mounted stavros@127.0.0.1:58300/home/stavros/shared to /tmp/.x2go-stavros/media/disk/_home_stavros_shared
May 26 01:37:22 stavros-pc /usr/bin/x2gomountdirs[3632]: successfully mounted stavros@127.0.0.1:58300/home/stavros/.x2go/S-stavros-51-1495751834_stDCINNAMON_dp24/spool to /tmp/.x2go-stavros/spool/C-stavros-51-1495751834_stDCINNAMON_dp24
May 26 01:37:25 stavros-pc /usr/bin/x2gosetkeyboard[3802]: Setting X keyboard according to /home/stavros/.x2go/C-stavros-51-1495751834_stDCINNAMON_dp24/keyboard
May 26 01:37:27 stavros-pc cinnamon-session[3727]: WARNING: t+0.00009s: Could not make bus activated clients aware of DISPLAY=:51 environment variable: Failed to connect to socket /tmp/dbus-2KDFD3y6XG: Connection refused
May 26 01:37:27 stavros-pc cinnamon-session[3727]: WARNING: t+0.00017s: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Failed to connect to socket /tmp/dbus-2KDFD3y6XG: Connection refused
May 26 01:37:27 stavros-pc cinnamon-session[3727]: WARNING: t+0.00020s: Could not make bus activated clients aware of QT_QPA_PLATFORMTHEME=qt5ct environment variable: Failed to connect to socket /tmp/dbus-2KDFD3y6XG: Connection refused
May 26 01:37:27 stavros-pc cinnamon-session[3727]: WARNING: t+0.00029s: Could not make bus activated clients aware of GTK_OVERLAY_SCROLLING=1 environment variable: Failed to connect to socket /tmp/dbus-2KDFD3y6XG: Connection refused
May 26 01:37:27 stavros-pc cinnamon-session[3727]: WARNING: t+0.00314s: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
May 26 01:37:32 stavros-pc /usr/bin/x2goumount-session[3941]: successfully unmounted "/tmp/.x2go-stavros/media/disk/_home_stavros_shared"
May 26 01:37:33 stavros-pc /usr/bin/x2goumount-session[3941]: successfully unmounted "/tmp/.x2go-stavros/spool/C-stavros-51-1495751834_stDCINNAMON_dp24"
It says something about GNOME and a deprecated variable, however I am using Cinnamon, and have selected the Cinnamon option from x2go.
There is a problem with systemd-logind. Below it shows that it's stuck activating. I tried restarting it but the process hanged and I had to ^C.
stavros@stavros-pc /v/l/j/8a9ddc0561eb45ee8c5c6fea03c547d4> sudo systemctl status systemd-logind
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
Active: activating (start) since Fri 2017-05-26 01:43:33 EEST; 34s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Softwar … /multiseat
Main PID: 4477 (systemd-logind)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
CGroup: /system.slice/systemd-logind.service
└─4477 /usr/lib/systemd/systemd-logindMay 26 01:43:33 stavros-pc systemd[1]: Starting Login Service...
May 26 01:43:33 stavros-pc systemd-logind[4477]: New seat seat0.
May 26 01:43:33 stavros-pc systemd-logind[4477]: Watching system buttons on /dev/input/event6 (Power Button)
May 26 01:43:33 stavros-pc systemd-logind[4477]: Watching system buttons on /dev/input/event5 (Power Button)
May 26 01:43:33 stavros-pc systemd-logind[4477]: Watching system buttons on /dev/input/event8 (Eee PC WMI hotkeys)
stavros@stavros-pc /v/l/j/8a9ddc0561eb45ee8c5c6fea03c547d4> sudo systemctl restart systemd-logind
Then I tried starting it again, it froze, and the service is stuck activating again.
stavros@stavros-pc /v/l/j/8a9ddc0561eb45ee8c5c6fea03c547d4> sudo systemctl start systemd-logind
^C⏎ stavros@stavros-pc /v/l/j/8a9ddc0561eb45ee8c5c6fea03c547d4> sudo systemctl status systemd-logind
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
Active: activating (start) since Fri 2017-05-26 01:47:15 EEST; 21s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Softwar … /multiseat
Main PID: 4730 (systemd-logind)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
CGroup: /system.slice/systemd-logind.service
└─4730 /usr/lib/systemd/systemd-logindMay 26 01:47:15 stavros-pc systemd[1]: Starting Login Service...
May 26 01:47:15 stavros-pc systemd-logind[4730]: New seat seat0.
May 26 01:47:15 stavros-pc systemd-logind[4730]: Watching system buttons on /dev/input/event6 (Power Button)
May 26 01:47:15 stavros-pc systemd-logind[4730]: Watching system buttons on /dev/input/event5 (Power Button)
May 26 01:47:15 stavros-pc systemd-logind[4730]: Watching system buttons on /dev/input/event8 (Eee PC WMI hotkeys)
EDIT 2:
After a few reboots systemd-logind starts normally and doesn't get stuck even when doing a systemctl restart systemd-logind.service. No other progress however, I still get the same errors as before.
Output of loginctl:
[stavros@stavros-pc pam.d]$ loginctl
SESSION UID USER SEAT TTY0 sessions listed.
EDIT 3:
Issue still persists when creating new user.
EDIT 4: Output of env:
[stavros@stavros-pc ~]$ env | grep -i dbus
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-NZ52GQGkFM,guid=8739262522a44c8086a7614059a56532
DBUS_SESSION_BUS_PID=30251
I also noticed that the bus address is different on my newer installation:
[stavros@souvlakia stavros]$ env | grep -i dbus
TERMINATOR_DBUS_NAME=net.tenshu.Terminator20x1a6021154d881c
TERMINATOR_DBUS_PATH=/net/tenshu/Terminator2
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
/run/user/1000 exists on the newer arch install but not on the one I'm having the problem. I'm sure it's some kind of config error but there are no .pacnew files.
Last edited by stavrakis (2017-08-29 13:27:32)
Offline
System message bus != session message bus.
I don't know much about x2goserver, but undoubtely the problem is that you don't have a working session dbus. Session d-bus is for inter-application communication running in a user's login session. It seems though, through recent experiments, that all of a user's sessions may now share the same d-bus. System d-bus is used for things that need to communicate across multiple users and system processes. dbus-launch might be all you need in this case, run it first. Your problems are probably similar to this : https://serverfault.com/questions/40551 … ng-on-exit
Last edited by ewaller (2017-05-25 17:44:06)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
I have edited the first post. Apparently systemd-login is getting stuck when starting. I have no idea what the cause is, though.
Offline
It turns out systemd-logind does start normally now but the errors remain. Also, no user sessions are listed with loginctl.
Offline
Tried creating a new user, but the same error persists. Is there anything I can do to fix it?
Offline