Automatic install & run issues with Raspberry Pi Os Bullseye #183

JanSHUP · 2022-04-03T21:07:32Z

Hey together,

the last days I tried to get TeleFrame running on Bullseye on a RPi 4b 4Gb but find some differences to Buster:

the automatic added "dtoverlay=vc4-fkms-v3d" is not used by Bullseye anymore. In my (and some others cases) the overlay results in a frozen boot state.
npm is not installed automatically with nodejs by the automatic installation script (see below)
I get some further problems installing / starting the teleframe (see below) e.g.:

raspberrypi kernel: Unhandled prefetch abort: breakpoint debug exception (0x222)
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0403
[8096:0403/224531.695448: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
(I disabled the dtoverlay from 1), otherwise boot alway froze. But I guess this is not the matter why I get these errors. Probably it is more about the wrong npm, electron, nodejs versions?)

I couldn't get it running yet! I changed back to Buster for a comparison and everything ran as expected.

Details:
Installation on a fresh Raspberry Pi OS Bullseye (official image from 2022.01.28):

pi@raspberrypi:~ $ bash -c "$(curl -sL https://raw.githubusercontent.com/LukeSky                                                                             walker92/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)? n
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
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-commo                                                                             n all 1.2.2+20180113-1.1 [11,7 kB]
Holen:2 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libao4 armh                                                                             f 1.2.2+20180113-1.1 [33,6 kB]
Holen:4 http://ftp.gwdg.de/pub/linux/debian/raspbian/raspbian bullseye/main armh                                                                             f libopencore-amrwb0 armhf 0.1.5-1 [45,9 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:5 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox3 arm                                                                             hf 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:7 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt-                                                                             ao armhf 14.4.2+git20190427-2 [48,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:8 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt-                                                                             base armhf 14.4.2+git20190427-2 [69,0 kB]
Holen:10 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt                                                                             -oss armhf 14.4.2+git20190427-2 [49,4 kB]
Holen:11 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt                                                                             -pulse armhf 14.4.2+git20190427-2 [47,9 kB]
Holen:12 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libsox-fmt                                                                             -all armhf 14.4.2+git20190427-2 [46,0 kB]
Holen:13 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf sox armhf                                                                              14.4.2+git20190427-2 [139 kB]
Holen:14 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf u                                                                             nclutter armhf 8-25 [15,2 kB]
Holen:15 http://mirror1.hs-esslingen.de/pub/Mirrors/archive.raspbian.org/raspbia                                                                             n bullseye/main armhf unclutter-startup all 8-25 [8.860 B]
Es wurden 936 kB in 3 s geholt (293 kB/s).
Vorkonfiguration der Pakete ...
Vormals nicht ausgewähltes Paket libao-common wird gewählt.
(Lese Datenbank ... 100218 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://archive.raspberrypi.org/debian bullseye InRelease
OK:2 http://raspbian.raspberrypi.org/raspbian 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 (3.157 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:1 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libc-ares2 armhf 1.17.1-1+deb11u1 [96,0 kB]
Holen:2 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libjs-highlight.js all 9.18.5+dfsg1-1 [397 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]
Holen:5 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf nodejs-doc all 12.22.5~dfsg-2~11u1 [2.545 kB]
Es wurden 10,4 MB in 2 s geholt (5.160 kB/s).
Vormals nicht ausgewähltes Paket libc-ares2:armhf wird gewählt.
(Lese Datenbank ... 100358 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 | 5.85 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!

npm was not found so I installed npm manually and reinstall Teleframe

sudo apt install npm
sudo rm -r ~/TeleFrame
pi@raspberrypi:~ $ bash -c "$(curl -sL https://raw.githubusercontent.com/LukeSky                                                                             walker92/TeleFrame/master/tools/install_raspberry.sh)"

this time it installs without error but I get some warnings about old NPM files:

pi@raspberrypi:~ $ 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)? n
Please tell me your telegram bot token. Token:  XXXXXXXXXXXXXXXXXXXXXXXXXX
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).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 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 | 9.97 MiB/s, fertig.
Löse Unterschiede auf: 100% (9/9), fertig.
Cloning TeleFrame Done!
Installing dependencies ...
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: 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.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142

