Invoking snap outputs `connect failed: No such file or directory` right from the start

[luzpaz]

Right after invoking FreeCAD Snap (edge, haven't tested on stable yet but it's probably there too) I see the following output to the terminal:
connect failed: No such file or directory

Is this a addon manager issue; a spacenav issue or something else entirely ?

OS: Ubuntu Core 22 (KDE/plasma/xcb)
Architecture: x86_64
Version: 1.1.0dev.39748 (Git) Snap 1244
Build type: Release
Branch: main
Hash: e977eb49e37ef836f695809263fa1f56a17cc657
Python 3.10.12, Qt 5.15.10, Coin 4.0.0, Vtk 7.1.1, OCC 7.7.1
Locale: English/United States (en_US)
Stylesheet/Theme/QtStyle: FreeCAD Dark.qss/FreeCAD Dark/Fusion

[luzpaz]

Possibly related:

• Old spaacenavd bug untrapped file error on start up due to spacenavd FreeCAD#5947
• Addon Manager/Github AddonManager: Checking Connection to github connect failed AddonManager#18

[luzpaz]

I cannot reproduce on AppImage, but still happens on Snap

OS: Manjaro Linux (KDE/plasma/xcb)
Architecture: x86_64
Version: 1.1.0dev.39750 (Git) Conda AppImage
Build type: Release
Branch: main
Hash: 7b548bee7f781837640df96831a3e7a7cfa4cf9b
Python 3.11.9, Qt 5.15.13, Coin 4.0.3, Vtk 9.2.6, OCC 7.7.2
Locale: English/United States (en_US)
Stylesheet/Theme/QtStyle: FreeCAD Dark.qss/FreeCAD Dark/Fusion

[furgo16]

I don't see this on my laptop, but I do on my desktop. I don't have any spacenav hardware.

[chennes]

The hardware doesn't matter: what version of libspnav is being used here in the snap? The output was fixed upstream in their 1.0 release.

ETA: to answer my own question, 0.2.3, a known-bad libspnav version. So this will fix itself when we stop using Ubuntu 22.04 (core22) as our snap build system.