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

back screan when start up an errors.....

Scheduled Pinned Locked Moved Solved Troubleshooting
5 Posts 2 Posters 1.3k Views 2 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
    jcklerk
    last edited by Jul 25, 2018, 3:08 PM

    is have installt it on ubuntu 16.04
    and i have this problem
    it start up whit errors and whit the server Only version i have no errors but still blank screan and th consel on Web Browser is spammed full…
    and when i start it up using npm start it have som errors i cant figger it out what the problem is…

    start up error:

    root@smart-mirror-jcklerk:~/MagicMirror# npm start
    
    > magicmirror@2.4.1 start /root/MagicMirror
    > sh run-start.sh
    
    
    (electron:6583): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
    
    (electron:6583): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
    
    (electron:6583): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
    Starting MagicMirror: v2.4.1
    Loading config ...
    Loading module helpers ...
    No helper found for module: alert.
    Initializing new module helper ...
    Module helper loaded: updatenotification
    No helper found for module: clock.
    Initializing new module helper ...
    Module helper loaded: calendar
    No helper found for module: compliments.
    No helper found for module: currentweather.
    No helper found for module: weatherforecast.
    Initializing new module helper ...
    Module helper loaded: newsfeed
    All module helpers loaded.
    Starting server on port 8989 ... 
    You're using a full whitelist configuration to allow for all IPs
    Server started ...
    Connecting socket for: updatenotification
    Connecting socket for: calendar
    Starting node helper for: calendar
    Connecting socket for: newsfeed
    Starting module: newsfeed
    Sockets connected & modules started ...
    
    (electron:6583): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
    Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    Launching application.
    Shutting down server...
    Stopping module helper: updatenotification
    Stopping module helper: calendar
    Stopping module helper: newsfeed
    root@smart-mirror-jcklerk:~/MagicMirror# 
    
    **test **
    
    0 info it worked if it ends with ok
    1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'test:e2e' ]
    2 info using npm@6.1.0
    3 info using node@v10.7.0
    4 verbose run-script [ 'pretest:e2e', 'test:e2e', 'posttest:e2e' ]
    5 info lifecycle magicmirror@2.4.1~pretest:e2e: magicmirror@2.4.1
    6 info lifecycle magicmirror@2.4.1~test:e2e: magicmirror@2.4.1
    7 verbose lifecycle magicmirror@2.4.1~test:e2e: unsafe-perm in lifecycle true
    8 verbose lifecycle magicmirror@2.4.1~test:e2e: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/root/MagicMirror/node_modules/.bin:/usr/local$
    9 verbose lifecycle magicmirror@2.4.1~test:e2e: CWD: /root/MagicMirror
    10 silly lifecycle magicmirror@2.4.1~test:e2e: Args: [ '-c',
    10 silly lifecycle   'NODE_ENV=test ./node_modules/mocha/bin/mocha tests/e2e --recursive' ]
    11 silly lifecycle magicmirror@2.4.1~test:e2e: Returned: code: 39  signal: null
    12 info lifecycle magicmirror@2.4.1~test:e2e: Failed to exec test:e2e script
    13 verbose stack Error: magicmirror@2.4.1 test:e2e: `NODE_ENV=test ./node_modules/mocha/bin/mocha tests/e2e --recursive`
    13 verbose stack Exit status 39
    13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:304:16)
    13 verbose stack     at EventEmitter.emit (events.js:182:13)
    13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
    13 verbose stack     at ChildProcess.emit (events.js:182:13)
    13 verbose stack     at maybeClose (internal/child_process.js:961:16)
    13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5)
    14 verbose pkgid magicmirror@2.4.1
    15 verbose cwd /root/MagicMirror
    16 verbose Linux 4.15.0-29-generic
    17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "test:e2e"
    18 verbose node v10.7.0
    19 verbose npm  v6.1.0
    20 error code ELIFECYCLE
    21 error errno 39
    22 error magicmirror@2.4.1 test:e2e: `NODE_ENV=test ./node_modules/mocha/bin/mocha tests/e2e --recursive`
    22 error Exit status 39
    23 error Failed at the magicmirror@2.4.1 test:e2e script.
    23 error This is probably not a problem with npm. There is likely additional logging output above.
    24 verbose exit [ 39, true ]
    

    i hope sam one can help me

    ? 1 Reply Last reply Jul 25, 2018, 3:18 PM Reply Quote 0
    • J Offline
      jcklerk
      last edited by jcklerk Jul 27, 2018, 7:03 AM Jul 26, 2018, 9:19 PM

      chek:
      npm install errors magicmirror@2.4.1 &

      dbus-deamon is running under the user jcklerk and i start up magicmirror whif root user

      but still black screen

      1 Reply Last reply Reply Quote 0
      • ? Offline
        A Former User @jcklerk
        last edited by Jul 25, 2018, 3:18 PM

        @jcklerk
        Try this.

        npm start -- --disable-gpu
        

        In my case, it worked.

        J 1 Reply Last reply Jul 25, 2018, 4:10 PM Reply Quote 0
        • J Offline
          jcklerk @Guest
          last edited by Jul 25, 2018, 4:10 PM

          @sean Nope doesn’t work for me…

          root@smart-mirror-jcklerk:~/MagicMirror# npm start -- --disable-gpu
          
          > magicmirror@2.4.1 start /root/MagicMirror
          > sh run-start.sh "--disable-gpu"
          
          
          (electron:7962): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
          
          (electron:7962): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
          
          (electron:7962): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
          Starting MagicMirror: v2.4.1
          Loading config ...
          Loading module helpers ...
          No helper found for module: alert.
          Initializing new module helper ...
          Module helper loaded: updatenotification
          No helper found for module: clock.
          Initializing new module helper ...
          Module helper loaded: calendar
          No helper found for module: compliments.
          No helper found for module: currentweather.
          No helper found for module: weatherforecast.
          Initializing new module helper ...
          Module helper loaded: newsfeed
          All module helpers loaded.
          Starting server on port 8989 ... 
          You're using a full whitelist configuration to allow for all IPs
          Server started ...
          Connecting socket for: updatenotification
          Connecting socket for: calendar
          Starting node helper for: calendar
          Connecting socket for: newsfeed
          Starting module: newsfeed
          Sockets connected & modules started ...
          
          (electron:7962): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
          Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
          Launching application.
          Shutting down server...
          Stopping module helper: updatenotification
          Stopping module helper: calendar
          Stopping module helper: newsfeed
          root@smart-mirror-jcklerk:~/MagicMirror# 
          
          1 Reply Last reply Reply Quote 0
          • J Offline
            jcklerk
            last edited by Jul 25, 2018, 9:54 PM

            I’m are going to re install ubuntu and chek if i have the same error bicase i have som oudio problems whit google assistant after i install magicmirror…

            1 Reply Last reply Reply Quote 0
            • J Offline
              jcklerk
              last edited by jcklerk Jul 27, 2018, 7:03 AM Jul 26, 2018, 9:19 PM

              chek:
              npm install errors magicmirror@2.4.1 &

              dbus-deamon is running under the user jcklerk and i start up magicmirror whif root user

              but still black screen

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              1 / 1
              • First post
                3/5
                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