pi 3B+

uname -a output

Linux raspberrypi 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux

How do I post the log? Far too large to go into a post, and isn’t a support file type to attach.

Error on my part… I still have the upgraded directory.

There is no info from the logs that I can tell that shows any sort of crash or anything. And the line from the npm logs just shows the run-start.sh command.

My MM install has been running reasonably well for a while and I have not pushed any updates to it in probably 18 months. I recently applied the most recent updates for Raspbian and things were still running correctly for maybe around a week.

Yesterday, I decided I was going to attempt an upgrade using one of the scripts. So, I did an rsync of the running directory to a second directory on the local device then ran the upgrade script.

Upon starting the mirror, it started complaining about an out-of-date module (MMM-ImagesPhotos). That module wasn’t installed from the original source, so updating it was not going to be something I could do without a bunch of research. So, I stopped the mirror, did an rm-rf on the MM directory, then renamed the backup directory back to its original name.

I -thought- it was running properly, but today it keeps restarting Chromium browser every minute or two. Where do I even begin?

@MMRIZE Thanks for the pointer.

Why wouldn’t I use the “Outline” option? That seems like it would achieve the result I’m after as well?

Also, I have absolutely no clue where or how to implement these changes. Working my way through CSS and such is an immensely trial-and-error process for me that tends to requires hours of “Developer Console” type access through a browser trying to chase down the files involved, tinkering with changes, and often times not actually getting the result I want without at least breaking one other thing.

@sdetweil While a “dynamic” solutions sounds like it would be great, I don’t see it as being terribly feasible.

Every photo that loads would have to be analyzed to determine something like a ‘brightness level’ or similar. Below a value gets a dark font, above a value gets a light font. That would have to map to regions on the screen since one picture could have multiple areas that are above and below that particular level.

Then, you’d have to assess the relationship between the area in the photo and the actual area where the text would be placed, taking into account different placements for text size, string length, wrap, etc.

Just seems like a two color font would address it more simply. Or some sort of way to “outline” text with a different color than the color of the font itself.

@sdetweil said in Two color font?:

@ember1205 I want it to handle that dynamically

In what way?

My mirror is part digital photo frame and part info display tool. The photos are shown in random order and are all full screen.

The info sections are all currently using various shades of gray fonts which are easy to see when the photo area “behind them” is darker. When the photo area is fairly light, however, the text is unreadable.

I’m wondering if there’s either a two color font (gray with a black outline or similar) or a way to render an outline around all of the font characters that are currently being shown. I’d want this to apply to all text sections in the mirror if I could do it.

@sdetweil

As long as you got it all fixed, then it was a good day!

@sdetweil

Now I have to find something else to break… sigh… :)

@sdetweil

Seems to be working reliably. Even why I simply do a “shutdown now” without any of my shutdown process items, it starts up correctly.

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

@sdetweil

Its trying to wipe a non-existent directory

0|mm  | + rm -rf /home/pi/.config/chromium-browser

@sdetweil

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.

@sdetweil

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.

@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?

@sdetweil

Happy to have broken it. Again. lol

@sdetweil

I removed the check I was running that was ensuring it would start correctly and put in the line you asked. I believe the log info you want is this:

0|mm       | + '[' -f ./untrack-css.sh ']'
0|mm       | + grep docker /proc/1/cgroup -qa
0|mm       | + '[' -z :0 ']'
0|mm       | ++ uname -m
0|mm       | + arch=armv7l
0|mm       | + false=false
0|mm       | ++ grep -i serveronly:
0|mm       | ++ awk -F: '{print tolower($2)}'
0|mm       | ++ tr -d ',"'\''\r'
0|mm       | ++ grep -v '^[[:blank:]]*//' config/config.js
0|mm       | ++ sed -e 's/^[[:space:]]*//'
0|mm       | + serveronly=local
0|mm       | + serveronly=local
0|mm       | + xprop -root
0|mm       | xprop:  unable to open display ':0'
0|mm       | ++ pgrep Xorg
0|mm       | + xorg=
0|mm       | + '[' . == . ']'
0|mm       | ++ pgrep X
0|mm       | + xorg=
0|mm       | ++ uname
0|mm       | + mac=Linux
0|mm       | + '[' local. '!=' false. -o armv7l == armv6l ']'
0|mm       | + '[' local. == true. ']'
0|mm       | + '[' . == . -a Linux '!=' Darwin ']'
0|mm       | + node serveronly

Here’s the rest that goes with it “just in case”:

