search

LukeSkywalker92 / TeleFrame

TeleFrame - a digital picture frame for telegram
MIT License
93 stars 28 forks source link

Reboot fails #177

Open AAAbrAkAdAbrAAA opened 2 years ago

AAAbrAkAdAbrAAA commented 2 years ago

First of all thanks for this Open Source Project. It is awesome and I hope to make my grandma happy this Christmas with a frame :)

But, when installing TeleFrame and booting it first, everything works fine. Pictures are received and displayed. So far, so good.

But when rebooting, the raspberry loops into infinity and input does not work.

I already disabled and deinstalled pm2, but it is still an issue. The raspberry tries to boot TeleFrame right from the start.

The TeleFrame Logo shows up first when rebooting. Then the screen goes off again. Then the screen is on without any text or output.

LukeSkywalker92 commented 2 years ago

Hey, I'm happy that you like the project! I see you are in a little hurry =)

First of all: which pm2 script are you using? Did you choose the one that is waiting for internet connection? Second: can you share the pm2 logs with us?

AAAbrAkAdAbrAAA commented 2 years ago

Yes, this is definitely a last minute present :-D

I tried both versions, with and without waiting, both seem to stuck.

How can I reach the logs, when the pi is totally freezed? Can I interrupt the pm2 startup?

LukeSkywalker92 commented 2 years ago

Do you have ssh access to the pi? Or is this also frozen? If you have access you can use pm2 logs 0 to get the logs...

AAAbrAkAdAbrAAA commented 2 years ago

let me try :)

AAAbrAkAdAbrAAA commented 2 years ago

Here are the log with the frame on first boot up, working fine:

pi@raspberrypi:~ $ pm2 logs 0 [TAILING] Tailing last 15 lines for [0] process (change the value with --lines option) /home/pi/.pm2/logs/TeleFrame-error.log last 15 lines: 0|TeleFram | (node:9063) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron. See https://github.com/electron/electron/issues/23506 for more information

/home/pi/.pm2/logs/TeleFrame-out.log last 15 lines: 0|TeleFram | 0|TeleFram | > teleframe@3.2.3 start 0|TeleFram | > electron . 0|TeleFram | 0|TeleFram | 2021-12-23T12:23:10.458Z [Main] info: Configuring for: Standard HDMI screen 0|TeleFram | 2021-12-23T12:23:10.476Z [Main] info: Main app started ... 0|TeleFram | 2021-12-23T12:23:13.218Z [Main] info: [AddonInterface] Load addons... 0|TeleFram | 2021-12-23T12:23:13.227Z [Main] info: [AddonInterface] Initialize listeners... 0|TeleFram | 2021-12-23T12:23:13.234Z [Main] info: [AddonInterface] Addons loaded 0|TeleFram | 2021-12-23T12:23:13.262Z [Main] info: Add Admin-Actions 0|TeleFram | 2021-12-23T12:23:13.269Z [Main] info: Bot created! 0|TeleFram | 2021-12-23T12:23:13.380Z [Main] info: Bot started! 0|TeleFram | 2021-12-23T12:23:14.089Z [Main] info: Using bot with name BilderrahmenOma_bot. 0|TeleFram | 2021-12-23T12:23:18.893Z [Renderer] info: Renderer started ...

LukeSkywalker92 commented 2 years ago

Ok, and then you do a reboot and it stops working? It looks like the logs are from some minutes ago, so ist it working right now?

AAAbrAkAdAbrAAA commented 2 years ago

Now I did the reboot and the pi is frozen.

I can ping the pi, but can not connect through SSH

AAAbrAkAdAbrAAA commented 2 years ago

What is also strange to me: I tried it also with pm2 disabled, but the TeleFrame starts as well here at start up. Is the autostart triggered anywhere else then?

I would like configure the frame the way, that it does not start from boot up.

LukeSkywalker92 commented 2 years ago

how did you disable it? pm2 stop 0 + pm2 save?

LukeSkywalker92 commented 2 years ago

if you don't want to run teleframe at boot, you don't need pm2... then you can just run it manually

AAAbrAkAdAbrAAA commented 2 years ago

I mean when setting up the frame. within one setup I said to pm2: No But when I rebooted the frame, the application startet at startup.

LukeSkywalker92 commented 2 years ago

did you just run the install script again?

AAAbrAkAdAbrAAA commented 2 years ago

yes, sevaral times.

LukeSkywalker92 commented 2 years ago

Ok, this might be the problem. I am honestly not sure what happens when you run it multiple times. My advice would be to flash a new raspberry pi os and run the script only once with the desired settings...

AAAbrAkAdAbrAAA commented 2 years ago

okay, sorry. I mean totally from new, with new OS.

AAAbrAkAdAbrAAA commented 2 years ago

It must be outside of the TeleFrame. No I deleted TeleFrame from the pm2 List. And rebooted. But the raspberry runs into a freeze again.

Is the installation of the teleframe changing anything else anywhere for the bootup?

LukeSkywalker92 commented 2 years ago

Not really. What happens when you reboot a new OS?

