Setting Up Magic Mirror on Ubuntu issue

THeStigh

@mykle1 said in Setting Up Magic Mirror on Ubuntu issue:

@duhcompuder said in Setting Up Magic Mirror on Ubuntu issue:

I’m going to stick with Raspbian for now

I don’t know if this matters but I use ubuntu 16.04 LTS exclusively on several machines, including my dev machine. The one time I tried to install MM on ubuntu 18.xx I encountered all the vulnerabilities that you are talking about. I immediately wiped the machine and installed ubuntu 16.04 LTS. Then I installed MM without a single problem. That includes the most current MM, v2.6.0

@Mykle1

I’ve just installed Ubuntu 14.04 on my laptop (to get full support for Snowboy), but when I run ‘npm start’, it starts the application but dont “open the magicmirror”. I can use my browser to dial into it.

Do you know if I need to add something extra to make it show upon running the application?

I run GNOME as desktop.

sdetweil

@thestigh i just upgraded to 2.6.0

this is what I see in the console window when I do npm start, obviously some of these modules are specific for my system

Starting MagicMirror: v2.6.0
Loading config ...
Loading module helpers ...
No helper found for module: alert.
handler helper in init
Module helper loaded: MMM-SleepWake
Initializing new module helper ...
Module helper loaded: MMM-ImagesPhotos
Initializing new module helper ...
Module helper loaded: MMM-voice
Initializing new module helper ...
Module helper loaded: WaterLevels
All module helpers loaded.
Starting server on port 8086 ...
Server started ...
Connecting socket for: MMM-SleepWake
handler helper in start
Connecting socket for: MMM-ImagesPhotos
Starting node helper for: MMM-ImagesPhotos
Connecting socket for: MMM-voice
Starting module helper: MMM-voice
Connecting socket for: WaterLevels
Starting module: WaterLevels
Sockets connected & modules started ...
Launching application.

do you see anything different?

npm start  dev

would open the developers console, and then change to the console tab to check for any errors (red text)

Mykle1

@thestigh said in Setting Up Magic Mirror on Ubuntu issue:

Do you know if I need to add something extra to make it show upon running the application?

No, you shouldn’t need anything “extra” although I only use ubutnu 16.04 LTS. I’m reading through some posts that mention the same exact problem that you’re experiencing, where MM is running but can only be seen remotely.

As suggested by @sdetweil, run npm start dev in your MagicMirror directory and choose the Console tab in the resulting window. Then copy/paste/report any errors there and/or in your terminal.

You might also want to make sure that all updates have been performed on your current ubuntu installation as well as ensuring that you have current stable versions of node and npm.

sdetweil

also check the node and npm versions,

node -v

and

npm -v

THeStigh

Guys, I’m giving up this task of getting Debian/Ubuntu running on an amd64 with MMM-Hotword. I again are getting the “invalid pointer” error.

Perhaps this is happening only on amd64 distro and would not happen on i386 (32bit).
If I’m going to test it? Maybe, but returning back to my Pi and Tinker Board for now…