> [email protected] install
> node ./tools/install.js


added 197 packages, and audited 198 packages in 28s

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

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 17s

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.

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

get NPM and electron versions

pi@raspberrypi:~ $ npm version
{
  npm: '7.5.2',
  node: '12.22.5',
  v8: '7.8.279.23-node.56',
  uv: '1.40.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.17.1',
  modules: '72',
  nghttp2: '1.43.0',
  napi: '8',
  llhttp: '2.1.3',
  http_parser: '2.9.4',
  openssl: '1.1.1k',
  cldr: '37.0',
  icu: '67.1',
  tz: '2019c',
  unicode: '13.0'
}
pi@raspberrypi:~/TeleFrame $ electron --version
v18.0.1

starting the teleframe again

pi@raspberrypi:~/TeleFrame $ DISPLAY=:0 npm start --verbose
npm verb cli [ '/usr/bin/node', '/usr/bin/npm', 'start', '--verbose' ]
npm info using [email protected]
npm info using [email protected]
npm timing config:load:defaults Completed in 4ms
npm timing config:load:file:/usr/share/nodejs/npm/npmrc Completed in 5ms
npm timing config:load:builtin Completed in 6ms
npm timing config:load:cli Completed in 7ms
npm timing config:load:env Completed in 1ms
npm timing config:load:file:/home/pi/TeleFrame/.npmrc Completed in 1ms
npm timing config:load:project Completed in 3ms
npm timing config:load:file:/home/pi/.npmrc Completed in 0ms
npm timing config:load:user Completed in 0ms
npm timing config:load:file:/etc/npmrc Completed in 0ms
npm timing config:load:global Completed in 1ms
npm timing config:load:cafile Completed in 1ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:setUserAgent Completed in 2ms
npm timing config:load:setEnvs Completed in 3ms
npm timing config:load Completed in 28ms
npm verb npm-session 817eb0998461d7e8
npm timing npm:load Completed in 68ms
[..................] \ : timing npm:load Completed in 68ms
> [email protected] start
> electron .

