Read the statement by Michael Teeuw here.
First start from the mirror does not work
-
Maybe I’m missing something here, but it seems you try to run
npm start
from a remote shell. That does not work since it doesn’t know on which screen to start. Try:DISPLAY=:0 npm start
-
@MichMich Hi! I am running npm start directly on the pi, and I get the same exact error.
-
-
Interesting as I didn’t have to do that as a separate step. However, as I posted in a different thread yesterday, keeping the base software on your Raspberry Pi is important.
-
Mhh maybe we should add those dependencies and/or
apt-get upgrade
to the installer script? -
I vote no because that’s outside the scope of MM. However, we could adjust the installer to pause and ask the user if they have performed an update/upgrade on their base rpi before continuing on with the MM install. This gives the user an opportunity to exit the installer and do the requires prerequisites before returning to the installer (at which point they can then say ‘yes’ to the question.)
-
@KirAsh4 I did the manual install for mine anyways, but I could have sworn I did an update / upgrade but I may be wrong.
Maybe it’s something that can just be added to the install instructions as a small note.
-
You know, I have a spare rpi-3 sitting at home. I’ll wipe it clean and start fresh when I get home later and see if I run into issues. All in the name of science!
-
@KirAsh4 haha alright go for it! Let us know what comes of it.
-
Will do. Right after I inspect the 3D print that I left going since last night, and I start the next print. And after I swap a laptop with a friend. And after I have dinner. And after I help another friend with their phone. And after i do some laser cutting of mock up pieces for an art piece. And after I dig up the electronic bits I need for a kid’s costume. And after I … and after … and … oh you’ll hear from me some time in 2036. Really, I promise.
(Is there ever such a thing as having too many projects going at the same time?)