@sdetweil i think i will just lean on the browser feature - npm run server seems to work. thanks for all your help!
Read the statement by Michael Teeuw here.
Best posts made by the_2winz
-
RE: dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
Latest posts made by the_2winz
-
RE: dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
@sdetweil i think i will just lean on the browser feature - npm run server seems to work. thanks for all your help!
-
RE: dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
@sdetweil rob@raspberry:~/MagicMirror $ file /usr/lib/i386-linux-gnu/libnss3.so
/usr/lib/i386-linux-gnu/libnss3.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=f3a5e41927cedc2024ae8cdc9a00bd699cd14278, stripped -
RE: dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
@sdetweil looks like it.
rob@raspberry:~/MagicMirror $ uname -a
Linux raspberry 5.10.0-15-amd64 #1 SMP Debian 5.10.120-1 (2022-06-09) x86_64 GNU/Linux
rob@raspberry:~/MagicMirror $ file /bin/bash
/bin/bash: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=56307740a4c93a51d04f9511eae7897e52a4ddb5, for GNU/Linux 3.2.0, stripped -
RE: dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
@sdetweil i was able to add it to the electron/dist/ directory but when i run npm run start, now i get this error /home/rob/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libnss3.so: wrong ELF class: ELFCLASS32
-
RE: dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
@sdetweil i cp to the right dir… but now when i run npm run start i get the following error > magicmirror@2.25.0 start
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js
/home/rob/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libnss3.so: wrong ELF class: ELFCLASS32
-
RE: dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
@sdetweil rob@raspberry:/usr/lib/x86_64-linux-gnu $ find libnss3.so
find: ‘libnss3.so’: No such file or directory -
RE: dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
@sdetweil still get this
rob@raspberry:~/MagicMirror $ npm run startmagicmirror@2.25.0 start
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js/home/rob/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
-
RE: dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
@sdetweil I found this Install libnss3 deb package: sudo apt-get install libnss3, but get this: /usr/lib/x86_64-linux-gnu $ sudo apt-get install libnss3
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
libnss3 is already the newest version (2:3.61-1+deb11u3).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. -
RE: dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
@sdetweil both actually. I ran npm run install-mm, then i ran your upgrade-script.sh got this Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v20.8.0
Installed Node version: v20.8.0
No Node.js upgrade necessary.
Check current NPM installation …
NPM currently installed. Checking version number.
Minimum npm version: V10.1.0
Installed npm version: V10.2.3
No npm upgrade necessary.upgrading from version 2.25.0 to 2.25.0
fetching latest revisionsChecking for modules with removed libraries
no modules found needing npm refresh