EDIT @ 2020 07 04 1527 US Central Time: Added contents of VNC Server .service file.
I'm running a headless Manjaro install on my Raspberry Pi 4b (4 GB). I've run a system update and have the latest stable everything installed.
I'm attempting to install TigerVNC in headless System mode, using the instructions here: https://wiki.archlinux.org/index.php/TigerVNC
The installation seems to have worked as the wiki said it should (the VNC server is visible as a running server in systemctl), but I get the following error(s) whenever I boot the system.
I think there's 1 or 2 errors here.
TigerVNC runs its own Xserver. From the wiki: "It is both a VNC server and an X server with a virtual framebuffer. This means it is similar to the standard X server but has a virtual screen rather than a physical one. The virtual server runs in parallel with the physical X server should one be running." Is it possible XFCE is trying to start its own Xserver and choking because TigerVNC already heas one up and going? If so, how do I fix it?
"Unable to Connect to DBUS." I'm still new enough not to understand exactly what a DBUS is, but I do understand it has something to do with connecting to virtual devices (like an X server). Not being able to connect seems like a fatal error. What should I do to fix this?
Sat Jul 4 13:43:48 2020
vncext: VNC extension running!
vncext: Listening for VNC connections on local interface(s), port 5901
vncext: created VNC server for screen 0
The XKEYBOARD keymap compiler (xkbcomp) reports:
Internal error: Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server
> /usr/bin/startxfce4: X server already running on display :1
> Failed to connect to bus: No such file or directory
> dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
vncserver@.service looks like this:
Description=Remote desktop service (VNC)
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :; /bin/dbus-launch'
ExecStart=/usr/bin/vncserver %i -geometry 1920x1080 -alwaysshared
ExecStop=/usr/bin/vncserver -kill %i
I modified it to try to force it to do dbus-launch before starting the service, but that did not change anything.
> │ └─vncserver@:1.service
│ ├─337 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
│ ├─350 /usr/bin/Xvnc :1 -alwaysshared -desktop sandbox -geometry 1920x1080 -localhost -securitytypes vncauth,tlsvnc -auth /home/panoptitom/.Xauthority -pn -rfbauth /home/$HOME/.vnc/passwd -rfbport 5901 -rfbwait 30000 -alwaysshared
│ └─411 xfce4-session
xstartup looks like this:
If I'm reading this right, XFCE4-session is actually running as PID 411.
I see that I'm actually unsetting DBUS_SESSION_BUS_ADDRESS, which is what the TigerVNC wiki entry says to do, which I'm guessing is my problem, but I don't yet know enough about how this works to guess at fixing it.
However, commenting out "unset DBUS_SESSSION_ADDRESS" had no impact. Error remains.