v2.18.0 update gave black screen, then nothing.

Richard238

pi@magicmirror:~ $ cd ~/MagicMirror/modules
pi@magicmirror:~/MagicMirror/modules $ mv default default.new
pi@magicmirror:~/MagicMirror/modules $ sudo cp -r -p ~/MagicMirror.save/modules/* modules
cp: target 'modules' is not a directory

Tried it without the space…

pi@magicmirror:~/MagicMirror/modules $ sudo cp -r -p ~/MagicMirror.save/modules/*modules
cp: missing destination file operand after '/home/pi/MagicMirror.save/modules/*modules'
Try 'cp --help' for more information.
pi@magicmirror:~/MagicMirror/modules $

Richard238

@richard238

I have to leave shortly Sam.

Thank you for all your help with this today, I’ll try again tomorrow.

Richard.

sdetweil

@richard238 ok

you forgot the cd …

cd ..
# copy all the modules from old install (incl default) preserve ownership and dates, need sudo to copy git info 
sudo cp -r -p ~/MagicMirror.save/modules/* modules

Richard238

@sdetweil

Trying to rename config.js to sample,

Error when getting information for file “/home/pi/MagicMirror/config/config.js”: No such file or directory
Error renaming file /home/pi/MagicMirror/config/config.js: No such file or directory

Yet I can see it, I can query it for permissions…

Back tomorrow.
Richard.

sdetweil

@richard238 said in v2.18.0 update gave black screen, then nothing.:

Error when getting information for file “/home/pi/MagicMirror/config/config.js”

you need to copy from save

cd ~/MagicMirror.save/config
cp -p config.js ~/Magicmirror/config

Richard238

@sdetweil

Good morning Sam.

Tried that late yesterday, and yes, it works.
And this morning, I copied

custom.css

from

/home/pi/MagicMirror.save/css

to

/home/pi/MagicMirror/css

This too is working perfectly.

Is there anything else to do, housekeeping maybe, or is that it now?

sdetweil

@richard238 if everything is running ok then I think you are done, and can delete the
MagicMirror.save folder

Richard238

@sdetweil

Ok, I’ll do that then.

Do we know what the cause of all this was, was it something to do with a mismatch in versions of node and npm?

sdetweil

@richard238 no idea what caused it.

there clearly was an error somewhere in the upgrade process, maybe reported and missed, or unreported.

but can u send me the MagicMirror.save/installers/upgrade.log

Richard238

@sdetweil

That’s a huge file, what’s the best way to send it?