Electron not starting on Raspberry Pi #145

MichMich · 2016-04-06T15:00:23Z

I just installed a Raspberry Pi with a clean Jessie installation to give MM2 a try.
Unfortunately, the app will not start, and doesn't give any errors of feedback.

See image below. Any ideas, @paviro & @nhubbard?

paviro · 2016-04-06T16:48:07Z

Strange, maybe try npm config set loglevel silly and see if you get any output then?

MichMich · 2016-04-07T07:37:01Z

No real helpful information.

MichMich · 2016-04-07T08:07:34Z

I've tried the Electron Quick Start, but that seems to have the same issue. I opened an issue in the Electron repository: electron/electron#5069

nhubbard · 2016-04-08T01:27:46Z

That's odd. Never have I seen a Node app that crashes without a stack trace.

MichMich · 2016-04-08T08:09:34Z

It doesn't even seem to crash. It exits with code 0. But it's an Raspberry Issue, since the Electron Quick Start does the same.

paviro · 2016-04-08T08:57:49Z

Strange, that it works without any Problems for me...

Am 08.04.2016 um 10:09 schrieb Michael Teeuw [email protected]:

It doesn't even seem to crash. It exits with code 0. But it's an Raspberry Issue, since the Electron Quick Start does the same.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

MichMich · 2016-04-08T09:36:53Z

@paviro Which RPi are you using? 2 or 3? On the Electron issue they said it had something to do with the RPi type: electron/electron#5069

paviro · 2016-04-08T09:37:35Z

Pi 2 with Jessie.

Am 08.04.2016 um 11:36 schrieb Michael Teeuw [email protected]:

electron/electron#5069 electron/electron#5069

MichMich · 2016-04-08T09:38:30Z

That's strange indeed. I'm using the same Pi. :-/

paviro · 2016-04-08T09:39:26Z

Yeah figured so, that's what I don't get... Does not make any sense.

Am 08.04.2016 um 11:38 schrieb Michael Teeuw [email protected]:

That's strange indeed. I'm using the same Pi. :-/

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub #145 (comment)

MichMich · 2016-04-08T18:38:31Z

@pavario, so I did another reinstall. Again without succes. Besides the magic mirror installer, I did not run any other installers.

I'm running: 2016-03-18-raspbian-jessie
Node: v5.10.1
GPU memory: 256MB

Any differences between the above and your situation?

paviro · 2016-04-08T19:03:14Z

Seems to be the same thing I did. Well I installed node via apt-get before but removed it again. Could be that I am running node 4 but I have to check if I really do, give me a sec.
Well seems like I installed v4.0.0 maybe try that version and see if it works?

MichMich · 2016-04-08T19:19:22Z

Same problem with v4.0.0.

But how can it be that you are running v4.0.0 if you used the installer?

paviro · 2016-04-08T19:52:25Z

There was no installer when I installed it but I did the same things the installer does just with the older node version.

MichMich · 2016-04-08T20:02:54Z

If you have an empty card laying around, would you mind trying the installer on a clean jessie installation?

paviro · 2016-04-08T20:03:48Z

I'll see if I find one :)

MichMich · 2016-04-08T20:30:14Z

Fun fact! I just put the same SD-card into a Pi3. Tried npm start and it just worked!
So there seems to be an issue with the Pi2.

pvyParts · 2016-04-09T04:01:48Z

in regards to the installer, this is how i installed node ( before i realized there was an installer )
curl -sL https://deb.nodesource.com/setup_5.x | sudo -E bash -
sudo apt-get install -y nodejs
from here

MichMich · 2016-04-09T06:30:49Z

@pvyParts: and does the MM run on a RPi2 in your case?

pvyParts · 2016-04-09T07:26:54Z

it did when i had one (read till few days ago) i blew mine up tho unfortunately so i'm only on a 3 now.

MichMich · 2016-04-09T07:28:21Z

Interesting! Thanks for letting me know.

Starbix · 2016-04-10T09:46:10Z

I have the same issue on a Pi B+ running Jessie

MichMich · 2016-04-10T11:40:44Z

I tried it yesterday on a different Pi 2, and that one worked. I've got no clue yet on the reason.

nhubbard · 2016-04-10T19:07:21Z