2022-04-03T20:19:45.347Z [Main] info: Configuring for: Standard HDMI screen
2022-04-03T20:19:45.352Z [Main] info: Main app started ...
2022-04-03T20:19:45.680Z [Main] info: [AddonInterface] Load addons...
2022-04-03T20:19:45.681Z [Main] info: [AddonInterface] Initialize listeners...
2022-04-03T20:19:45.682Z [Main] info: [AddonInterface] Addons loaded
2022-04-03T20:19:45.709Z [Main] info: Add Admin-Actions
2022-04-03T20:19:45.711Z [Main] info: Bot created!
2022-04-03T20:19:45.729Z [Main] info: Bot started! in 68ms
(node:7192) 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-03T20:19:45.939Z [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
[7192:0403/221948.532070: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 timing command:run-script Completed in 5949ms
npm timing command:start Completed in 5957ms
npm verb stack Error: command failed
npm verb stack     at ChildProcess.<anonymous> (/usr/share/nodejs/@npmcli/promise-spawn/index.js:64:27)
npm verb stack     at ChildProcess.emit (events.js:314:20)
npm verb stack     at maybeClose (internal/child_process.js:1022:16)
npm verb stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
npm verb pkgid [email protected]
npm verb cwd /home/pi/TeleFrame
npm verb Linux 5.15.30-v7l+
npm verb argv "/usr/bin/node" "/usr/bin/npm" "start" "--verbose"
npm verb node v12.22.5
npm verb npm  v7.5.2
npm ERR! code 1
npm ERR! path /home/pi/TeleFrame
npm ERR! command failed
npm ERR! command sh -c electron .
npm verb exit 1
npm timing npm Completed in 6595ms

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

White teleframe start screen is shown for a second and the telegram bot is answering to e.g. "/start" and than crashes

Now using the recommended way to update NPM:

pi@raspberrypi:~/TeleFrame $ sudo npm install npm@latest -g
[ -z "$npm_config_arch" ] && (echo -e "# npm archive configuration\nexport npm_config_arch=\$(uname -m)" >> ~/.profile)
export npm_config_arch=$(uname -m)
cd ~/TeleFrame
rm -rf node_modules/
npm install --arch=$(uname -m)

added 1 package, and audited 201 packages in 6s

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

found 0 vulnerabilities

> [email protected] install
> node ./tools/install.js


added 197 packages, and audited 198 packages in 17s

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.

get versions

pi@raspberrypi:~/TeleFrame $ npm version
{
  teleframe: '3.2.3',
  npm: '7.5.2',
  node: '12.22.5',
  v8: '7.8.279.23-node.56',
  uv: '1.40.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.17.1',
  modules: '72',
  nghttp2: '1.43.0',
  napi: '8',
  llhttp: '2.1.3',
  http_parser: '2.9.4',
  openssl: '1.1.1k',
  cldr: '37.0',
  icu: '67.1',
  tz: '2019c',
  unicode: '13.0'
}
pi@raspberrypi:~/TeleFrame $ electron --version
v18.0.1

start Teleframe again

pi@raspberrypi:~/TeleFrame $ DISPLAY=:0 npm start --verbose
npm verb cli [ '/usr/bin/node', '/usr/bin/npm', 'start', '--verbose' ]
npm info using [email protected]
npm info using [email protected]
npm timing config:load:defaults Completed in 4ms
npm timing config:load:file:/usr/share/nodejs/npm/npmrc Completed in 5ms
npm timing config:load:builtin Completed in 6ms
npm timing config:load:cli Completed in 7ms
npm timing config:load:env Completed in 1ms
npm timing config:load:file:/home/pi/TeleFrame/.npmrc Completed in 1ms
npm timing config:load:project Completed in 3ms
npm timing config:load:file:/home/pi/.npmrc Completed in 0ms
npm timing config:load:user Completed in 0ms
npm timing config:load:file:/etc/npmrc Completed in 1ms
npm timing config:load:global Completed in 1ms
npm timing config:load:cafile Completed in 0ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:setUserAgent Completed in 2ms
npm timing config:load:setEnvs Completed in 2ms
npm timing config:load Completed in 27ms
npm verb npm-session d08eb7b6a0659174
npm timing npm:load Completed in 66ms
[..................] \ : timing npm:load Completed in 66ms
> [email protected] start
> electron .

2022-04-03T20:45:28.762Z [Main] info: Configuring for: Standard HDMI screen
2022-04-03T20:45:28.767Z [Main] info: Main app started ...
2022-04-03T20:45:29.118Z [Main] info: [AddonInterface] Load addons...
2022-04-03T20:45:29.119Z [Main] info: [AddonInterface] Initialize listeners...
2022-04-03T20:45:29.120Z [Main] info: [AddonInterface] Addons loaded
2022-04-03T20:45:29.147Z [Main] info: Add Admin-Actions
2022-04-03T20:45:29.148Z [Main] info: Bot created!
2022-04-03T20:45:29.153Z [Main] info: Bot started!
(node:8096) 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-03T20:45:29.404Z [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
[8096:0403/224531.695448: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 timing command:run-script Completed in 4482ms
npm timing command:start Completed in 4490ms
npm verb exit 0
npm timing npm Completed in 5011ms
npm info ok

get npm log

nano ~/.npm/_logs/2022-04-03T20_45_48_273Z-debug-0.log

0 verbose cli /usr/bin/node /usr/local/bin/npm
1 info using [email protected]
2 info using [email protected]
3 timing npm:load:whichnode Completed in 1ms
4 timing config:load:defaults Completed in 6ms
5 timing config:load:file:/usr/local/lib/node_modules/npm/npmrc Completed in 7ms
6 timing config:load:builtin Completed in 7ms
7 timing config:load:cli Completed in 5ms
8 timing config:load:env Completed in 1ms
9 timing config:load:file:/home/pi/TeleFrame/.npmrc Completed in 0ms
10 timing config:load:project Completed in 5ms
11 timing config:load:file:/home/pi/.npmrc Completed in 0ms
12 timing config:load:user Completed in 0ms
13 timing config:load:file:/etc/npmrc Completed in 0ms
14 timing config:load:global Completed in 0ms
15 timing config:load:validate Completed in 1ms
16 timing config:load:credentials Completed in 3ms
17 timing config:load:setEnvs Completed in 3ms
18 timing config:load Completed in 33ms
19 timing npm:load:configload Completed in 33ms
20 timing npm:load:mkdirpcache Completed in 4ms
21 timing npm:load:mkdirplogs Completed in 1ms
22 verbose title npm start
23 verbose argv "start"
24 timing npm:load:setTitle Completed in 4ms
25 timing config:load:flatten Completed in 10ms
26 timing npm:load:display Completed in 22ms
27 verbose logfile logs-max:10 dir:/home/pi/.npm/_logs
28 verbose logfile /home/pi/.npm/_logs/2022-04-03T20_45_48_273Z-debug-0.log
29 timing npm:load:logFile Completed in 17ms
30 timing npm:load:timers Completed in 0ms
31 timing npm:load:configScope Completed in 1ms
32 timing npm:load Completed in 85ms
33 silly logfile done cleaning log files
34 http fetch GET 200 https://registry.npmjs.org/npm 745ms (cache miss)
35 http fetch GET 200 https://registry.npmjs.org/npm 852ms (cache miss)
36 timing command:run-script Completed in 4742ms
37 timing command:start Completed in 4752ms
38 verbose exit 1
39 timing npm Completed in 4866ms

in journalctl -xe i find:

Apr 03 22:56:04 raspberrypi kernel: Unhandled prefetch abort: breakpoint debug exception (0x222) at 0x00000000

Do you have any ideas what could be wrong or how I could continue debugging?

Thanks

The text was updated successfully, but these errors were encountered:

reiseradeln · 2022-06-20T14:19:41Z

Hi @JanSHUP,

I just tried to install TeleFrame on a new Raspberry Pi. In the end it worked.

Update the Pi
sudo apt-get update
sudo apt-get upgrade
Install Node package manager - npm
sudo apt-get install npm
Install latest node version
sudo npm install -g n@latest
Install latest v8 version
sudo npm install -g v8@latest
Install TeleFrame
bash -c "$(curl -sL https://raw.githubusercontent.com/LukeSkywalker92/TeleFrame/master/tools/install_raspberry.sh)"
Prevent boot freeze by comment out the last line in config.txt.
sudo nano /boot/config.txt
#dtoverlay=vc4-fkms-v3d
Prevent stuck at TeleFrame startscreen (Thanks to @celphicious)
cd TeleFrame/
nano main.js
-> Add the bold marked line after line 42

	// Create the browser window.
	win = new BrowserWindow({
	width: 1024,
	height: 600,
	webPreferences: {
	nodeIntegration: true,
	enableRemoteModule: true, //don't miss the comma
	contextIsolation: false //this had to be added!
	},
	});

With this the installation was successful on Bullseye (image from 04-04-2022).

Cheers Tim

rtulke · 2023-03-20T21:27:15Z

This also works for me @reiseradeln thx!

Raspbian OS

Release date: February 21st 2023
System: 32-bit
Kernel version: 5.15
Debian version: 11 (bullseye)

root@raspberrypi:~# cat /etc/debian_version
11.6

root@raspberrypi:~# npm -v
7.5.2

pi@raspberrypi:~/TeleFrame $ npm version
{
  teleframe: '3.2.3',
  npm: '7.5.2',
  node: '12.22.12',
  v8: '7.8.279.23-node.57',
  uv: '1.40.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.17.1',
  modules: '72',
  nghttp2: '1.43.0',
  napi: '8',
  llhttp: '2.1.6',
  http_parser: '2.9.4',
  openssl: '1.1.1n',
  cldr: '37.0',
  icu: '67.1',
  tz: '2019c',
  unicode: '13.0'
}

matzetronic · 2023-08-02T10:32:25Z

Hi @JanSHUP,

I just tried to install TeleFrame on a new Raspberry Pi. In the end it worked.

1. Update the Pi
   `sudo apt-get update`
   `sudo apt-get upgrade`

2. Install Node package manager - npm
   `sudo apt-get install npm`

3. Install latest node version
   `sudo npm install -g n@latest`

4. Install latest v8 version
   `sudo npm install -g v8@latest`

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

6. Prevent boot freeze by comment out the last line in config.txt.
   `sudo nano /boot/config.txt`
   `#dtoverlay=vc4-fkms-v3d`

7. Prevent stuck at TeleFrame startscreen (Thanks to @celphicious)
   `cd TeleFrame/`
   `nano main.js`
   -> Add the bold marked line after line 42

	// Create the browser window.
	win = new BrowserWindow({
	width: 1024,
	height: 600,
	webPreferences: {
	nodeIntegration: true,
	enableRemoteModule: true, //don't miss the comma
	contextIsolation: false //this had to be added!
	},
	});

With this the installation was successful on Bullseye (image from 04-04-2022).

Cheers Tim

For me these installation instructions failed because electron 25.x did not start because of strange errors like

../../buildtools/third_party/libc++/trunk/include/vector:1471: assertion __n < size() failed: vector[] index out of bounds[3650:0802/121144.157697:ERROR:gpu_process_host.cc(954)] GPU process exited unexpectedly: exit_code=6

So I removed the globally installed electron (v25):
sudo npm remove electron -g

And also globally installed v8 (if you have it installed):
sudo npm remove v8 -g

And instead of instruction 4. from above do the following:
4. Install lts version of node (I think this is missing in the list above):
sudo n lts

Then in your teleframe folder you can try to start it via:
DISPLAY=:0 npm start
This will use electron 13.x in your TeleFrame/node_modules folder. As this will be already installed by running the installer or npm install inside your TeleFrame folder. Also I don't understand the recommendation to have it installed globally. Then you have it installed twice, once globally (in /usr/local/lib/node_modules and in TeleFrame/node_modules) which is quite confusing.

npm version
{
  teleframe: '3.2.3',
  npm: '9.6.7',
  node: '18.17.0',
  acorn: '8.8.2',
  ada: '2.5.0',
  ares: '1.19.1',
  brotli: '1.0.9',
  cldr: '43.0',
  icu: '73.1',
  llhttp: '6.0.11',
  modules: '108',
  napi: '9',
  nghttp2: '1.52.0',
  nghttp3: '0.7.0',
  ngtcp2: '0.8.1',
  openssl: '3.0.9+quic',
  simdutf: '3.2.12',
  tz: '2023c',
  undici: '5.22.1',
  unicode: '15.0',
  uv: '1.44.2',
  uvwasi: '0.0.18',
  v8: '10.2.154.26-node.26',
  zlib: '1.2.13.1-motley'
}
pi@teleframe:~/TeleFrame $ npx electron -v
v13.6.6

For me it works with these versions on a pi3 using bullseye, hope it helps 👍🏻

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Automatic install & run issues with Raspberry Pi Os Bullseye #183

Automatic install & run issues with Raspberry Pi Os Bullseye #183

JanSHUP commented Apr 3, 2022 •

edited

Loading

reiseradeln commented Jun 20, 2022

rtulke commented Mar 20, 2023 •

edited

Loading

matzetronic commented Aug 2, 2023

Automatic install & run issues with Raspberry Pi Os Bullseye #183

Automatic install & run issues with Raspberry Pi Os Bullseye #183

Comments

JanSHUP commented Apr 3, 2022 • edited Loading

reiseradeln commented Jun 20, 2022

rtulke commented Mar 20, 2023 • edited Loading

matzetronic commented Aug 2, 2023

JanSHUP commented Apr 3, 2022 •

edited

Loading

rtulke commented Mar 20, 2023 •

edited

Loading