Oahu, Hawaii, USA

@sdetweil
My problem is resolved. I upgraded to bullseye and reinstalled the mirror. I used your alternative install script vs cloning manually. It worked flawlessly setting up the mirror and the pm2 autostart. So many thanks for that.

I think I spent more time getting the mirror to rotate properly than anything else. File locations have changed for bullseye vs some of the older versions so it took a little hunting around to get things configured.
But all good now. Thanks again!

@ecirpnaes Never mind. I found it. I was looking for a file and then realized it was the command line config. DOH. If anyone else needs to enable the OpenGL driver just…
sudo raspi-config
Go to Advanced Options->GL Driver

@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.

@Peter
I followed the instructions on this page.
https://github.com/MichMich/MagicMirror/wiki/Configuring-the-Raspberry-Pi#enable-the-open-gl-driver-to-decrease-electrons-cpu-usage

They’re a little outdated because they deal with older versions also but the basic information is there.

Essentially, it seems that the Open GL driver is enabled by default now, so I had to:

sudo nano /etc/xdg/lxsession/LXDE-pi/autostart
and added the following line.

@xrandr --output HDMI-1 --rotate right

@Knight Your problem is the exact same as what I had.
Same error message.
Same outdated OS.

The fix is to back up your config file(s), update your OS to the latest (bullseye), reinstall the mirror software and any custom modules.

Sam has a bunch on scripts in git repo that make this a very simple operation. Took me less than an hour, with the vast majority of that waiting for package files to download.

@sdetweil
My problem is resolved. I upgraded to bullseye and reinstalled the mirror. I used your alternative install script vs cloning manually. It worked flawlessly setting up the mirror and the pm2 autostart. So many thanks for that.

I think I spent more time getting the mirror to rotate properly than anything else. File locations have changed for bullseye vs some of the older versions so it took a little hunting around to get things configured.
But all good now. Thanks again!

@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.

@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 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 Standard way. git pull & npm install

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.

@d3r This.
I had the same issue on a Pi 2. Starting in safe mode (repeatedly mashing the Shift key on boot) got me up. Editing the boot config.txt file and commenting out the lines that get added when you enable the Open GL driver fixed things.

@ecirpnaes Never mind. I found it. I was looking for a file and then realized it was the command line config. DOH. If anyone else needs to enable the OpenGL driver just…
sudo raspi-config
Go to Advanced Options->GL Driver