• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

Setting Up Magic Mirror on Ubuntu issue

Scheduled Pinned Locked Moved Unsolved Troubleshooting
11 Posts 5 Posters 3.6k Views 5 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    justjim1220 Module Developer @DuhCompuder
    last edited by Jan 20, 2019, 12:55 AM

    @duhcompuder

    Install the same way: npm i acorn@latest

    with any of those kind of warnings do the same.

    I’m having issues right now getting MM to run on a new install of Ubuntu.
    Keep getting errors that the sh start.sh or something like that isn’t valid.
    Can’t figure it out, had this issue once before a long time ago and not sure how I fixed it.

    "Life's Too Short To Dance With Ugly People"
    Jim Hallock - 1995

    D 1 Reply Last reply Jan 21, 2019, 4:44 AM Reply Quote 0
    • D Offline
      DuhCompuder @justjim1220
      last edited by Jan 21, 2019, 4:44 AM

      I don’t even know how to describe this… So after fixing the acorn issue, the lodash issue reappeared. For some reason, I can no longer fix the lodash issue (even with sudo and root terminal). It just would not let me install lodash 4.17.5 or even the newest version because of the vulnerability.

      I’m hypothesizing that MM might be using something that is dependent on a previous version of lodash that conflicts with Ubuntu’s security vulnerability


      Here is an article referring the lodash vulnerabilities existing in versions prior to 4.17.11:

      https://resources.whitesourcesoftware.com/blog-whitesource/top-5-open-source-security-vulnerabilities-november-2018


      Conclusion.

      After updating my system’s lodash file to 4.17.12 through a root terminal, I was able to resolve updating issues related to lodash within the MM directory. The only issue is the message about the vulnerability that is not resolvable with npm audit fix

      Starting the program displays the message that MagicMirror is online yet the UI does not change.

      I’m going to stick with Raspbian for now

      M 1 Reply Last reply Jan 22, 2019, 1:30 AM Reply Quote 0
      • M Offline
        Mykle1 Project Sponsor Module Developer @DuhCompuder
        last edited by Jan 22, 2019, 1:30 AM

        @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

        Create a working config
        How to add modules

        T 1 Reply Last reply Jan 23, 2019, 7:49 PM Reply Quote 1
        • T Offline
          THeStigh @Mykle1
          last edited by THeStigh Jan 23, 2019, 7:49 PM Jan 23, 2019, 7:49 PM

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

          S M 2 Replies Last reply Jan 23, 2019, 8:05 PM Reply Quote 0
          • S Offline
            sdetweil @THeStigh
            last edited by Jan 23, 2019, 8:05 PM

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

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            1 Reply Last reply Reply Quote 0
            • M Offline
              Mykle1 Project Sponsor Module Developer @THeStigh
              last edited by Mykle1 Jan 23, 2019, 8:53 PM Jan 23, 2019, 8:49 PM

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

              Create a working config
              How to add modules

              S 1 Reply Last reply Jan 23, 2019, 8:50 PM Reply Quote 0
              • S Offline
                sdetweil @Mykle1
                last edited by Jan 23, 2019, 8:50 PM

                also check the node and npm versions,

                node -v
                

                and

                npm -v
                

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                1 Reply Last reply Reply Quote 0
                • T Offline
                  THeStigh
                  last edited by Jan 23, 2019, 10:18 PM

                  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…

                  1 Reply Last reply Reply Quote 0
                  • 1
                  • 2
                  • 1 / 2
                  1 / 2
                  • First post
                    8/11
                    Last post
                  Enjoying MagicMirror? Please consider a donation!
                  MagicMirror created by Michael Teeuw.
                  Forum managed by Sam, technical setup by Karsten.
                  This forum is using NodeBB as its core | Contributors
                  Contact | Privacy Policy