MM won't run, blank screen with cursor showing after updating

jmartin1009

@sdetweil i accidentally installed it in the folder previous to MM, but it still worked, but im installing it in the MM folder right now. Thought you meant the first level cd. Should i remove it in the pi folder? If so how because it doesn’t show up

sdetweil

@jmartin1009 sure

cd ~
npm uninstall rrule

jmartin1009

@sdetweil how do i fix this?

pi@raspberrypi:~/MagicMirror $ npm install rrule
npm WARN acorn-jsx@5.0.1 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN grunt-stylelint@0.10.1 requires a peer of stylelint@^9.0.0 but none is installed. You must install peer dependencies yourself.

+ rrule@2.6.2
added 2 packages from 2 contributors and audited 2431 packages in 49.239s
found 4 vulnerabilities (2 low, 2 high)
  run `npm audit fix` to fix them, or `npm audit` for details
pi@raspberrypi:~/MagicMirror $ npm audit fix
npm WARN acorn-jsx@5.0.1 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN grunt-stylelint@0.10.1 requires a peer of stylelint@^9.0.0 but none is installed. You must install peer dependencies yourself.

up to date in 51.138s
fixed 0 of 4 vulnerabilities in 2431 scanned packages
  2 package updates for 4 vulns involved breaking changes
  (use `npm audit fix --force` to install breaking changes; or refer to `npm audit` for steps to fix these manually)

Thanks for all your help btw

sdetweil

@jmartin1009 said in MM won't run, blank screen with cursor showing after updating:
it says

run npm audit fix to fix them

many times you cannot fix them all… so, after one try, ignore it

jmartin1009

@sdetweil Okay! Do you know anything about MM-voice? having issues with that for some reason and i can’t figure out why.

sdetweil

@jmartin1009 yes, what troubles? i have it installed on one of my MagicMirror systems…

jmartin1009

@sdetweil I have it installed but when i run MM, the little microphone says initializing, then ERROR. I used debug: true, and the file said

sdetweil

@jmartin1009 ok. usually this is the device name of the mic…

run

arecord -l

to get the list of mic devices

make sure that is in the MMM-Voice config, mine is

       config: {
              microphone: '1,0',

jmartin1009

@sdetweil

pi@raspberrypi:~ $ arecord -l
**** List of CAPTURE Hardware Devices ****
card 1: Snowball [Blue Snowball], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

does this mean it is 1 or 1,0?

sdetweil

@jmartin1009

card 1
device 0

1,0

you can also test the mic with

arecord -D hw:1,0 test.wav

ctrl-break , ctrl-c, or ctrl-z after saying something

then

aplay test.wav

to hear the recorded voice back