Bullseye

[bert269]

Ok, run your install script. This time it worked. The screensaver interfered - but I can fix that. This is what I saw during install
Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v14.0.0
Installed Node version: v17.1.0
No Node.js upgrade necessary.
Check current NPM installation …
NPM currently installed. Checking version number.
Minimum npm version: V6.0.0
Installed npm version: V8.1.2
No npm upgrade necessary.
Cloning MagicMirror …
Cloning into ‘MagicMirror’…
remote: Enumerating objects: 325, done.
remote: Counting objects: 100% (325/325), done.
remote: Compressing objects: 100% (290/290), done.
remote: Total 325 (delta 53), reused 146 (delta 22), pack-reused 0
Receiving objects: 100% (325/325), 477.94 KiB | 330.00 KiB/s, done.
Resolving deltas: 100% (53/53), done.
Cloning MagicMirror Done!
touch: cannot touch ‘/etc/chromium-browser/customizations/01-disable-update-check’: No such file or directory
tee: /etc/chromium-browser/customizations/01-disable-update-check: No such file or directory
Installing dependencies …
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘eslint-plugin-jsdoc@36.1.1’,
npm WARN EBADENGINE required: { node: ‘^12 || ^14 || ^16’ },
npm WARN EBADENGINE current: { node: ‘v17.1.0’, npm: ‘8.1.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@es-joy/jsdoccomment@0.10.8’,
npm WARN EBADENGINE required: { node: ‘^12 || ^14 || ^16’ },
npm WARN EBADENGINE current: { node: ‘v17.1.0’, npm: ‘8.1.2’ }
npm WARN EBADENGINE }
Dependencies installation Done!
Check plymouth installation …
Splashscreen: Checking themes directory.
Splashscreen: Create theme directory if not exists.

Splashscreen: Changed theme to MagicMirror successfully.
Do you want use pm2 for auto starting of your MagicMirror (y/N)?y
install and setup pm2
Created symlink /etc/systemd/system/multi-user.target.wants/pm2-pi.service → /etc/systemd/system/pm2-pi.service.
[PM2] Spawning PM2 daemon with pm2_home=/home/pi/.pm2
[PM2] PM2 Successfully daemonized
[PM2][WARN] Applications MagicMirror not running, starting…
[PM2] App [MagicMirror] launched (1 instances)
┌─────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ default │ 2.17.1 │ fork │ 4352 │ 0s │ 0 │ online │ 0% │ 2.7mb │ pi │ enabled │
└─────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
[PM2] Saving current process list…
[PM2] Successfully saved in /home/pi/.pm2/dump.pm2
Do you want to disable the screen saver? (y/N)?y
xscreensaver running
grep: /home/pi/.xscreensaver: No such file or directory
bash: line 587: [: !=: unary operator expected

We’re ready! Run pm2 start MagicMirror from the ~/MagicMirror directory to start your MagicMirror.

pi@piMirror:~ $ cd MagicMirror/
pi@piMirror:~/MagicMirror $ pm2 start MagicMirror
[PM2] Applying action restartProcessId on app [MagicMirror](ids: [ 0 ])
[PM2] MagicMirror ✓
[PM2] Process successfully started
┌─────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ default │ 2.17.1 │ fork │ 4551 │ 0s │ 1 │ online │ 0% │ 2.7mb │ pi │ disabled │
└─────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

[sdetweil]

@bert269 said in Bullseye:

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.