Closed rglory closed 11 months ago
robertsLando
commented
11 months ago @jmgiaever it should be as easy as adding this dep to the snapcraft: apt-get install libatomic1
You are already doing it for armhf but maybe it should be done for arm64 too: https://github.com/giaever-online-iot/zwave-js-ui/blob/main/snap/snapcraft.yaml#L182C20-L182C20
jmgiaever
commented
11 months ago apt-get install libatomic1
This won't help. But staging it as I've done it for the amrhf should do it.
I can't remember any longer why it was necessary for armhf in the past, but not arm64 (and amd64).
However it is strange if this is happening just on Raspbian?
It runs flawlessly on both Ubuntu Server arm64 and Ubuntu Core arm64.
sudo snap install zwave-js-ui --candidate@rglory You've followed the setup instructions for rasbian?
rglory
commented
11 months ago @jmgiaever > You've followed the setup instructions for rasbian?
Yes I did and this is not a new install. It used to work, but quite recently (though difficult to say exactly say when) stopped. I started to investigate and found this issue. Switching back to stable (I had to use candidate when upgraded home assistant) fixes this issue. And if I look through virtual filesystems I do see libatomic.so.1 now:
/snap/zwave-js-ui/287/usr/lib/arm-linux-gnueabihf/libatomic.so.1
When it was on candidate it was missing.
jmgiaever
commented
11 months ago Can you give it a shot now? Candidate channel
node: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory
Package is installed: libatomic1 is already the newest version (12.2.0-14+rpi1).
And googling this problem shows that is a problem with a snap.
Any help?
PS Switching to stable channel fixed the issue. Looks like this is problem of "candidate" version.