First start from the mirror does not work

mochman

@samydp all you should have to do is change the language portion of your config.js from
language: 'en', -> language: 'de',

As for the rest of your modules, I recommend adding them one by one to your config.js file to make sure they work. If you get that electron.js error, it was on the module you just added.

-Luke

samydp

Many thanks for your help and your tip! but only tow module works =( the clock an the compliments why this ?
Whenever I will add another module of the screen black!
i have install the electron.js again but
the add the module as in the proceeds described readme does not work !

mochman

Beats me, did you run npm install in the MagicMirror folder?

samydp

yes i have install the npm in the MM Folder , only compliment, clock and news works other moduls come a error ( no config file )

EoF

Hi I am having this same issue. Did you ever get it working?

MichMich

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

EoF

@MichMich Hi! I am running npm start directly on the pi, and I get the same exact error.

EoF

As an update to my situation, I was able to get mine working by installing electron dependencies.

sudo apt-get install libgtk2.0-0 libnotify4 libgconf2-4 libnss3

I am running a pi 3 with Jessie by the way.

FYI @MichMich @paviro

KirAsh4

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.

paviro

Mhh maybe we should add those dependencies and/or apt-get upgrade to the installer script?

KirAsh4

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

EoF

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

KirAsh4

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!

EoF

@KirAsh4 haha alright go for it! Let us know what comes of it.

KirAsh4

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?)

EoF

@KirAsh4 Haha I know that feeling!

KirAsh4

Ok, I finally had time last night to run through a complete setup and install, from taking the rpi out of its box to having MM up and running. I did not have to manually install any of the aforementioned packages. Which makes me wonder, @EoF, were you running the full Jessie distribution, or Jessie-Lite? If it’s Jessie-Lite, you would’ve had to install a lot more than just those few pieces as it does not come with an X-server.

Anyway, I’ll have a step-by-step tutorial written up soon …hmm, let’s check calendar … oh yeah, some time in 2036.

EoF

@KirAsh4 Hi! Glad you finally got around to testing this! I did in fact use the lite version of Jessie, so that would explain it then.

KirAsh4

Right, the lite version wouldn’t have any of those packages installed, nor would it have an X-server, so you would’ve had to do that yourself. :)

A Former User

I had the same erorr and I did use the full Jessie distribution. In my case “npm start” showed the same error but the problem was before at “npm install”.

I never really took the time to watch the entire npm install routine, because it took a while. I had my rasbperry connected via usb on my tv. And while running npm install it rebooted! So in my case it was caused by an inadequate power supply. Switched to a plug and everything worked fine.

Perhaps somebody runs into the same error like me.