• 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
  1. Home
  2. thedk
  3. Posts
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
T
Offline
  • Profile
  • Following 0
  • Followers 0
  • Topics 6
  • Posts 42
  • Groups 0

Posts

Recent Best Controversial
  • RE: Black screen after Update again

    This is not possible over a terminal programm?

    The Error is back…

    0|mm       | [9898:0407/121438.093751:FATAL:bus.cc(1151)] D-Bus connection was disconnected. Aborting.
    0|mm       | XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
    0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by environment.
    0|mm       | npm ERR! code ELIFECYCLE
    0|mm       | npm ERR! errno 1
    0|mm       | npm ERR! magicmirror@2.7.1 start: `sh run-start.sh`
    0|mm       | npm ERR! Exit status 1
    0|mm       | npm ERR!
    0|mm       | npm ERR! Failed at the magicmirror@2.7.1 start script.
    0|mm       | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    0|mm       |
    0|mm       | npm ERR! A complete log of this run can be found in:
    0|mm       | npm ERR!     /home/pi/.npm/_logs/2019-04-07T10_21_07_746Z-debug.log
    0|mm       | XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
    0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by environment.
    
    
    posted in Troubleshooting
    T
    thedk
    Apr 7, 2019, 2:02 PM
  • RE: Black screen after Update again

    Tried it, but still the same.
    No error in the log but just the black screen.

    Dont know what i can try now. Has anybod a idea?

    posted in Troubleshooting
    T
    thedk
    Apr 7, 2019, 10:23 AM
  • RE: Black screen after Update again

    Ah ok.
    I just did it in the modul folder and for the PIR modul, not for the rest.
    Will try this later.

    posted in Troubleshooting
    T
    thedk
    Apr 6, 2019, 1:20 PM
  • Black screen after Update again

    Hey Guys.
    After the Update i got a black screen and it seems not to be the PIR. With the Remote Module i see everything in the Browser, but the screen shows nothing.
    This is the LOG

    /home/pi/.pm2/logs/mm-error.log last 15 lines:
    0|mm       |     at IncomingMessage.emit (events.js:187:15)
    0|mm       |     at endReadableNT (_stream_readable.js:1090:12)
    0|mm       |     at process._tickCallback (internal/process/next_tick.js:63:19)
    0|mm       | npm ERR! code ELIFECYCLE
    0|mm       | npm ERR! errno 1
    0|mm       | npm ERR! magicmirror@2.7.1 start: `sh run-start.sh`
    0|mm       | npm ERR! Exit status 1
    0|mm       | npm ERR!
    0|mm       | npm ERR! Failed at the magicmirror@2.7.1 start script.
    0|mm       | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    0|mm       |
    0|mm       | npm ERR! A complete log of this run can be found in:
    0|mm       | npm ERR!     /home/pi/.npm/_logs/2019-04-06T11_59_36_840Z-debug.log
    0|mm       | XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
    0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by environment.
    
    

    the complete Log:
    0 info it worked if it ends with ok
    1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’ ]
    2 info using npm@6.8.0
    3 info using node@v9.11.2
    4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
    5 info lifecycle magicmirror@2.7.1~prestart: magicmirror@2.7.1
    6 info lifecycle magicmirror@2.7.1~start: magicmirror@2.7.1
    7 verbose lifecycle magicmirror@2.7.1~start: unsafe-perm in lifecycle true
    8 verbose lifecycle magicmirror@2.7.1~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/$
    9 verbose lifecycle magicmirror@2.7.1~start: CWD: /home/pi/MagicMirror
    10 silly lifecycle magicmirror@2.7.1~start: Args: [ ‘-c’, ‘sh run-start.sh’ ]
    11 silly lifecycle magicmirror@2.7.1~start: Returned: code: 1 signal: null
    12 info lifecycle magicmirror@2.7.1~start: Failed to exec start script
    13 verbose stack Error: magicmirror@2.7.1 start: sh run-start.sh
    13 verbose stack Exit status 1
    13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
    13 verbose stack at EventEmitter.emit (events.js:180:13)
    13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
    13 verbose stack at ChildProcess.emit (events.js:180:13)
    13 verbose stack at maybeClose (internal/child_process.js:936:16)
    13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
    14 verbose pkgid magicmirror@2.7.1
    15 verbose cwd /home/pi/MagicMirror
    16 verbose Linux 4.14.79-v7+
    17 verbose argv “/usr/bin/node” “/usr/bin/npm” “start”
    18 verbose node v9.11.2
    19 verbose npm v6.8.0
    20 error code ELIFECYCLE
    21 error errno 1
    22 error magicmirror@2.7.1 start: sh run-start.sh
    22 error Exit status 1
    23 error Failed at the magicmirror@2.7.1 start script.
    23 error This is probably not a problem with npm. There is likely additional logging output above.
    24 verbose exit [ 1, true ]

    posted in Troubleshooting
    T
    thedk
    Apr 6, 2019, 12:22 PM
  • RE: Google-route Citys disappear changing height/width

    Also with max-width and max-height the map doesnt get smaller, it just moves out of the Display.

    posted in Troubleshooting
    T
    thedk
    Feb 17, 2019, 6:30 PM
  • RE: Hide modules when display goes off through PIR (power saving)

    A fan wouldnt be a solution. The 5-10 seconds waiting would be ok.

    posted in Requests
    T
    thedk
    Feb 17, 2019, 6:11 PM
  • RE: Google-route Citys disappear changing height/width

    tested it and i dont know why, but it doesnt work.
    Thats my custom.css

     body {
     	
     }
    
    .normal {
      color: #fff;
    }
    
    .region.top.right,
    .region.top.left,
    .region.top.center {
      top: 80%;
    }
    
    .region.bottom.right,
    .region.bottom.center,
    .region.bottom.left {
      bottom: 80%;
    }
    
    
    posted in Troubleshooting
    T
    thedk
    Feb 17, 2019, 6:07 PM
  • RE: Hide modules when display goes off through PIR (power saving)

    Nice discussion :)
    My thought just was to reduce the temperature of the CPU when the display switches of.
    But the point with the network requests is also good!

    posted in Requests
    T
    thedk
    Feb 17, 2019, 5:59 PM
  • RE: Google-route Citys disappear changing height/width

    Thanks for your help.
    So i have to change the size of the region where the modul is i guess.

    posted in Troubleshooting
    T
    thedk
    Feb 17, 2019, 5:55 PM
  • RE: Glossy or Non-Glossy Display

    To end this. I tried both, you dont really see any different.

    posted in Hardware
    T
    thedk
    Feb 17, 2019, 3:23 PM
  • 1
  • 2
  • 3
  • 4
  • 5
  • 2 / 5
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