[Solved Upstream] When loading FC console shows: "connect failed: No such file or directory"

[tsadowski]

I am responsible for this. "connect failed..." is the error message from libspnav. There is no socket when the daemon is not running. It might be possible to avoid this message by checking before if the daemon is running but using the return value of spnav_open() is a check by benign failure.

I did not change the build behaviour on Linux. If libspnav is found, it is compiled in.

A nice option would be weak linking of libspnav but this is easy on Mac OSX but not on Linux. Here is a pointer:
https://github.com/opadron/weak-linking-demo

But is it really an issue?

Cheers, Torsten

[chrisb]

But is it really an issue?

It's not severe, but it is an issue. False positives are irritating and misleading and may obscure real issues.

[tsadowski]

Ok, I see the following options:
- Ask the Spnav developers nicely to remove the error message -> No hint when you want to know why it is not working
- Ask the Spnav developers nicely to add an extra error report function -> Could be the best solution
- Fork libspnav
- Check if the socket file is present before calling spnav_open() -> upstream code could change without notice, strange failure
- Using dlopen() -> error message when libspnav is present but daemon not running

I prefer the second option. Weak linking is not a full solution as the client library could be present on the system without the daemon running.

Cheers,
Torsten

[tsadowski]

I asked the spacenavd developer. The offending message is gone. This will be fixed when the distribution packages are updated.

Cheers,
Torsten

[Kunda1]

I asked the spacenavd developer. The offending message is gone. This will be fixed when the distribution packages are updated.

That is awesome news. Thank you! Any idea when they will be cutting a new release ?

[tsadowski]

I did ask for a new release but the maintainer declined. I created a git package in the Arch user repository.

Does someone know what the policies are for git packages in the different Linux distros?

Cheers, Torsten

[Kunda1]

I did ask for a new release but the maintainer declined. I created a git package in the Arch user repository.

When's the next release slated for ?

Does someone know what the policies are for git packages in the different Linux distros?

Maybe Kurt does?
I'm sure debian is out of the equation. not sure about Ubuntu. I bet the PPA would be fine pulling from Arch. I guess we could ask the different packagers over in the packaging subforum https://forum.freecadweb.org/viewforum.php?f=42

[tsadowski]

Releases of libspnav are very irregular. The last release (0.2.3) was 2014. The maintainer suggests either to use a specific git revision or to add the commit containing the wanted change to the package diffs.

https://sourceforge.net/p/spacenav/patches/8/

Cheers,
Torsten

[looo]

It's patched for the conda-forge package. So the warning shouldn't show up for the coming appimages:
https://github.com/conda-forge/libspnav ... 28be93e88e

[Kunda1]

Thank you @looo!