Could the Pi be bad? We might want to involve @raspberrypi to see if the issues are related.

MichMich · 2016-04-10T19:15:42Z

Nope, it seems like a electron issue. If you run node serveronly there is no issue.

Bangee44 · 2016-04-14T11:36:53Z

I have the same problems with the PI 1..

markbarton · 2016-06-08T16:02:59Z

prompt it boots into - doesnt work
command prompt window in gui - works fine

MichMich · 2016-06-08T16:04:22Z

That's the expected result. Electron (In which MagicMirror runs) is a GUI application, so it needs a GUI environment. It can't start that environment for you.

markbarton · 2016-06-08T16:12:48Z

Ah - thanks.

Seems obvious in hindsight - thats what the Auto start instructions were for.

sundaytill · 2016-06-18T08:45:04Z

markbarton/michmich
I have the same bug , i noticed there is no config directory ( MagicMirror/config/ ) from the boot terminal. I did install the config directory by ssh. I am able to npm start from the terminal after the startX command from the host machine and there is a MagicMirror/config directory on the host machine
How do I fix this ? Is this an autostart problem ? A directory issue? I'm really new at all of this please excuse my lack of experience and not understanding these posts

markbarton · 2016-06-18T09:15:50Z

Hi,

It wasnt a bug - it was my lack of understanding :-)

You need to use PM2 - which is a nodejs Package Manager to provide the
autostart capability for the Magic Mirror - https://github.com/Unitech/pm2

Its pretty straight forward to use.

Mark

On 18 June 2016 at 09:45, sundaytill [email protected] wrote:

markbarton/michmich
I have the same bug , i noticed there is no config directory (
MagicMirror/config/ ) from the boot terminal. I did install the config
directory by ssh. I am able to npm start from the terminal after the startX
command from the host machine and there is a MagicMirror/config directory
on the host machine
How do I fix this ? Is this an autostart problem ? A directory issue? I'm
really new at all of this please excuse my lack of experience and not
understanding these posts

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#145 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAFqd5LBlkFJh8leA_epCOPt4Rrq-1l6ks5qM7AYgaJpZM4IBLKc
.

http://www.markbarton.com

MichMich · 2016-06-18T09:57:21Z

@sundaytill This doesn't seem related to this issue. Please open a support question in http://forum.magicmirror.builders

Thanks!

sundaytill · 2016-06-18T17:56:11Z

Hi
Mark ,
Thank you

On Saturday, June 18, 2016, markbarton [email protected] wrote:

Hi,

It wasnt a bug - it was my lack of understanding :-)

You need to use PM2 - which is a nodejs Package Manager to provide the
autostart capability for the Magic Mirror - https://github.com/Unitech/pm2

Its pretty straight forward to use.

Mark

On 18 June 2016 at 09:45, sundaytill <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

markbarton/michmich
I have the same bug , i noticed there is no config directory (
MagicMirror/config/ ) from the boot terminal. I did install the config
directory by ssh. I am able to npm start from the terminal after the
startX
command from the host machine and there is a MagicMirror/config directory
on the host machine
How do I fix this ? Is this an autostart problem ? A directory issue? I'm
really new at all of this please excuse my lack of experience and not
understanding these posts

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
#145 (comment)
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AAFqd5LBlkFJh8leA_epCOPt4Rrq-1l6ks5qM7AYgaJpZM4IBLKc

.

http://www.markbarton.com

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#145 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ATFXp8zJfpBIG60l3A1bLhHvskBDeBUPks5qM7dOgaJpZM4IBLKc
.

Serubin · 2016-10-20T03:27:55Z

Any update on the issue in the op? Seems the thread got a bit sidetracked ;)

After launching something on DISPLAY=:0 I also launched a second one on DISPLAY=:1. This triggered the original electron window to open up for whatever reason

MichMich · 2016-10-20T07:07:23Z

Yeah the OP is solved a while ago. Had something to do with an older Electron version. Not relevant anymore.

tilleyc · 2016-10-22T17:32:58Z

Still getting the issue on a Raspberry Pi 3. The auto-install script happens to mention this as well:

Installing dependencies ...
npm WARN deprecated [email protected]: electron-prebuilt has been renamed to electron. For more details, see http://electron.atom.io/blog/2016/08/16/npm-install-electron
npm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g

