dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

the_2winz

@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

sdetweil

@the_2winz yes this

uname -a
file /bin/bash

I think you have a hybrid system… 64 bit kernel, 32 bit runtime

the_2winz

@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

sdetweil

@the_2winz hm can you do the
file command on the libnss3.so

the_2winz

@sdetweil like libnss3.so bin/bash/ ? i’m not sure i follow

sdetweil

@the_2winz

file /usr/lib/x86_64-linux-gnu/libnss3.so

mine says

/usr/lib/x86_64-linux-gnu/libnss3.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=53f5a8a185db3abf260b77ea560179a395b892e0, stripped

my /bin/bash says
/bin/bash: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=2a9f157890930ced4c3ad0e74fc1b1b84aad71e6, for GNU/Linux 3.2.0, stripped

the_2winz

@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

sdetweil

@the_2winz aha! you showed the 386 mode, not x64… SOOOOO that means electron is wrong… looking for the 64 bit library…

sdetweil

I would install Ubuntu instead of the raspian x86 image, which is a mess.

the_2winz

@sdetweil i think i will just lean on the browser feature - npm run server seems to work. thanks for all your help!