Bullseye

sdetweil

Minimum Node version: v14.0.0
Installed Node version: v17.1.0

no worky on node 17

bert269

it seems fine - it works for me with 17.1. I do not know which modules witll fail/break, but the vanilla config.js brought up MagiMirror2.

Thanks - let me know if you do need any more info I supply/help with.

bert269

Something seems off with the screensaver stop script too:
pi@piMirror:~ $ bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/screensaveroff.sh)”
xscreensaver running
grep: /home/pi/.xscreensaver: No such file or directory
bash: line 42: [: !=: unary operator expected

I guess there is a lot involved with the fact that they changed from fkms to kms

sdetweil

@bert269 thanks will fix

bert269

@sdetweil No problem - thank you for the help and support. I will attach the install.log - if you still need that.[0_1636743781431_install.log.txt](Uploading 100%)

sdetweil

@bert269 don’t attach here… attach to the issue in github

bert269

@sdetweil ok Sorry (is that why it’s not working…oops!)

BKeyport

@sdetweil I don’t think you’re gonna be able to get around it.

Manual install is failing too - apparently there’s a file in several packages that’s being locked by the system and causing errors in the nodejs installer.

dpkg: error processing archive /var/cache/apt/archives/nodejs_14.18.1-deb-1nodesource1_armhf.deb (--unpack):
 trying to overwrite '/usr/share/doc/nodejs/api/embedding.json.gz', which is also in package nodejs-doc 12.22.5~dfsg-2~11u1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/nodejs_14.18.1-deb-1nodesource1_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any further installs will require this to finish, which won’t because of this error, etc.

nmwust

@bkeyport
Any chance you are using a full image and not a basic image. Thinking it may be related to the nodeRed install on the full image that is not there on the basic image. I hit what i think was the same error on a full image and had no problems if i swapped cards and went back to a basic image.

sdetweil

@bkeyport yeh, I installed nvm, then installed 14 and it was ok… then switched to 17 with nvm and its ok…

not sure how to correct script yet