You can compile the daemon without Xlib, but it won't be compatible with applications that where written for the original proprietary 3Dconnexion driver (e.g. maya, houdini, etc). The 3dxsrv compatibility interface needs to communicate with clients through the X window system. Programs designed to work with the alternative spacenavd-specific interface however (e.g. blender) will work fine even when spacenavd is built without X11 support.
spnavd_ctl, which SideFX lists as a step in their guide (above), produces the following error:You must have an X server running before starting up spacenavd-X11 events.
spnavd_ctlis just a bash script, which runs xdpyinfoto look for an X server. After installing xdpyinfothe script still complains with the same error, but this time because it´s looking for a display at ":0". My display is apparently at ":1", for some reason, according to xdpyinfo. I tried updating spnavd_ctlto use ":1" instead, causing it to run successfully, but with Houdini still not recognizing the space mouse. It might be an assumption that the display is at ":0" so I must figure out how to change this.
/var/log/spnavd.log, after starting the daemon, the log says:failed to open X11 display ":0.0"
src/proto_x11.ccompiled in spacenavd, with the code:/* if the server started from init, it probably won't have a DISPLAY env var * so let's add a default one. */ if(!getenv("DISPLAY")) { putenv("DISPLAY=:0.0"); }
spacenavdassumes ":0.0", which is wrong in my case.
systemdinstead of init.d, I had to add the following line to my /etc/systemd/system/spacenavd.serviceunder the section [Service]:Environment=DISPLAY=:1
spnavd_ctlprogram must be running in addition to the spacenavddaemon.
Don't forget to update the display in the /usr/local/bin/spnavd_ctl file sudo cp contrib/systemd/spacenavd.service /etc/systemd/system/
[rob@customer bin]$ who rob :1 2025-02-05 09:59 (:1)
[Service] Type=forking PIDFile=/var/run/spnavd.pid ExecStart=/usr/local/bin/spacenavd StandardError=syslog Environment=DISPLAY=:1
..... if [ "$2" = 'start' ]; then # check to see there is a local X server running. DISPLAY=":1" .....
sudo systemctl enable spacenavd
sudo systemctl start spacenavd
/usr/local/bin/spnavd_ctl x11 start -v
spacenavdis started as root (as a service), it can't access the user X server, and Houdini can't talk to it ("failed to open X11 display"in /var/log/spnavd.log).spacenavdmanually, it works fine. But I want it running as a service.spacenavdas a user service, it fails due to lacking permission to (create?) the socket file in /var/run/spnav.sock.spacenavdas a service (root), but give root access to the user X server. To do this on each login I added the following to ~/.zlogin:xhost +si:localuser:root > /dev/null
~/.profileinstead.spacenavdcode to handle the socket file differently.
johnmather
If it's started through systemd, you could try telling it to run the service as your user. You can addUser=usernameunder[Service]in the service unit definition.
spacenavdmanually as the same user.
kimsnarf
xhost +si:localuser:root > /dev/null
