MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. Samwise
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    S
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 6
    • Groups 0

    Samwise

    @Samwise

    0
    Reputation
    42
    Profile views
    6
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    Samwise Unfollow Follow

    Latest posts made by Samwise

    • RE: MMM-GooglePhotos

      also, the auto start script doesn’t seem to work either

      posted in Entertainment
      S
      Samwise
    • RE: MMM-GooglePhotos

      Hey, so i’m not sure what this means, but it happens whenever I try to start it:

      pi@sam-raspberrypi:~/MagicMirror $ npm start

      magicmirror@2.7.1 start /home/pi/MagicMirror
      sh run-start.sh

      /home/pi/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
      npm ERR! file sh
      npm ERR! code ELIFECYCLE
      npm ERR! errno ENOENT
      npm ERR! syscall spawn
      npm ERR! magicmirror@2.7.1 start: sh run-start.sh
      npm ERR! spawn ENOENT
      npm ERR!
      npm ERR! Failed at the magicmirror@2.7.1 start script.
      npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

      npm ERR! A complete log of this run can be found in:
      npm ERR! /home/pi/.npm/_logs/2020-04-02T05_53_17_399Z-debug.log

      posted in Entertainment
      S
      Samwise
    • RE: MMM-GooglePhotos

      @Sean where do i find the log?

      Also, this popped up: pi@raspberrypi:~/MagicMirror $ npm start

      magicmirror@2.7.1 start /home/pi/MagicMirror
      sh run-start.sh

      /home/pi/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
      npm ERR! file sh
      npm ERR! code ELIFECYCLE
      npm ERR! errno ENOENT
      npm ERR! syscall spawn
      npm ERR! magicmirror@2.7.1 start: sh run-start.sh
      npm ERR! spawn ENOENT
      npm ERR!
      npm ERR! Failed at the magicmirror@2.7.1 start script.
      npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

      npm ERR! A complete log of this run can be found in:
      npm ERR! /home/pi/.npm/_logs/2020-02-29T10_46_17_131Z-debug.log

      posted in Entertainment
      S
      Samwise
    • RE: MMM-GooglePhotos

      ok i think everything is in order, but the pictures don’t actually show up…

      posted in Entertainment
      S
      Samwise
    • RE: MMM-GooglePhotos

      ok, so it worked, but then when i tried to set which album i wanted, it said this:

      pi@raspberrypi:~/MagicMirror/modules/MMM-GooglePhotos $ nano MMM-GooglePhotos.js
      nano: error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directory

      posted in Entertainment
      S
      Samwise
    • RE: MMM-GooglePhotos

      my auth_and_test is not working. it worked like a year ago, but I haven’t used it since. I’m really new and don’t really know what I’m doing. this is what i get:

      pi@raspberrypi:~/MagicMirror/modules/MMM-GooglePhotos $ node auth_and_test.js
      (node:698) UnhandledPromiseRejectionWarning: Error: invalid_grant
      at createError (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/core/createError.js:16:15)
      at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/core/settle.js:18:12)
      at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/adapters/http.js:201:11)
      at IncomingMessage.emit (events.js:198:15)
      at endReadableNT (_stream_readable.js:1139:12)
      at processTicksAndRejections (internal/process/task_queues.js:81:17)
      (node:698) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
      (node:698) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

      Any suggestions?

      posted in Entertainment
      S
      Samwise