Forum Replies Created
March 21, 2019 at 08:59 in reply to: Connection fails on headless client #21800
I bow to you mighty Linux-Wizard 🙂 I’m only guessing what your magic does but I’m thankful that it solved my problem!March 20, 2019 at 09:15 in reply to: Connection fails on headless client #21789
There seems to be a issue with some tray icons, though. NoMachine icon appears as nxclient.bin and its context menu looks different from the usual login session. But the main problem is that some other icons are missing completely which makes my cloud storage app inaccessible. Do you have a clue what the reason could be?March 19, 2019 at 10:18 in reply to: Connection fails on headless client #21784
It finally connects! Changing su to system-(remote-)login and removing dbus-launch worked 😀 Thank you soooooooooo much graywolf!!!March 18, 2019 at 09:18 in reply to: Connection fails on headless client #21773
I think the issue is somehow related to Arch since it doesn’t work on Antergos and Manjaro (both based on Arch) with multi-user.target either.
It even won’t connect successfully after starting the display manager until nxserver is restarted manually.
After trying almost every change I could find that might be related to this problem I’m really out of ideas 🙁March 15, 2019 at 15:35 in reply to: Connection fails on headless client #21761
startkde: Starting up... dbus-update-activation-environment: error: unable to connect to D-Bus: Failed to connect to socket /tmp/dbus-t7CoXdBU1J: Connection refused startkde: Could not sync environment to dbus.
Mar 15 14:00:49 V5 audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 15 14:00:49 V5 dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1' (uid=981 pid=378 comm="/usr/lib/systemd/systemd-networkd ") Mar 15 14:02:35 V5 systemd: dbus.socket: Succeeded.