Read the statement by Michael Teeuw here.
Autostarts but doesn't run, will run on restart
-
Happy to have broken it. Again. lol
-
@ember1205 ok, do this
cd ~/MagicMirror curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/test/run-start.sh >run-start.sh
edit the MagicMirror/installers/mm.sh
add a line before the npm start
export wait_for_x=1
(or true, or ANYTHING)
the value can be anythingedit the run-start.sh and add the -x on the 1st line again
do the pm2 flush
pm2 restartjust to test
then do the reboot test -
@sdetweil said in Autostarts but doesn't run, will run on restart:
export wait_for_x=1
That isn’t the mm.sh that my system launches from, though… Mine is ~/mm.sh
Does the one you’re referencing get called from one of the other scripts?
-
@ember1205 whatever script…
if you used my setup script it uses the one already in installers
-
Ok… Modified the ~/mm.sh script
pm2 restart mm failed to start Chromium correctly - landed on the Chrome Desktop.
Purged the config directory and started mm without issue.Restarted the mirror and everything came up clean multiple times, but there is clearly still something weird happening with Chromium in that I have to continue wiping the config directory before it will start up correctly.
-
@ember1205 the new script wipes the config folder already
-
Whatever it’s doing, it isn’t doing it correctly. “pm2 restart mm” lands me on the Chrome Desktop every time. I have to wipe the config folder by hand.
-
Its trying to wipe a non-existent directory
0|mm | + rm -rf /home/pi/.config/chromium-browser
-
@ember1205 ah. I ‘assumed’ folder name matched executable…doah…
-
@sdetweil said in Autostarts but doesn't run, will run on restart:
cd ~ rm -rf .config/chromium rm -rf .config/electron
This was what you had mentioned earlier in the thread and worked, and it’s what I built my config wipe based on.