LukeSkywalker92 commented 2 years ago

But you could also try the manual installation...

Chrissib1743 commented 2 years ago

@AAAbrAkAdAbrAAA Have you ever resolved this issue? I‘m having the same problem.

JanSHUP commented 2 years ago

EDITED: Freeze after Boot solved - see two posts below.

Hey everybody. I found the same issue with a Raspberry Pi 4b 4Gb with Raspberry Pi OS. I installed with "install_raspberry.sh" via SSH and also got some NPM and NodeJs warnings. (See below). Pi is not booting correctly anymore and running into black screen after ~5 seconds. SSH connection fails -> "login as:"-request and password-request are shown but after sending the password it is not responding anymore.

If anybody has an idea what went wrong or if I anyhow can get the PI back to life or avoid this behaivour at next installation I would be happy. Thanks in advance.

PS: Raspberry Pi OS was installed yesterday and kodi was compiled manually to run parallel to teleframe. Nothing else was changed systemwise.

Installation log: (unfortunately it is german)

bash -c "$(curl -sL https://raw.githubusercontent.com/LukeSkywalker92/TeleFrame/master/tools/install_raspberry.sh)"

_________ _______  _        _______  _______  _______  _______  _______  _______
\__   __/(  ____ \( \      (  ____ \(  ____ \(  ____ )(  ___  )(       )(  ____ \
   ) (   | (    \/| (      | (    \/| (    \/| (    )|| (   ) || () () || (    \/
   | |   | (__    | |      | (__    | (__    | (____)|| (___) || || || || (__
   | |   |  __)   | |      |  __)   |  __)   |     __)|  ___  || |(_)| ||  __)
   | |   | (      | |      | (      | (      | (\ (   | (   ) || |   | || (  
   | |   | (____/\| (____/\| (____/\| )      | ) \ \__| )   ( || )   ( || (____/\
   )_(   (_______/(_______/(_______/|/       |/   \__/|/     \||/     \|(_______/

Do you want to disable the screensaver (y/N)? y
Do you want your mouse pointer to be autohided (y/N)? y
Do you want to use pm2 for auto starting of your TeleFrame (y/N)? y
Do you want pm2 to wait for internet connection before auto starting your TeleFrame (y/N)? n
Please tell me your telegram bot token. Token:  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Updating packages ...
Holen:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15,0 kB]
OK:2 http://archive.raspberrypi.org/debian bullseye InRelease
Es wurden 15,0 kB in 1 s geholt (23,4 kB/s).
Paketlisten werden gelesen… Fertig
Installing helper tools ...
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
build-essential ist schon die neueste Version (12.9).
curl ist schon die neueste Version (7.74.0-1.3+deb11u1).
git ist schon die neueste Version (1:2.30.2-1).
unzip ist schon die neueste Version (6.0-26).
wget ist schon die neueste Version (1.21-1+deb11u1).
wget wurde als manuell installiert festgelegt.
x11-xserver-utils ist schon die neueste Version (7.7+8).
x11-xserver-utils wurde als manuell installiert festgelegt.
Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
  libfuse2
Verwenden Sie »sudo apt autoremove«, um es zu entfernen.
Die folgenden zusätzlichen Pakete werden installiert:
  libao-common libao4 libopencore-amrnb0 libopencore-amrwb0 libsox-fmt-alsa
  libsox-fmt-ao libsox-fmt-base libsox-fmt-mp3 libsox-fmt-oss
  libsox-fmt-pulse libsox3 unclutter-startup
Vorgeschlagene Pakete:
  libaudio2 libsndio6.1
Die folgenden NEUEN Pakete werden installiert:
  libao-common libao4 libopencore-amrnb0 libopencore-amrwb0 libsox-fmt-all
  libsox-fmt-alsa libsox-fmt-ao libsox-fmt-base libsox-fmt-mp3
  libsox-fmt-oss libsox-fmt-pulse libsox3 sox unclutter unclutter-startup
0 aktualisiert, 15 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 936 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 1.947 kB Plattenplatz zusätzlich benutzt.
Holen:1 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libao-common all 1.2.2+20180113-1.1 [11,7 kB]
Holen:2 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libao4 armhf 1.2.2+20180113-1.1 [33,6 kB]
Holen:7 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt-ao armhf 14.4.2+git20190427-2 [48,3 kB]
Holen:8 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt-base armhf 14.4.2+git20190427-2 [69,0 kB]
Holen:3 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian bullseye/main armhf libopencore-amrnb0 armhf 0.1.5-1 [85,3 kB]
Holen:11 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt-pulse armhf 14.4.2+git20190427-2 [47,9 kB]
Holen:13 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf sox armhf 14.4.2+git20190427-2 [139 kB]
Holen:4 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian bullseye/main armhf libopencore-amrwb0 armhf 0.1.5-1 [45,9 kB]
Holen:5 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox3 armhf 14.4.2+git20190427-2 [227 kB]
Holen:6 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt-alsa armhf 14.4.2+git20190427-2 [51,3 kB]
Holen:9 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt-mp3 armhf 14.4.2+git20190427-2 [56,8 kB]
Holen:10 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt-oss armhf 14.4.2+git20190427-2 [49,4 kB]
Holen:12 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt-all armhf 14.4.2+git20190427-2 [46,0 kB]
Holen:14 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian bullseye/main armhf unclutter armhf 8-25 [15,2 kB]
Holen:15 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian bullseye/main armhf unclutter-startup all 8-25 [8.860 B]
Es wurden 936 kB in 10 s geholt (91,8 kB/s).
Vorkonfiguration der Pakete ...
Vormals nicht ausgewähltes Paket libao-common wird gewählt.
(Lese Datenbank ... 111924 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../00-libao-common_1.2.2+20180113-1.1_all.deb ...
Entpacken von libao-common (1.2.2+20180113-1.1) ...
Vormals nicht ausgewähltes Paket libao4:armhf wird gewählt.
Vorbereitung zum Entpacken von .../01-libao4_1.2.2+20180113-1.1_armhf.deb ...
Entpacken von libao4:armhf (1.2.2+20180113-1.1) ...
Vormals nicht ausgewähltes Paket libopencore-amrnb0:armhf wird gewählt.
Vorbereitung zum Entpacken von .../02-libopencore-amrnb0_0.1.5-1_armhf.deb ...
Entpacken von libopencore-amrnb0:armhf (0.1.5-1) ...
Vormals nicht ausgewähltes Paket libopencore-amrwb0:armhf wird gewählt.
Vorbereitung zum Entpacken von .../03-libopencore-amrwb0_0.1.5-1_armhf.deb ...
Entpacken von libopencore-amrwb0:armhf (0.1.5-1) ...
Vormals nicht ausgewähltes Paket libsox3:armhf wird gewählt.
Vorbereitung zum Entpacken von .../04-libsox3_14.4.2+git20190427-2_armhf.deb ...
Entpacken von libsox3:armhf (14.4.2+git20190427-2) ...
Vormals nicht ausgewähltes Paket libsox-fmt-alsa:armhf wird gewählt.
Vorbereitung zum Entpacken von .../05-libsox-fmt-alsa_14.4.2+git20190427-2_armhf.deb ...
Entpacken von libsox-fmt-alsa:armhf (14.4.2+git20190427-2) ...
Vormals nicht ausgewähltes Paket libsox-fmt-ao:armhf wird gewählt.
Vorbereitung zum Entpacken von .../06-libsox-fmt-ao_14.4.2+git20190427-2_armhf.deb ...
Entpacken von libsox-fmt-ao:armhf (14.4.2+git20190427-2) ...
Vormals nicht ausgewähltes Paket libsox-fmt-base:armhf wird gewählt.
Vorbereitung zum Entpacken von .../07-libsox-fmt-base_14.4.2+git20190427-2_armhf.deb ...
Entpacken von libsox-fmt-base:armhf (14.4.2+git20190427-2) ...
Vormals nicht ausgewähltes Paket libsox-fmt-mp3:armhf wird gewählt.
Vorbereitung zum Entpacken von .../08-libsox-fmt-mp3_14.4.2+git20190427-2_armhf.deb ...
Entpacken von libsox-fmt-mp3:armhf (14.4.2+git20190427-2) ...
Vormals nicht ausgewähltes Paket libsox-fmt-oss:armhf wird gewählt.
Vorbereitung zum Entpacken von .../09-libsox-fmt-oss_14.4.2+git20190427-2_armhf.deb ...
Entpacken von libsox-fmt-oss:armhf (14.4.2+git20190427-2) ...
Vormals nicht ausgewähltes Paket libsox-fmt-pulse:armhf wird gewählt.
Vorbereitung zum Entpacken von .../10-libsox-fmt-pulse_14.4.2+git20190427-2_armhf.deb ...
Entpacken von libsox-fmt-pulse:armhf (14.4.2+git20190427-2) ...
Vormals nicht ausgewähltes Paket libsox-fmt-all:armhf wird gewählt.
Vorbereitung zum Entpacken von .../11-libsox-fmt-all_14.4.2+git20190427-2_armhf.deb ...
Entpacken von libsox-fmt-all:armhf (14.4.2+git20190427-2) ...
Vormals nicht ausgewähltes Paket sox wird gewählt.
Vorbereitung zum Entpacken von .../12-sox_14.4.2+git20190427-2_armhf.deb ...
Entpacken von sox (14.4.2+git20190427-2) ...
Vormals nicht ausgewähltes Paket unclutter wird gewählt.
Vorbereitung zum Entpacken von .../13-unclutter_8-25_armhf.deb ...
Entpacken von unclutter (8-25) ...
Vormals nicht ausgewähltes Paket unclutter-startup wird gewählt.
Vorbereitung zum Entpacken von .../14-unclutter-startup_8-25_all.deb ...
Entpacken von unclutter-startup (8-25) ...
libsox3:armhf (14.4.2+git20190427-2) wird eingerichtet ...
libsox-fmt-oss:armhf (14.4.2+git20190427-2) wird eingerichtet ...
libao-common (1.2.2+20180113-1.1) wird eingerichtet ...
libopencore-amrwb0:armhf (0.1.5-1) wird eingerichtet ...
unclutter (8-25) wird eingerichtet ...
update-alternatives: /usr/bin/unclutter-classic wird verwendet, um /usr/bin/unclutter (unclutter) im automatischen Modus bereitzustellen
libsox-fmt-alsa:armhf (14.4.2+git20190427-2) wird eingerichtet ...
libao4:armhf (1.2.2+20180113-1.1) wird eingerichtet ...
libopencore-amrnb0:armhf (0.1.5-1) wird eingerichtet ...
libsox-fmt-base:armhf (14.4.2+git20190427-2) wird eingerichtet ...
libsox-fmt-ao:armhf (14.4.2+git20190427-2) wird eingerichtet ...
unclutter-startup (8-25) wird eingerichtet ...
libsox-fmt-mp3:armhf (14.4.2+git20190427-2) wird eingerichtet ...
libsox-fmt-pulse:armhf (14.4.2+git20190427-2) wird eingerichtet ...
sox (14.4.2+git20190427-2) wird eingerichtet ...
libsox-fmt-all:armhf (14.4.2+git20190427-2) wird eingerichtet ...
Trigger für libc-bin (2.31-13+rpt2+rpi1+deb11u2) werden verarbeitet ...
Trigger für man-db (2.9.4-2) werden verarbeitet ...
Trigger für mailcap (3.69) werden verarbeitet ...
Check current Node installation ...
Node.js is not installed.
Installing Node.js ...

================================================================================
================================================================================

                              DEPRECATION WARNING

  Node.js 10.x is no longer actively supported!

  You will not receive security or critical stability updates for this version.

  You should migrate to a supported version of Node.js as soon as possible.
  Use the installation script that corresponds to the version of Node.js you
  wish to install. e.g.

   * https://deb.nodesource.com/setup_12.x — Node.js 12 LTS "Erbium"
   * https://deb.nodesource.com/setup_14.x — Node.js 14 LTS "Fermium" (recommended)
   * https://deb.nodesource.com/setup_16.x — Node.js 16 "Gallium"

  Please see https://github.com/nodejs/Release for details about which
  version may be appropriate for you.

  The NodeSource Node.js distributions repository contains
  information both about supported versions of Node.js and supported Linux
  distributions. To learn more about usage, see the repository:
    https://github.com/nodesource/distributions

================================================================================
================================================================================

Continuing in 20 seconds ...

## Installing the NodeSource Node.js 10.x repo...

## Populating apt-get cache...

+ apt-get update
OK:1 http://archive.raspberrypi.org/debian bullseye InRelease
OK:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Paketlisten werden gelesen… Fertig

## Confirming "bullseye" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_10.x/dists/bullseye/Release'

## Adding the NodeSource signing key to your keyring...

+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null

## Creating apt sources list file for the NodeSource Node.js 10.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_10.x bullseye main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_10.x bullseye main' >> /etc/apt/sources.list.d/nodesource.list

## Running `apt-get update` for you...

+ apt-get update
OK:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
OK:2 http://archive.raspberrypi.org/debian bullseye InRelease
Holen:3 https://deb.nodesource.com/node_10.x bullseye InRelease [4.586 B]
Holen:4 https://deb.nodesource.com/node_10.x bullseye/main armhf Packages [769 B]
Es wurden 5.355 B in 2 s geholt (2.521 B/s).
Paketlisten werden gelesen… Fertig

## Run `sudo apt-get install -y nodejs` to install Node.js 10.x and npm
## You may also need development tools to build native addons:
     sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
     curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null
     echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
     sudo apt-get update && sudo apt-get install yarn

Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
  libfuse2
Verwenden Sie »sudo apt autoremove«, um es zu entfernen.
Die folgenden zusätzlichen Pakete werden installiert:
  libc-ares2 libjs-highlight.js libnode72 nodejs-doc
Vorgeschlagene Pakete:
  npm
Die folgenden NEUEN Pakete werden installiert:
  libc-ares2 libjs-highlight.js libnode72 nodejs nodejs-doc
0 aktualisiert, 5 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 10,4 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 45,6 MB Plattenplatz zusätzlich benutzt.
Holen:2 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libjs-highlight.js all 9.18.5+dfsg1-1 [397 kB]
Holen:1 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libc-ares2 armhf 1.17.1-1+deb11u1 [96,0 kB]
Holen:5 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf nodejs-doc all 12.22.5~dfsg-2~11u1 [2.545 kB]
Holen:3 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libnode72 armhf 12.22.5~dfsg-2~11u1 [7.261 kB]
Holen:4 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf nodejs armhf 12.22.5~dfsg-2~11u1 [147 kB]
Es wurden 10,4 MB in 4 s geholt (2.821 kB/s).
Vormals nicht ausgewähltes Paket libc-ares2:armhf wird gewählt.
(Lese Datenbank ... 112064 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libc-ares2_1.17.1-1+deb11u1_armhf.deb ...
Entpacken von libc-ares2:armhf (1.17.1-1+deb11u1) ...
Vormals nicht ausgewähltes Paket libjs-highlight.js wird gewählt.
Vorbereitung zum Entpacken von .../libjs-highlight.js_9.18.5+dfsg1-1_all.deb ...
Entpacken von libjs-highlight.js (9.18.5+dfsg1-1) ...
Vormals nicht ausgewähltes Paket libnode72:armhf wird gewählt.
Vorbereitung zum Entpacken von .../libnode72_12.22.5~dfsg-2~11u1_armhf.deb ...
Entpacken von libnode72:armhf (12.22.5~dfsg-2~11u1) ...
Vormals nicht ausgewähltes Paket nodejs wird gewählt.
Vorbereitung zum Entpacken von .../nodejs_12.22.5~dfsg-2~11u1_armhf.deb ...
Entpacken von nodejs (12.22.5~dfsg-2~11u1) ...
Vormals nicht ausgewähltes Paket nodejs-doc wird gewählt.
Vorbereitung zum Entpacken von .../nodejs-doc_12.22.5~dfsg-2~11u1_all.deb ...
Entpacken von nodejs-doc (12.22.5~dfsg-2~11u1) ...
libc-ares2:armhf (1.17.1-1+deb11u1) wird eingerichtet ...
libnode72:armhf (12.22.5~dfsg-2~11u1) wird eingerichtet ...
libjs-highlight.js (9.18.5+dfsg1-1) wird eingerichtet ...
nodejs (12.22.5~dfsg-2~11u1) wird eingerichtet ...
update-alternatives: /usr/bin/nodejs wird verwendet, um /usr/bin/js (js) im automatischen Modus bereitzustellen
nodejs-doc (12.22.5~dfsg-2~11u1) wird eingerichtet ...
Trigger für man-db (2.9.4-2) werden verarbeitet ...
Trigger für libc-bin (2.31-13+rpt2+rpi1+deb11u2) werden verarbeitet ...
Node.js installation Done!
Cloning TeleFrame ...
Klone nach 'TeleFrame' ...
remote: Enumerating objects: 89, done.
remote: Counting objects: 100% (89/89), done.
remote: Compressing objects: 100% (81/81), done.
remote: Total 89 (delta 9), reused 44 (delta 1), pack-reused 0
Empfange Objekte: 100% (89/89), 11.54 MiB | 8.60 MiB/s, fertig.
Löse Unterschiede auf: 100% (9/9), fertig.
Cloning TeleFrame Done!
Installing dependencies ...
bash: Zeile 131: npm: Kommando nicht gefunden.
Unable to install dependencies!

###############
########### SCRIPT Stopped here and due to "NPM Comand not found" I tried to install nodejs and NPM again.
###############

pi@raspberrypi:~ $ sudo apt-get install -y nodejs
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
nodejs ist schon die neueste Version (12.22.5~dfsg-2~11u1).
Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
  libfuse2
Verwenden Sie »sudo apt autoremove«, um es zu entfernen.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

pi@raspberrypi:~ $ reboot
JanSHUP commented 2 years ago

reading the log again I guess I should have tried installing the npm package manually? at least the log suggests to install npm package: "Vorgeschlagene Pakete: npm" and doesnt install automatically - at least that is what I read there. Unfortunately I need to install Pi Os again to check if this is the real issue.

JanSHUP commented 2 years ago

Hello together,

I made a fresh PiOs installation and used the install.sh script again. got the same result as yesterday. Therefore I tried to install npm manually and try again. Unsuccessfull - see below.

sudo apt install npm
nano teleframe2.sh

I copied the install-script from line 131 where the error appeared into teleframe2.sh and finished installation

chmod +x teleframe2.sh
./teleframe2.sh

-> 
Installing dependencies ...

> teleframe@3.2.3 install
> node ./tools/install.js

added 197 packages, and audited 198 packages in 34s

6 vulnerabilities (1 low, 3 moderate, 2 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
Dependencies installation Done!
Installing electron globally ...

added 86 packages, and audited 87 packages in 29s

5 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
Electron installation Done!
Creating image directory ...
mkdir: das Verzeichnis ▒images▒ kann nicht angelegt werden: Die Datei existiert bereits
Check plymouth installation ...
./teleframe2.sh: Zeile 31: command_exists: Kommando nicht gefunden.
plymouth is not installed.

We're ready! Run DISPLAY=:0 npm start from the ~/TeleFrame directory to start your TeleFrame.

Now I tried to run teleframe: 

pi@raspberrypi:~ $ cd TeleFrame/
pi@raspberrypi:~/TeleFrame $  DISPLAY=:0 npm start

> teleframe@3.2.3 start
> electron .

2022-04-02T09:16:55.487Z [Main] info: Configuring for: Standard HDMI screen
2022-04-02T09:16:55.492Z [Main] info: Main app started ...
2022-04-02T09:16:55.909Z [Main] info: [AddonInterface] Load addons...
2022-04-02T09:16:55.910Z [Main] info: [AddonInterface] Initialize listeners...
2022-04-02T09:16:55.911Z [Main] info: [AddonInterface] Addons loaded
(node:5928) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
[5928:0402/101658.468711:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
/home/pi/TeleFrame/node_modules/electron/dist/electron exited with signal SIGTRAP
npm ERR! code 1
npm ERR! path /home/pi/TeleFrame
npm ERR! command failed
npm ERR! command sh -c electron .

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

Now I removed the ~/Teleframe folder and restarted the installation process. Installation looked better:

sudo rm -r TeleFrame
bash -c "$(curl -sL https://raw.githubusercontent.com/LukeSkywalker92/TeleFrame/master/tools/install_raspberry.sh)"

_________ _______  _        _______  _______  _______  _______  _______  _______
\__   __/(  ____ \( \      (  ____ \(  ____ \(  ____ )(  ___  )(       )(  ____ \
   ) (   | (    \/| (      | (    \/| (    \/| (    )|| (   ) || () () || (    \/
   | |   | (__    | |      | (__    | (__    | (____)|| (___) || || || || (__
   | |   |  __)   | |      |  __)   |  __)   |     __)|  ___  || |(_)| ||  __)
   | |   | (      | |      | (      | (      | (\ (   | (   ) || |   | || (
   | |   | (____/\| (____/\| (____/\| )      | ) \ \__| )   ( || )   ( || (____/\
   )_(   (_______/(_______/(_______/|/       |/   \__/|/     \||/     \|(_______/

Do you want to disable the screensaver (y/N)? y
Do you want your mouse pointer to be autohided (y/N)? y
Do you want to use pm2 for auto starting of your TeleFrame (y/N)? y
Do you want pm2 to wait for internet connection before auto starting your TeleFrame (y/N)? y
Please tell me your telegram bot token. Token:  XXXXXXXXXXXXXXXXXXXXXXXXXXX
Updating packages ...
OK:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
OK:2 http://archive.raspberrypi.org/debian bullseye InRelease
OK:3 https://deb.nodesource.com/node_10.x bullseye InRelease
Paketlisten werden gelesen... Fertig
Installing helper tools ...
Paketlisten werden gelesen... Fertig
Abh▒ngigkeitsbaum wird aufgebaut... Fertig
Statusinformationen werden eingelesen... Fertig
build-essential ist schon die neueste Version (12.9).
curl ist schon die neueste Version (7.74.0-1.3+deb11u1).
git ist schon die neueste Version (1:2.30.2-1).
libsox-fmt-all ist schon die neueste Version (14.4.2+git20190427-2).
sox ist schon die neueste Version (14.4.2+git20190427-2).
unclutter ist schon die neueste Version (8-25).
unzip ist schon die neueste Version (6.0-26).
wget ist schon die neueste Version (1.21-1+deb11u1).
x11-xserver-utils ist schon die neueste Version (7.7+8).
Das folgende Paket wurde automatisch installiert und wird nicht mehr ben▒tigt:
  libfuse2
Verwenden Sie ▒sudo apt autoremove▒, um es zu entfernen.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 91 nicht aktualisiert.
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v10.15.2
Installed Node version: v12.22.5
No Node.js upgrade necessary.
Cloning TeleFrame ...
Klone nach 'TeleFrame' ...
remote: Enumerating objects: 89, done.
remote: Counting objects: 100% (89/89), done.
remote: Compressing objects: 100% (81/81), done.
remote: Total 89 (delta 9), reused 44 (delta 1), pack-reused 0
Empfange Objekte: 100% (89/89), 11.54 MiB | 10.30 MiB/s, fertig.
L▒se Unterschiede auf: 100% (9/9), fertig.
Cloning TeleFrame Done!
Installing dependencies ...

> teleframe@3.2.3 install
> node ./tools/install.js

added 197 packages, and audited 198 packages in 16s

6 vulnerabilities (1 low, 3 moderate, 2 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
Dependencies installation Done!
Installing electron globally ...

changed 86 packages, and audited 87 packages in 15s

5 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
Electron installation Done!
Creating image directory ...
mkdir: das Verzeichnis ▒images▒ kann nicht angelegt werden: Die Datei existiert bereits
Check plymouth installation ...
Splashscreen: Checking themes directory.
Splashscreen: Create theme directory if not exists.
Splashscreen: Theme copied successfully.
Splashscreen: Changed theme to TeleFrame successfully.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.

added 183 packages, and audited 184 packages in 21s

12 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

                        -------------

__/\\\\\\\\\\\\\____/\\\\____________/\\\\____/\\\\\\\\\_____
 _\/\\\/////////\\\_\/\\\\\\________/\\\\\\__/\\\///////\\\___
  _\/\\\_______\/\\\_\/\\\//\\\____/\\\//\\\_\///______\//\\\__
   _\/\\\\\\\\\\\\\/__\/\\\\///\\\/\\\/_\/\\\___________/\\\/___
    _\/\\\/////////____\/\\\__\///\\\/___\/\\\________/\\\//_____
     _\/\\\_____________\/\\\____\///_____\/\\\_____/\\\//________
      _\/\\\_____________\/\\\_____________\/\\\___/\\\/___________
       _\/\\\_____________\/\\\_____________\/\\\__/\\\\\\\\\\\\\\\_
        _\///______________\///______________\///__\///////////////__

                          Runtime Edition

        PM2 is a Production Process Manager for Node.js applications
                     with a built-in Load Balancer.

                Start and Daemonize any application:
                $ pm2 start app.js

                Load Balance 4 instances of api.js:
                $ pm2 start api.js -i 4

                Monitor in production:
                $ pm2 monitor

                Make pm2 auto-boot at server restart:
                $ pm2 startup

                To go further checkout:
                http://pm2.io/

                        -------------

[PM2] Init System found: systemd
Platform systemd
Template
[Unit]
Description=PM2 process manager
Documentation=https://pm2.keymetrics.io/
After=network.target

[Service]
Type=forking
User=pi
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
Environment=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games:/usr/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Environment=PM2_HOME=/home/pi/.pm2
PIDFile=/home/pi/.pm2/pm2.pid
Restart=on-failure

ExecStart=/usr/local/lib/node_modules/pm2/bin/pm2 resurrect
ExecReload=/usr/local/lib/node_modules/pm2/bin/pm2 reload all
ExecStop=/usr/local/lib/node_modules/pm2/bin/pm2 kill

[Install]
WantedBy=multi-user.target

Target path
/etc/systemd/system/pm2-pi.service
Command list
[ 'systemctl enable pm2-pi' ]
[PM2] Writing init configuration in /etc/systemd/system/pm2-pi.service
[PM2] Making script booting at startup...
[PM2] [-] Executing: systemctl enable pm2-pi...
Created symlink /etc/systemd/system/multi-user.target.wants/pm2-pi.service -> /etc/systemd/system/pm2-pi.service.
[PM2] [v] Command successfully executed.
+---------------------------------------+
[PM2] Freeze a process list on reboot via:
$ pm2 save

[PM2] Remove init script via:
$ pm2 unstartup systemd

                        -------------

__/\\\\\\\\\\\\\____/\\\\____________/\\\\____/\\\\\\\\\_____
 _\/\\\/////////\\\_\/\\\\\\________/\\\\\\__/\\\///////\\\___
  _\/\\\_______\/\\\_\/\\\//\\\____/\\\//\\\_\///______\//\\\__
   _\/\\\\\\\\\\\\\/__\/\\\\///\\\/\\\/_\/\\\___________/\\\/___
    _\/\\\/////////____\/\\\__\///\\\/___\/\\\________/\\\//_____
     _\/\\\_____________\/\\\____\///_____\/\\\_____/\\\//________
      _\/\\\_____________\/\\\_____________\/\\\___/\\\/___________
       _\/\\\_____________\/\\\_____________\/\\\__/\\\\\\\\\\\\\\\_
        _\///______________\///______________\///__\///////////////__

                          Runtime Edition

        PM2 is a Production Process Manager for Node.js applications
                     with a built-in Load Balancer.

                Start and Daemonize any application:
                $ pm2 start app.js

                Load Balance 4 instances of api.js:
                $ pm2 start api.js -i 4

                Monitor in production:
                $ pm2 monitor

                Make pm2 auto-boot at server restart:
                $ pm2 startup

                To go further checkout:
                http://pm2.io/

                        -------------

[PM2] Spawning PM2 daemon with pm2_home=/home/pi/.pm2
[PM2] PM2 Successfully daemonized
[PM2][WARN] Applications TeleFrame not running, starting...
[PM2] App [TeleFrame] launched (1 instances)
┌─────┬──────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id  │ name         │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├─────┼──────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0   │ TeleFrame    │ default     │ 3.2.3   │ fork    │ 6404     │ 0s     │ 0    │ online    │ 0%       │ 1.7mb    │ pi       │ enabled  │
└─────┴──────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
[PM2] Saving current process list...
[PM2] Successfully saved in /home/pi/.pm2/dump.pm2

We're ready! Run DISPLAY=:0 npm start from the ~/TeleFrame directory to start your TeleFrame.

Teleframe started automatically with a blank screen all approx. 5 seconds and closed automatically again Therefore I disabled the pm2 serviece and tried to start it manually

sudo systemctl disable pm2-pi.service
sudo systemctl stop pm2-pi.service
pi@raspberrypi:~/TeleFrame $ DISPLAY=:0 npm start

> teleframe@3.2.3 start
> electron .

2022-04-02T09:32:22.826Z [Main] info: Configuring for: Standard HDMI screen
2022-04-02T09:32:22.832Z [Main] info: Main app started ...
2022-04-02T09:32:23.266Z [Main] info: [AddonInterface] Load addons...
2022-04-02T09:32:23.271Z [Main] info: [AddonInterface] Initialize listeners...
2022-04-02T09:32:23.275Z [Main] info: [AddonInterface] Addons loaded
2022-04-02T09:32:23.317Z [Main] info: Add Admin-Actions
2022-04-02T09:32:23.319Z [Main] info: Bot created!
2022-04-02T09:32:23.340Z [Main] info: Bot started!
(node:8721) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
2022-04-02T09:32:23.628Z [Main] info: Using bot with name EJ_Fotorahmen_bot.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
[8721:0402/103226.179062:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
/home/pi/TeleFrame/node_modules/electron/dist/electron exited with signal SIGTRAP
npm ERR! code 1
npm ERR! path /home/pi/TeleFrame
npm ERR! command failed
npm ERR! command sh -c electron .

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

NPM Log looks like this:

nano /home/pi/.npm/_logs/2022-04-02T09_32_26_299Z-debug.log

0 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
1 info using npm@7.5.2
2 info using node@v12.22.5
3 timing config:load:defaults Completed in 6ms
4 timing config:load:file:/usr/share/nodejs/npm/npmrc Completed in 8ms
5 timing config:load:builtin Completed in 8ms
6 timing config:load:cli Completed in 6ms
7 timing config:load:env Completed in 1ms
8 timing config:load:file:/home/pi/TeleFrame/.npmrc Completed in 1ms
9 timing config:load:project Completed in 4ms
10 timing config:load:file:/home/pi/.npmrc Completed in 1ms
11 timing config:load:user Completed in 1ms
12 timing config:load:file:/etc/npmrc Completed in 1ms
13 timing config:load:global Completed in 1ms
14 timing config:load:cafile Completed in 1ms
15 timing config:load:validate Completed in 1ms
16 timing config:load:setUserAgent Completed in 2ms
17 timing config:load:setEnvs Completed in 4ms
18 timing config:load Completed in 36ms
19 verbose npm-session 0a69a3ba214654c1
20 timing npm:load Completed in 75ms
21 timing command:run-script Completed in 5171ms
22 timing command:start Completed in 5180ms
23 verbose stack Error: command failed
23 verbose stack     at ChildProcess.<anonymous> (/usr/share/nodejs/@npmcli/promise-spawn/index.js:64:27)
23 verbose stack     at ChildProcess.emit (events.js:314:20)
23 verbose stack     at maybeClose (internal/child_process.js:1022:16)
23 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
24 verbose pkgid teleframe@3.2.3
25 verbose cwd /home/pi/TeleFrame
26 verbose Linux 5.10.92-v7l+
27 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
28 verbose node v12.22.5
29 verbose npm  v7.5.2
30 error code 1
31 error path /home/pi/TeleFrame
32 error command failed
33 error command sh -c electron .
34 verbose exit 1

I rebooted the PI with 

sudo reboot

and got again into the stucked mode I was yesterday. After SSH authentification SSH stops working (cant write or send). After reboot I see the black Teleframe logo for a second and than it hangs again.

JanSHUP commented 2 years ago

Boot-Lock solved, NPM error still persistent

Wondering that it still stuck beside the service beeing disabled I had a closer look at the installation script and made a change in /boot/config.txt having the SD card inserted into a Windows machine:

I commented the added dtoverlay

#dtoverlay=vc4-fkms-v3d

now it is booting again.

A first google search revealed, that it could be the combination of the newest Raspberry Pi OS with the display (mine is Waveshare 10.1 Touchscreen) and dtoverlay=vc4-fkms-v3d.

Nevertheless, teleframe is still not starting. Showing the white starting screen shortly but crashing a second later after using 

npm start

In terminal again I get:

 DISPLAY=:0 npm start

> teleframe@3.2.3 start
> electron .

2022-04-02T13:40:12.868Z [Main] info: Configuring for: Standard HDMI screen
2022-04-02T13:40:12.872Z [Main] info: Main app started ...
2022-04-02T13:40:13.170Z [Main] info: [AddonInterface] Load addons...
2022-04-02T13:40:13.171Z [Main] info: [AddonInterface] Initialize listeners...
2022-04-02T13:40:13.174Z [Main] info: [AddonInterface] Addons loaded
2022-04-02T13:40:13.216Z [Main] info: Add Admin-Actions
2022-04-02T13:40:13.217Z [Main] info: Bot created!
2022-04-02T13:40:13.249Z [Main] info: Bot started!
(node:1578) electron: The default of contextIsolation is deprecated and will be                                                                              changing from false to true in a future release of Electron.  See https://github                                                                             .com/electron/electron/issues/23506 for more information
2022-04-02T13:40:13.491Z [Main] info: Using bot with name EJ_Fotorahmen_bot.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-                                                                             bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-                                                                             bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-                                                                             bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-                                                                             bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-                                                                             bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-                                                                             bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-                                                                             bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-                                                                             bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-                                                                             bpf failure in syscall 0403
[1578:0402/144015.759339:FATAL:gpu_data_manager_impl_private.cc(445)] GPU proces                                                                             s isn't usable. Goodbye.
/home/pi/TeleFrame/node_modules/electron/dist/electron exited with signal SIGTRA                                                                             P
npm ERR! code 1
npm ERR! path /home/pi/TeleFrame
npm ERR! command failed
npm ERR! command sh -c electron .

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

I don't know if this error is related to the boot problem and the overlay but I guess it is not.