Mirror broken after v2.22.0 upgrade

[ecirpnaes]

Just upgraded to the latest MM version, and I’m getting an Electron error on startup.

Specifically… .node_modules/[…]/dist/electron: symbol lookup error: undefined symbol: gbm_bo_get_modifier.

I assumed I had some out of date core files, so I upgraded my core raspian OS, since I was sadly out of date, but no help. I tried rolling back Electron to the previous 19.1 version, but ran into other dependency issues.

Anyone else experiencing anything like this? I’m tempted to just take some time and do a clean install, but was hoping someone knew of a simpler fix.

[sdetweil]

@ecirpnaes ok, do this

cd ~/MagicMirror
rm -rf node_modules
npm install --omit=dev --no-audit --no-fund

i just did this on my pi4 after upgrading from 2.21

[sdetweil]

@ecirpnaes how did u upgrade?

[ecirpnaes]

@sdetweil Standard way. git pull & npm install

[sdetweil]

@ecirpnaes ok, do this

cd ~/MagicMirror
rm -rf node_modules
npm install --omit=dev --no-audit --no-fund

i just did this on my pi4 after upgrading from 2.21

[ecirpnaes]

@sdetweil Thanks!
I had already tried blowing away the node_modules and letting it rebuild doing a standard “npm install”, but hadn’t tried it with omitting the dev only files. That said, I just did it and still no go.

To be clear, the mirror will run with a “server only” option, so the error is clearly with a library file with electron.

/home/pi/MagicMirror/node_modules/electron/dist/electron: symbol lookup error: /home/pi/MagicMirror/node_modules/electron/dist/electron: undefined symbol: gbm_bo_get_modifier

I’ll try a few other things but I guess worse comes to worse, I can pull a clean image and just clone everything down again.

[sdetweil]

@ecirpnaes ok, what system are u running on?

lsb_release-a
uname -a

I did the install on pi os, and on Intel Linux.

what desktop are u running?
Wayland, x11, ??

[ecirpnaes]

@sdetweil
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.13 (stretch)
Release: 9.13
Codename: stretch

Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux

Honestly not sure what desktop it is running. I usually just putty into it from a windows machine.

[sdetweil]

@ecirpnaes ok stretch is too old for this latest electron

I think u have to move up to buster(release after stretch) as least

bullseye is the current

and another one coming soon… this year I think.

u might be able to backup,/restore using my scripts
https://github.com/sdetweil/MagicMirror-backup-restore

and use my script to install latest to restore config to.
https://github.com/sdetweil/MagicMirror_scripts

[ecirpnaes]

@sdetweil That sounds about right. It’s been a couple years since I’ve updated my base image. I assumed it was going to come to that sooner or later.
Thanks for the confirmation. I’ll definitely take a look at your scripts.

[Peter]

@sdetweil said in Mirror broken after v2.22.0 upgrade:

@ecirpnaes ok, do this

cd ~/MagicMirror
rm -rf node_modules
npm install --omit=dev --no-audit --no-fund

i just did this on my pi4 after upgrading from 2.21

Great!
Solved my problem too!
Thanks.
Peter