> [email protected] postinstall /home/pi/MagicMirror/node_modules/electron-prebuilt
> node install.js

I then ran...

npm install -g coffee-script
npm install -g colorguard
npm install -g jsonlint
npm install -g electron

Still getting the issue. This is on a Raspberry Pi 3 with a clean install of Raspbian, all updated.

Full error on doing npm start in /MagicMirror..

pi@raspberrypi:~/MagicMirror $ npm start

> [email protected] start /home/pi/MagicMirror
> electron js/electron.js


npm ERR! Linux 4.4.26-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `electron js/electron.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script 'electron js/electron.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the magicmirror package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     electron js/electron.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs magicmirror
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls magicmirror
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/MagicMirror/npm-debug.log
pi@raspberrypi:~/MagicMirror $

EDIT:

Since it mentions including the contents of npm.debug.log...

pi@raspberrypi:~/MagicMirror $ cat /home/pi/MagicMirror/npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
10 verbose lifecycle [email protected]~start: CWD: /home/pi/MagicMirror
11 silly lifecycle [email protected]~start: Args: [ '-c', 'electron js/electron.js' ]
12 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start: `electron js/electron.js`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:877:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /home/pi/MagicMirror
17 error Linux 4.4.26-v7+
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
19 error node v6.9.1
20 error npm  v3.10.8
21 error code ELIFECYCLE
22 error [email protected] start: `electron js/electron.js`
22 error Exit status 1
23 error Failed at the [email protected] start script 'electron js/electron.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the magicmirror package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     electron js/electron.js
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs magicmirror
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls magicmirror
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
pi@raspberrypi:~/MagicMirror $

MichMich · 2016-10-22T18:29:44Z

Could you give this repo a try to see if electron works at all? https://github.com/electron/electron-quick-start

tilleyc · 2016-10-22T22:34:51Z

Same results it looks like:

npm ERR! Linux 4.4.26-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `electron .`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script 'electron .'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the electron-quick-start package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     electron .
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs electron-quick-start
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls electron-quick-start
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/electron-quick-start/npm-debug.log
pi@raspberrypi:~/electron-quick-start $

Results from the npm-debug.log:

pi@raspberrypi:~/electron-quick-start $ cat /home/pi/electron-quick-start/npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/electron-quick-start/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
10 verbose lifecycle [email protected]~start: CWD: /home/pi/electron-quick-start
11 silly lifecycle [email protected]~start: Args: [ '-c', 'electron .' ]
12 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start: `electron .`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:877:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /home/pi/electron-quick-start
17 error Linux 4.4.26-v7+
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
19 error node v6.9.1
20 error npm  v3.10.8
21 error code ELIFECYCLE
22 error [email protected] start: `electron .`
22 error Exit status 1
23 error Failed at the [email protected] start script 'electron .'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the electron-quick-start package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     electron .
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs electron-quick-start
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls electron-quick-start
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
pi@raspberrypi:~/electron-quick-start $

Sillec123 · 2016-10-25T07:17:06Z

I have the same error with:
Pi2
electron-v1.4.4

npm ERR! node v6.9.1
npm ERR! npm v3.10.8

node serveronly is running but PM2 not.

[STREAMING] Now streaming realtime logs for [all] processes
0|mm | 2016-10-25T07:16:04.470Z INFO no settings file found, will only use default settings
0|mm | 2016-10-25T07:16:05.644Z INFO Presets loaded: { example:
0|mm | { players:
0|mm | [ { roomName: 'Bathroom', volume: 10 },
0|mm | { roomName: 'Kitchen', volume: 10 },
0|mm | { roomName: 'Office', volume: 10 },
0|mm | { roomName: 'Bedroom', volume: 10 },
0|mm | { roomName: 'TV Room', volume: 15 } ],
0|mm | playMode: { shuffle: true, repeat: 'all', crossfade: false },
0|mm | pauseOthers: false,
0|mm | favorite: 'My example favorite' } }
0|mm | 2016-10-25T07:16:05.789Z INFO http server listening on port 5005
/root/.pm2/logs/mm-error-0.log last 10 lines:
0|mm | npm ERR! Tell the author that this fails on your system:
0|mm | npm ERR! electron js/electron.js
0|mm | npm ERR! You can get information on how to open an issue for this project with:
0|mm | npm ERR! npm bugs magicmirror
0|mm | npm ERR! Or if that isn't available, you can get their info via:
0|mm | npm ERR! npm owner ls magicmirror
0|mm | npm ERR! There is likely additional logging output above.
0|mm |
0|mm | npm ERR! Please include the following file with any support request:
0|mm | npm ERR! /root/MagicMirror/npm-debug.log

MichMich · 2016-10-25T09:36:19Z

@BlindArrow Please open an issue in the electron repository.
@Sillec123 Did you try? https://github.com/electron/electron-quick-start if not, please open an issue in the electron repository.

Tajno · 2016-10-30T03:11:03Z

I've got the same issues, fresh installed OS, cloned your repo - but electron doesn't work. Neither the quick-start. I've receive the same messages like above.

Think we have to wait for a fix by electron.

Sillec123 · 2016-10-30T07:18:18Z

It was a permission problem. Now everything works

Tajno · 2016-10-30T14:10:01Z

Allright, I will have look at this. Do you have a hint which permissions caused the error (on the first look its looks fine) Thanks anyway for your feedback.

Btw really strange is: On the serveronly mode it works over the browser (well with some errors but the display and "default" modules like wheater and RSS works). So that looks like it must be the permissions of electron...

ghost · 2016-11-30T15:16:36Z

I also have the same problem on the current jessie lite and raspi 3.

I am working on a Mac with El Capitan and XQuartz as Xserver. If I am using ssh -X .... it is running without any problems. Maybe this helps.

EDIT:
After the installation of jessie (not lite) by the manual https://forum.magicmirror.builders/topic/236/complete-setup-tutorial/5 and running "sudo npm install electron" (after the error message) in the terminal on the gui it worked starting in the terminal on the gui.

And after using the manual https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror it also worked at the ssh terminal.

96Octavian · 2017-01-07T10:26:10Z

Hi guys, I had this exact issue since this morning: make sure you have libgconf-2-4 and libxss1. I don't know how I figured this out but I installed those two and know in my RPi 2 MagicMirror runs perfectly

robozera · 2017-02-15T02:14:16Z

I get all work with a fresh new Raspbian Jessie install and running all the install since from the beggining in my RPI3 and worked like a charm.

Even though the grunt still warns me about not being installed.

Windows4Fun · 2017-07-13T12:49:28Z

Cheers mates.

Today i tryed to install the MM for the first time.
Jessie installation was good. Configuration like you wrote in you manual (http://michaelteeuw.nl/post/83188136918/magic-mirror-part-v-installing-the-raspberry-pi).
I got to the point where i used the automatic installer bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)".
The installation took quite a while and i first thought my pi just froze. After lunch (about one hour later) the installation was kind of done.
Please find attached two screenshots wich i took.
I am an absolute linux/pi rookie. Since this discussion was about "electron is not starting", how do i handle the MM installation, when electron was not even installed?
Can i stop at this point and try the "server only" method? Or is the installation corrupted?

I am using the Raspberry Pi 3 Model B.

hwikene · 2017-09-24T13:49:47Z

Hi.
Any updates here? i get the same error as casus90.

matteos1 · 2017-11-13T11:33:59Z

raspberry pi3 freeze and mm not work

sebcaps · 2017-11-19T15:10:12Z

@casus90 i got the same issue, but did not had patince to wait node-gyup rebuild... I just edited package.json to 'update' electron version, In dependencies section (line 57) , update electron version from ^1.6.10"to '^1.7.9' and sounds good. (no checked everything but install and start is OK)
(I'm using Rpi 3 on Stretch)

Hope it helps

wseme · 2017-12-30T18:40:18Z

I had the same issue on my Raspberry Pi 2 with a fresh install and after upgrading. Nothing above seemed to work.
Electron kept failing to be installed via the bash command/installer.
/usr/lib/node_modules was root.

I tried running:

npm install -g jsonlint
npm install -g electron

Both failed for me due to permissions issue.
I ran them both as sudo and this corrected the problem. I doubt this is the best way to do this. But hopefully this willl help get a fix in.

sudo npm install -g electron
sudo npm install -g jsonlint
cd ~/MagicMirror/
sh run-start.sh

E3V3A · 2018-01-06T03:22:35Z

Using latest Raspbian Stretch with (4.9.59-v7+) , this works great out-of-the-box. No problem anywhere. Just make sure to install and update Node, npm and PM2. (All installed with sudo. The rest probably doesn't need to.)

Windows4Fun · 2018-03-29T22:15:08Z

Cheers,

I am sorry for my late response! I finally found some time to try it again.
This time, I just installed (Automatic Installer) everything from scratch again and it works just fine!
There is nothing else to it. I am sorry :D :D

Best,
Andreas

MichMich mentioned this issue Apr 8, 2016

Electron not starting on Raspberry Pi electron/electron#5069

Closed

MichMich mentioned this issue Apr 11, 2016

Electron process just exits or armv6 Raspbery Pi electron/electron#4677

Closed

MichMich added the bug label Apr 11, 2016

MichMich mentioned this issue Apr 13, 2016

WARNING! Could not find config. Please create one. #168

Closed

nicolascoffman mentioned this issue Dec 29, 2016

Problem with installation #583

Closed

roramirez mentioned this issue Jan 8, 2017

electron.js issue #577

Closed

E3V3A mentioned this issue Mar 15, 2018

What is the current status for dependecies? #1210

Closed

Electron not starting on Raspberry Pi #145

Electron not starting on Raspberry Pi #145

Comments

MichMich commented Apr 6, 2016

paviro commented Apr 6, 2016

MichMich commented Apr 7, 2016

MichMich commented Apr 7, 2016

nhubbard commented Apr 8, 2016

MichMich commented Apr 8, 2016

paviro commented Apr 8, 2016

MichMich commented Apr 8, 2016

paviro commented Apr 8, 2016

MichMich commented Apr 8, 2016

paviro commented Apr 8, 2016

MichMich commented Apr 8, 2016

paviro commented Apr 8, 2016

MichMich commented Apr 8, 2016

paviro commented Apr 8, 2016

MichMich commented Apr 8, 2016

paviro commented Apr 8, 2016

MichMich commented Apr 8, 2016

pvyParts commented Apr 9, 2016

MichMich commented Apr 9, 2016

pvyParts commented Apr 9, 2016

MichMich commented Apr 9, 2016

Starbix commented Apr 10, 2016

MichMich commented Apr 10, 2016

nhubbard commented Apr 10, 2016

MichMich commented Apr 10, 2016

Bangee44 commented Apr 14, 2016

markbarton commented Jun 8, 2016

MichMich commented Jun 8, 2016

markbarton commented Jun 8, 2016

sundaytill commented Jun 18, 2016

markbarton commented Jun 18, 2016

MichMich commented Jun 18, 2016

sundaytill commented Jun 18, 2016

Serubin commented Oct 20, 2016 • edited Loading

MichMich commented Oct 20, 2016

tilleyc commented Oct 22, 2016 • edited Loading

MichMich commented Oct 22, 2016

tilleyc commented Oct 22, 2016

Sillec123 commented Oct 25, 2016

MichMich commented Oct 25, 2016

Tajno commented Oct 30, 2016 • edited Loading

Sillec123 commented Oct 30, 2016

Tajno commented Oct 30, 2016 • edited Loading

ghost commented Nov 30, 2016 • edited by ghost Loading

96Octavian commented Jan 7, 2017

robozera commented Feb 15, 2017

Windows4Fun commented Jul 13, 2017

hwikene commented Sep 24, 2017

matteos1 commented Nov 13, 2017 • edited Loading

sebcaps commented Nov 19, 2017

wseme commented Dec 30, 2017

E3V3A commented Jan 6, 2018 • edited Loading

Windows4Fun commented Mar 29, 2018

Serubin commented Oct 20, 2016 •

edited

Loading

tilleyc commented Oct 22, 2016 •

edited

Loading

Tajno commented Oct 30, 2016 •

edited

Loading

Tajno commented Oct 30, 2016 •

edited

Loading

ghost commented Nov 30, 2016 •

edited by ghost

Loading

matteos1 commented Nov 13, 2017 •

edited

Loading

E3V3A commented Jan 6, 2018 •

edited

Loading