/home/pi/.pm2/pm2.log last 100 lines:
PM2        | 2022-05-11T08:48:46: PM2 log: PM2 successfully stopped
PM2        | 2022-05-11T08:49:03: PM2 log: ===============================================================================
PM2        | 2022-05-11T08:49:03: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
PM2        | 2022-05-11T08:49:03: PM2 log: Time                 : Wed May 11 2022 08:49:03 GMT-0400 (Eastern Daylight Time)
PM2        | 2022-05-11T08:49:03: PM2 log: PM2 version          : 4.4.1
PM2        | 2022-05-11T08:49:03: PM2 log: Node.js version      : 16.15.0
PM2        | 2022-05-11T08:49:03: PM2 log: Current arch         : arm
PM2        | 2022-05-11T08:49:03: PM2 log: PM2 home             : /home/pi/.pm2
PM2        | 2022-05-11T08:49:03: PM2 log: PM2 PID file         : /home/pi/.pm2/pm2.pid
PM2        | 2022-05-11T08:49:03: PM2 log: RPC socket file      : /home/pi/.pm2/rpc.sock
PM2        | 2022-05-11T08:49:03: PM2 log: BUS socket file      : /home/pi/.pm2/pub.sock
PM2        | 2022-05-11T08:49:03: PM2 log: Application log path : /home/pi/.pm2/logs
PM2        | 2022-05-11T08:49:03: PM2 log: Worker Interval      : 30000
PM2        | 2022-05-11T08:49:03: PM2 log: Process dump file    : /home/pi/.pm2/dump.pm2
PM2        | 2022-05-11T08:49:03: PM2 log: Concurrent actions   : 2
PM2        | 2022-05-11T08:49:03: PM2 log: SIGTERM timeout      : 1600
PM2        | 2022-05-11T08:49:03: PM2 log: ===============================================================================
PM2        | 2022-05-11T08:49:04: PM2 log: App [mm:0] starting in -fork mode-
PM2        | 2022-05-11T08:49:04: PM2 log: App [mm:0] online


/home/pi/.pm2/logs/mm-out.log last 100 lines:
0|mm       |
0|mm       | > magicmirror@2.13.0 start
0|mm       | > ./run-start.sh
0|mm       |
0|mm       | [2022-05-11 08:49:14.433] [LOG]    Starting MagicMirror: v2.13.0
0|mm       | [2022-05-11 08:49:14.450] [LOG]    Loading config ...
0|mm       | [2022-05-11 08:49:14.465] [LOG]    Loading module helpers ...
0|mm       | [2022-05-11 08:49:15.909] [LOG]    Initializing new module helper ...
0|mm       | [2022-05-11 08:49:15.914] [LOG]    Module helper loaded: MMM-ImagesPhotos
0|mm       | [2022-05-11 08:49:15.923] [LOG]    No helper found for module: alert.
0|mm       | [2022-05-11 08:49:16.037] [LOG]    Initializing new module helper ...
0|mm       | [2022-05-11 08:49:16.040] [LOG]    Module helper loaded: updatenotification
0|mm       | [2022-05-11 08:49:16.044] [LOG]    No helper found for module: clock.
0|mm       | [2022-05-11 08:49:16.351] [LOG]    Initializing new module helper ...
0|mm       | [2022-05-11 08:49:16.353] [LOG]    Module helper loaded: calendar
0|mm       | [2022-05-11 08:49:16.401] [LOG]    No helper found for module: currentweather.
0|mm       | [2022-05-11 08:49:16.576] [LOG]    No helper found for module: weatherforecast.
0|mm       | [2022-05-11 08:49:16.578] [LOG]    All module helpers loaded.
0|mm       | [2022-05-11 08:49:18.093] [LOG]    Starting server on port 8080 ...
0|mm       | [2022-05-11 08:49:18.123] [LOG]    Server started ...
0|mm       | [2022-05-11 08:49:18.126] [LOG]    Connecting socket for: MMM-ImagesPhotos
0|mm       | [2022-05-11 08:49:18.127] [LOG]    Starting node helper for: MMM-ImagesPhotos
0|mm       | [2022-05-11 08:49:18.130] [LOG]    Connecting socket for: updatenotification
0|mm       | [2022-05-11 08:49:18.132] [LOG]    Connecting socket for: calendar
0|mm       | [2022-05-11 08:49:18.134] [LOG]    Starting node helper for: calendar
0|mm       | [2022-05-11 08:49:18.135] [LOG]    Sockets connected & modules started ...
0|mm       | [2022-05-11 08:49:18.137] [LOG]
0|mm       | Ready to go! Please point your browser to: http://0.0.0.0:8080

@sdetweil

Oh… now I follow.

@sdetweil said in Autostarts but doesn't run, will run on restart:

… my pi 0 now comes up instead of the chrome desktop
which was random before…

Not sure I’m following what this should mean?

@sdetweil

The test I’m referring to checks to see if X is running. If not, it moves on to test for Lubuntu. If that also fails, it assumes server only and moves on.

I do recall seeing a specific Docker test at the very beginning of the script, but that’s a fair bit earlier than where I’ve added this check (which is right before the “pgrep Xorg” line).