Blank black screen | Noob

KirAsh4

@amanzimdwini, I didn’t mention it … yet … because I like to figure out where the problem is, before I tell someone to start from scratch. :)

Arod192

@KirAsh4 Update Node.js and I’m still having the problem

Arod192

@KirAsh4 Okay I just changed the language from en to nl (just to see what’ll happen) and now it works!

But now everything is in the “nl” language but when I change it back to “en” the screen is black again

Arod192

@KirAsh4 Looks like all languages work but when I change the language to en I get a black screen

Arod192

@KirAsh4 Alright I think I fixed it. What I did was I went into the translations folder and I renamed en.js to en-us.js. After that I went into the config and changed en to en-us.

ronny3050

@Arod192 I can confirm this is a bug. Hardcoding ‘en’ in config.js causes black-screen, however, leaving it as ’ ’ or node serveronly runs fine.

overviewcs

noob here reporting same issue and same workaround works for me.

Exact Same issue and hardware and OS as poster. From a clean build, updated all before running MM auto installer as I thought I had made a mistake my first time around.

“used the automatic installer located here, https://github.com/MichMich/MagicMirror, and followed every step.
I’m using a Raspberry Pi 3 Model B.
I’m running Raspian Jesse 4.4, Node v4.4.3.
The MagicMirror is up-to-date”

server nodeonly -works
npm start -does not

changing ‘en’ to ‘’ in config.js works as a workaround. It will now open in electron.

KirAsh4

Odd bug, as I have two different rpi 3s running just fine with 'en' as the value. This makes me wonder … can any of you paste the contents of your ‘/usr/share/X11/locale/’ folder?

$ sudo ls -aF /usr/share/X11/locale/

smithdsl

Hey Everyone,
I was have the same issue. Change from ‘en’ to ’ ’ now it works.
@KirAsh4 this is my “locale” folder.

pi@raspberrypi:~ $ sudo ls -aF /usr/share/X11/locale/
./            fi_FI.UTF-8/       iso8859-11/  iso8859-6/    ja.SJIS/      locale.dir         sr_CS.UTF-8/   zh_CN.gb18030/    zh_TW.UTF-8/
../           georgian-academy/  iso8859-13/  iso8859-7/    km_KH.UTF-8/  microsoft-cp1251/  tatar-cyr/     zh_CN.gbk/
am_ET.UTF-8/  georgian-ps/       iso8859-14/  iso8859-8/    ko/           microsoft-cp1255/  th_TH/         zh_CN.UTF-8/
armscii-8/    ibm-cp1133/        iso8859-15/  iso8859-9/    koi8-c/       microsoft-cp1256/  th_TH.UTF-8/   zh_HK.big5/
C/            iscii-dev/         iso8859-2/   iso8859-9e/   koi8-r/       mulelao-1/         tscii-0/       zh_HK.big5hkscs/
compose.dir   isiri-3342/        iso8859-3/   ja/           koi8-u/       nokhchi-1/         vi_VN.tcvn/    zh_HK.UTF-8/
el_GR.UTF-8/  iso8859-1/         iso8859-4/   ja.JIS/       ko_KR.UTF-8/  pt_BR.UTF-8/       vi_VN.viscii/  zh_TW/
en_US.UTF-8/  iso8859-10/        iso8859-5/   ja_JP.UTF-8/  locale.alias  ru_RU.UTF-8/       zh_CN/         zh_TW.big5/
pi@raspberrypi:~ $

Thanks.

KirAsh4

And in the EN_US.UTF-8 folder? Is there stuff in there?

smithdsl

pi@raspberrypi:/usr/share/X11/locale/en_US.UTF-8 $ ls -aF
./ …/ Compose XI18N_OBJS XLC_LOCALE
pi@raspberrypi:/usr/share/X11/locale/en_US.UTF-8 $

KirAsh4

Yeah that’s odd, it’s the same on mine, so you do have en_US locale installed on the rpi. But why is MM² failing for you, when it’s working fine for me, that’s a bit of a mystery. If you don’t mind, just for grins, would you care to run through only Step 2 in this post: https://forum.magicmirror.builders/topic/236/complete-setup-tutorial/4, specifically the Internationalization part.

MichMich

This is a real strange situation. I tried it with different language setting, but none of them seem to cause an issue. (Even when using language: 'foobar', it just works fine.) Could one of you who is experiencing the bug, look in the developer’s console for any error messages?

ronny3050

@MichMich I think this has something to do with electron? Because everything runs fine on server only.

MichMich

I can’t really see how that’s affected. It’s just a variable that will be used to select the right file. I really need a log from the console to figure out what’s wrong.

smithdsl

@MichMich How do I dump the log file?

MichMich

It’s not the node log. It’s the console log you can see in the developers tools. A screenshot (with the red error messages) is enough.

MichMich

I just pushed a possible fix to the develop branch. Please let me know if this solves the issue.

dejayou

Hi MichMich- I am using the new develop branch and whatever the fix was is not working for me. I am still getting the blank black screen. I also wasn’t able to fix it with changing the naming conventions related to the language settings that worked for others.

MichMich

In your case its probably an other issue. Could you share your config.js (don’t forget to take out sensitive info)?