Updating my MagicMirror using @sdetweil's script.

[manu85340]

Hello, I can no longer update my MagicMirror using @sdetweil’s script; do you know why? I’m getting this message:
"update log will be in /home/pi/MagicMirror/installers/upgrade.log
doing test run = false

MagicMirror version 2.28.0 (July 1 2024), will not run on OS level buster, due to system limitations

you must upgrade to a newer release of the raspi OS at some point" Could you please help me? Thanks.

[sdetweil]

@manu85340 thanks , I just updated the text… good catch.
but it says everything…
running latest releases doesn’t work on buster

I recommend using my backup script to save your MM config and list of modules
with the backup command

see https://github.com/sdetweil/MagicMirror-backup-restore

setup the new sd card, <— do NOT write over your existing card til you have new system running
install MM, make sure it runs,

then restore your config and modules
with the restore command

[manu85340]

Thanks for the reply. I just reinstalled everything using your script, but I’ve run into something strange: my custom CSS file is no longer being recognized, and none of the settings inside it are taking effect. Do you know why?

[sdetweil]

@manu85340 in the new versions since 2.35, custom.css is in the config folder (all the user config stuff in one folder)

runtime should move it if found…
install puts an empty file there
upgrade moves it too

[manu85340]

@sdetweil Thanks Sam, I just saw your reply, and indeed I hadn’t noticed that a custom.css file had been created in config.js. Thanks for your help.

[sdetweil]

@manu85340 if you had used my backup/restore I would have put your custom.css in the right place

[manu85340]

@sdetweil Yes, you’re right—I tried to go too fast. I’ll know for next time. Thanks again for your help.

[sdetweil]

@manu85340 back up now, and when you make changes . Be ready in case

[manu85340]

@sdetweil I just updated MM using your script and it won’t start anymore; it stays on the Raspberry Pi desktop. Please help!

[sdetweil]

@manu85340 are you using pm2?

can you do

pm2 status

and

pm2 stop  xx

where xx is the number of the row of the application (MagicMirror)
usually 0
you can use either the name or the number

then
go to the MagicMirror folder

can you also do

lsb_release -a

do you know if the OS is running Wayland or x11 desktop

we changed the wayland startup , so…

[rabbit83ka]

i just updated to 2.38 via your script. Electron starts, but is only shown for a few seconds in fullscreen, then minimzed to the taskbar:
Latest PiOS (trixie) with wayland. Log doesn’t show anything after “launching electron”

[sdetweil]

@rabbit83ka If you click on that does it come on screen?

[rabbit83ka]

@sdetweil no

[manu85340]

@sdetweil I installed Debian Bookworm; I’m not sure if that’s what you’re asking for.

[sdetweil]

@manu85340 ok, lets try this

pm2 stop all
cd ~/MagicMirror
npm run start:x11

[rabbit83ka]

@sdetweil figured it out, nothing related to wayland. Somehow the udpated messed up the npm, removing it rm -rf node_modules package-lock.json and reinstalling with npm install fixed it

[sdetweil]

@rabbit83ka can you send the the
~/MagicMirror/installers/upgrade.log

same userid as here at gmail

messed up nvm? I should only updated node version if required…
nvm or n (node version of nvm)

[rabbit83ka]

@sdetweil just sent the log

[manu85340]

@sdetweil Someone told me to skip this line and it worked.```

cd ~/MagicMirror && npm install electron@43 --save-exact

[sdetweil]

@manu85340 where is that line? not in either of my scripts…