Fix Raspberry Pi 4 Model B support / Upgrade to Raspbian Buster

[vpetersson]

It has become evident that the support for Pi 4 is broken. I'm going to use this ticket to track the remaining efforts to get this across the finishing line. It's a large and complex task unfortunately with many moving parts.

The status below reflects the current status of a manual installation on Raspbian Buster (Lite) on a Raspberry Pi 4 Model B.

Update for Experimental branch

• Raspberry Pi 3 Model B
  • Assets
    • Web
    • Images
    • Video
  • Balena
  • Native
  • Splash Screen
• Raspberry Pi 4 Model B
  • Assets
    • Web
    • Images
    • Video
  • Balena
  • Native
  • Splash Screen

This task is becoming ginormous. I've created a new milestone to track this instead.
https://github.com/Screenly/screenly-ose/milestone/12

Here are the outstanding issues on Development branch:

- [x] Installation (development branch)
- [x] Web interface
- [x] Display of webpages
- [x] Display of images
- [x] Display of videos
~~ - Unclear if h265 works at the moment~~
- [ ] Splash screen isn't working
~~ - This appears to be a Raspberry Pi 4 Model B issue only. Moving the SD card to a Raspberry Pi 3 Model B brings back the splash screen back just fine.
~~ - I've created this forum post to try to troubleshoot the issue

Tasks once QC/QA has been performed:

• Create new disk image (this pull request needs to be merged before)
• Merge master to production

[bf8392]

Display of webpages was not working on my pi 4 (not properly rendered)

[vpetersson]

Not sure what you're testing with @bd8392 but it works fine for me. I have Hacker News loaded on the screen in my lab without issues. If you're talking about some kind of complex page, then that is out of the scope of this issue. This is purely about getting the Pi 4 to work, not about extending the functionality of the browser.

[bf8392]

Not sure what you're testing with @bd8392 but it works fine for me. I have Hacker News loaded on the screen in my lab without issues. If you're talking about some kind of complex page, then that is out of the scope of this issue. This is purely about getting the Pi 4 to work, not about extending the functionality of the browser.

Oh okay I tested two wordpress-sites....both were not working but Google worked...

[vpetersson]

Just a note on the splash screen. As I mentioned to @ealmonte32 here, it's currently unclear if the issue is related to the Pi 4 or Buster.

[bf8392]

Can you deacitvate overscan in boot.txt by default image? Because on 99% of screens it produces unwanted black-bars...

[vpetersson]

No, this is about splash screen. It has nothing to do with overscan.

[bf8392]

No, this is about splash screen. It has nothing to do with overscan.

OHHH okay I'm sorry =). The Black bars really afffect just splash...Just tested one =)

[ealmonte32]

No, this is about splash screen. It has nothing to do with overscan.

OHHH okay I'm sorry =). The Black bars really afffect just splash...Just tested one =)

You can do this yourself manually, just go into the /boot/config.txt file and make the changes there. Read over the comments on that file or even on raspberry pi website, and you will see it is very easy to configure overscan and adjust for your tv/monitor. You can even do it when you have the SD card inserted in your computer, you can edit the config.txt file directly from there.

[ealmonte32]

@vpetersson
This is regarding the splash screen issue.
I found these instructions 1 and 2, and without plymouth or themes, splash screen is working by using framebuffer image viewer fbi only.

Raspbian Buster Lite on RPi4.

The splashscreen.service file:

pi@pi4blk:~ $ cat /etc/systemd/system/splashscreen.service 
[Unit]
Description=Screenly splash screen
DefaultDependencies=no
After=local-fs.target

[Service]
ExecStart=/usr/bin/fbi -d /dev/fb0 --noverbose -a /home/pi/screenlylogo.png
StandardInput=tty
StandardOutput=tty

[Install]
WantedBy=sysinit.target

The /boot/cmdline.txt file:

pi@pi4blk:~ $ cat /boot/cmdline.txt 
console=serial0,115200 console=tty1 root=PARTUUID=53c6e06f-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait logo.nologo quiet

[vpetersson]

So we used to use fbi in the early days but we moved away from it because the upstream Raspbian adopted plymouth. Thus I'm not sure it would make sense to move back.

[shaqaruden]

From my research using fbi seems to be the common method for Raspbian Lite

[vpetersson]

Yes, this is true. That's why we started using it. However, it has a number of drawbacks over Plymouth.

[ealmonte32]

So we used to use fbi in the early days but we moved away from it because the upstream Raspbian adopted plymouth. Thus I'm not sure it would make sense to move back.

Gotcha, so we keep plymouth.
I started troubleshooting, so far I can see all of the default themes showing splash screen after installing plymouth and plymouth-themes , then running sudo plymouth-set-default-theme -R themename , as you know to see the list we use plymouth-set-default-theme -l .

I will continue troubleshooting

[ealmonte32]

Ok so it is working for me:

pi@pi4blk:~ $ sudo plymouth-set-default-theme -R screenly
pi@pi4blk:~ $ sudo update-initramfs -u
pi@pi4blk:~ $ sudo reboot

..

I compared ansible splashscreen files like screenly.plymouth and screenly.script, and they are identical...

These are the packages I installed during testing:

pi@pi4blk:~ $ dpkg -l | grep -i "plymouth"
ii  libplymouth4:armhf             0.9.4-1.1+rpt2                      armhf        graphical boot animation and logger - shared libraries
ii  plymouth                       0.9.4-1.1+rpt2                      armhf        boot animation, logger and I/O multiplexer
ii  plymouth-label                 0.9.4-1.1+rpt2                      armhf        boot animation, logger and I/O multiplexer - label control
ii  plymouth-theme-breeze          5.14.5-1                            armhf        Breeze theme for Plymouth
ii  plymouth-theme-hamara          1.0                                 all          boot animation, logger and I/O multiplexer - Hamara theme
ii  plymouth-themes                0.9.4-1.1+rpt2                      armhf        boot animation, logger and I/O multiplexer - themes

..

This is the /boot/cmdline.txt

pi@pi4blk:~ $ sudo cat /boot/cmdline.txt 
console=serial0,115200 console=tty1 root=PARTUUID=53c6e06f-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait logo.nologo quiet plymouth.ignore-serial-consoles loglevel=0 splash

Screenshot with test image as logo:

[shaqaruden]

did you have to modify cmdline.txt?

[ealmonte32]

did you have to modify cmdline.txt?

yes, I believe the original cmdline.txt file didnt have these:

logo.nologo quiet plymouth.ignore-serial-consoles loglevel=0 splash

loglevel=0 is not necessary I just left it there during testing, it can be safely removed.

[vpetersson]

Good job @ealmonte32! So the missing step was just sudo update-initramfs -u?

[shaqaruden]

I attempted this myself but I was not able to get it working. Here's what I did

1. Flash latest Raspberry Pi OS Lite
2. sudo apt update && sudo apt upgrade
3. Installing Screenly from the development branch
4. Install all missing packages from @ealmonte32's list
5. Edit cmdline.txt to reflect what @ealmonte32's is (minus log)
6. sudo plymouth-set-default-theme -R screenly
7. sudo update-initramfs -u
8. sudo reboot

[vpetersson]

Interesting. And this was on a Pi 4 @shaqaruden?

[shaqaruden]

@vpetersson yes

[ealmonte32]

@shaqaruden
I am going to test again with documenting each step since by the end result there were so many back and forth changes that I did not keep track of every single one because i just wanted to see if it was actually capable of showing the splash screen.

Is your buster image this one:
http://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2020-08-24/

[shaqaruden]

@ealmonte32 yes I am using that image

[ealmonte32]

@shaqaruden

I got it to work again after much trial and error..

i forgot to tell you to install:
sudo apt install rpd-plym-splash
but dont do it yet, try this first:

pi@raspberrypi4:~ $ sudo plymouth-set-default-theme -r
pi@raspberrypi4:~ $ sudo plymouth-set-default-theme -R screenly
pi@raspberrypi4:~ $ sudo plymouth --show-splash
pi@raspberrypi4:~ $ sudo update-initramfs -u

pi@raspberrypi4:~ $ sudo nano /etc/plymouth/plymouthd.conf 

these are the contents of my conf file: notice the ShowDelay=1

# Administrator customizations go in this file
#[Daemon]
#Theme=futureprototype
#ShowDelay=0
[Daemon]
Theme=screenly
ShowDelay=1

Then reboot, let me know how it goes..
Also, did you add disable_splash=1 to your /boot/config.txt file?

[ealmonte32]

working splash screen:

[vpetersson]

No, those are just some dependencies. You need to run bash <(curl -sL https://www.screenly.io/install-ose.sh) and select the development release.

[Raziers]

@vpetersson

Now i got that worked out

But now it seems i dont have plymouth.conf in /etc/plymouth

I only got plymouthd.conf

is that the same file?

pi@raspberrypi:/etc/plymouth $ ls
plymouthd.conf

if i edit the plymouthd.conf instead, and follow the rest of the steps. ending with a reboot. I ust boot into a black screen with a writing prompt that dosnt do anything.

[ealmonte32]

Guys, plymouth themes seem to be case sensitive, so you will get an error if you do:
sudo plymouth-set-default-theme -R Screenly because Screenly should be lowercase like screenly
you can check the exact theme name you need to write by typing: sudo plymouth-set-default-theme -l

@Raziers , /etc/plymouth/plymouthd.conf is the correct file to have.
type cat /etc/plymouth/plymouthd.conf and show me what comes up.

[Raziers]

Did something get updated? I ran through @shaqaruden guide again, but only got to installing Screenly from the dev branch. After that, it seems to work fine now on the raspberry 4

[ealmonte32]

Well yes many many changes/commits are on the dev/master branch vs the production branch.

[kmichaliq]

I am testing screenly ose and I some problems. I have raspberry 4 model B 4GB, when I install on raspbian lite by bash command and I choose development release the installation is successful but when I want display the page i just see white screen. I saw other issues and i know that i have to choose experimental release but I got error on task [screenly : Run docker-compose] . Are there any plans to fix this problem?

[ealmonte32]

@MichaliQQ , do not use experimental for this purpose, development branch should be the one.
Can you explain more about the website you are adding? I have Pi4B here and can test this, it could simply be the website/uzbl related.

[kmichaliq]

@ealmonte32 Website just uses socket.io and jquery. I cant show you because site is created locally. Screenly only load from this website image of logo (the rest of the page is white), in screenly browser console returns error in index with 4 line let socket = io();

[Monomaniak-Tek]

I tried varius methods of installation with Pi 4 (with this topic and little more). Unfortunately, in the best way, uzbl seem not workink very well (no javascript, no css?).
Is it possible to change browser or install webkit1 ?
If anyone have a nice installation of scrennly OSE on Pi 4, is it possible to share image file of SD card?
Thanks !

[ealmonte32]

@ealmonte32 Website just uses socket.io and jquery. I cant show you because site is created locally. Screenly only load from this website image of logo (the rest of the page is white), in screenly browser console returns error in index with 4 line let socket = io();

Oh ok.. well, so based on this info then yes the reason for webpage not displayed properly is UZBL browser, which is being replaced on the next version of Screenly.

[ealmonte32]

Hi @Monomaniak-Tek

I tried varius methods of installation with Pi 4 (with this topic and little more). Unfortunately, in the best way, uzbl seem not workink very well (no javascript, no css?).
Is it possible to change browser or install webkit1 ?

As mentioned to other user above and in other posts, UZBL has been the culprit of all these issues with displaying of web assets incorrectly and it is being replaced in the next version of Screenly.
The new browser should have WebKit built-in as part of the Qt Web View browser app that will be used.

Since UZBL has not been updated in many years (in the official debian packages repo) , you would need to compile it manually and install it yourself (instructions are on their github repo). This might allow more web pages to work but in the end, the browser is not updated frequently so for example the last version they officially released as source is: v0.9.1 @keis keis released this on Oct 27, 2016 , so as you can see, 4 years old, which is still better than the current version on raspbian apt sources of 0.0.0~git.20120514-1.2+b18 , which is from 2012...
If i can compile this newer version and have it working without doing so many workarounds, I will post here what to do, but I dont want to promise anything.

If anyone have a nice installation of scrennly OSE on Pi 4, is it possible to share image file of SD card?

But installing it on Pi 4 does not change the browser outcome, so I am not sure what you are asking for an image file.. this is not good, you should never install non-official images of entire OS+applications on your device.. Do other webpage assets work on your Pi4 with latest version of Screenly OSE (dev/master branch)?

[vpetersson]

Update from last week:

• I've been doing heavy refactoring on the experimental branch to make it more manageable going forward. Some things I did in the update:
  • Consolidate Balena and non-Balena docker-compose.yml files (with overrides)
  • Move WebViewer into main repo
  • Introduced a base image to reduce space (much more can be done here)
  • Introduced multi-stage builds for viewer
  • Documented and verified how QT Base is built
  • Refactored almost all Dockerfiles
  • Scripted docker build (and prepared it for GitHub Actions)
  • ...and probably a lot more that I've forgotten about already :)

Other outstanding issues:

• Fix Raspberry Pi 4 Model B support
  • As things stand right now, the viewer component does not work on Pi 4 on the Experimental branch. This is possibly due to lack of Pi 4 support in QT 5.9.
• Fix IP on intro page
  • Because we're running inside a docker container, we cannot detect the IP of the host.
• Fix SSL support
  • With the refactoring of the Nginx code, I broke the SSL support. This should be relatively easy to fix.
• Validate that the WiFi Hotspot code works

[ealmonte32]

@vpetersson
Just to confirm, to work on some of the outstanding issues we have to do the troubleshooting under the experimental branch + pi3?

[vpetersson]

Yes, exactly. I'm working with @rusko124 to get the Experimental branch to support Pi 4. However, in the meantime, it would be helpful to kick the tires on a Pi 3 as we've pushed a lot of changes to the branch recently.

[Monomaniak-Tek]

I (with a friend..) can solved UZBL display problem on Pi4 using webkit2 :
If this can help anyone...
What to do:

1. Download uzbl-next:
   git clone --depth=1 https://github.com/uzbl/uzbl -b next
   cd uzbl

2. Install the dependancies:
   apt-get install libwebkit2gtk-4.0-dev libgnutls28-dev

3. Build uzbl-core:
   export CFLAGS=" pkg-config --cflags --libs webkit2gtk-4.0 glib-2.0 gtk+-3.0 libsoup-2.4 gnutls"
   make uzbl-core

4. Install the binary:
   mv /usr/bin/uzbl-core{,.orig}
   cp uzbl-core /usr/bin/

5. Fix the last line of /usr/bin/uzbl-browser, replacing "@" by
   127.0.0.1:8080/splash-page --config - --print-events, so the line
   becomes: exec uzbl-core 127.0.0.1:8080/splash-page --config -
   --print-events ${config_file:+--config "$config_file"} --connect-socket
   $DAEMON_SOCKET

6. Restart the daemon (or reboot):
   systemctl restart screenly-viewer.service

[vpetersson]

@Monomaniak-Tek Thanks, but we've already moved away from uzbl in the Experimental branch that we hope to get out in the coming weeks. Uzbl has more or less been abandoned upstream so we're moving to a more modern browser based on WebEngine.

[javad87]

Guys, plymouth themes seem to be case sensitive, so you will get an error if you do:
sudo plymouth-set-default-theme -R Screenly because Screenly should be lowercase like screenly
you can check the exact theme name you need to write by typing: sudo plymouth-set-default-theme -l

@Raziers , /etc/plymouth/plymouthd.conf is the correct file to have.
type cat /etc/plymouth/plymouthd.conf and show me what comes up.

For this Error: "no such file or directory problem" when executing :sudo plymouth-set-default-theme -R Screenly,
I guess the problem is not with case sensitivness, I did both ways but still had the Error, after checking folders in /etc/systemd/system I could not find the screenly related services and also in /usr/.... path also did not find screenly folder and related files, although screenly installation via bash script provided, finished successfully and it asked for reboot ....

I changed pi password to default password of pi which is "raspberry" and run the installation script again, this time services and screenly files installed correctly and not receiving the error....

So, if you changed pi default password, return it back to raspberry and run bash <(curl -sL https://www.screenly.io/install-ose.sh) again...

consider that during installation u will be asked to enter pi password which u have to enter default one and also later for security reason asking to change it...I did not change it u can change it later ...first check if it boots correctly...

U can change password by raspberry config menu: sudo raspi-config

Anyone knows how can I move from splash screen to main X window os environment (rasbian) or opening shell or new tty?
I want to turn my wifi on/off or doing some configuration....
by the way in screenly splash screen when I connected vi WiFi it says can not resolve IP...I found my IP via my access point admin pannel..

Thanks guys for ur help, hope all be well and healthy and wealthy

[Monomaniak-Tek]

@Monomaniak-Tek Thanks, but we've already moved away from uzbl in the Experimental branch that we hope to get out in the coming weeks. Uzbl has more or less been abandoned upstream so we're moving to a more modern browser based on WebEngine.

Ok, but on Pi 4, I only can install development branch (as explain by shaqaruden) however PI 4 crash with Experimental branch.

[Monomaniak-Tek]

Raspberry Pi 4 Model B 2G with Development Branch

• web with webkit2 for javascript & css (See my post above to resolve)

• Images: troubleshooting = black screen, then I had to modify the "viewer.py" file.

• Vidéo with audio (Nothing to do)

[javad87]

I did the same things that mentioned above, everything is ok except when it comes to showing video assets, screen will be black for a moment till moving to a next asset which is a pic and it shows pic....

I increased GPU to 256, file is around 2 minutes and 13MB , mp4 codec H264, omxplayer Version: 20190723+gitf543a0d-1,I use buster image, Rapi 4 model B

What should I do to solve black screen problem?

screenly log:

Dec 01 17:41:57 raspberrypi python[3119]: Displaying video /home/pi/screenly_assets/9f0e815ed52840199fb48dcebd2722e1 for 1
Dec 01 17:41:57 raspberrypi python[3119]: current url is file:///tmp/screenly_html/black_page.html
Dec 01 17:44:50 raspberrypi python[3119]: Last update: 2020-12-01 10:18:41.020324
Dec 01 17:44:50 raspberrypi python[3119]: get_next_asset
Dec 01 17:44:50 raspberrypi python[3119]: refresh_playlist
Dec 01 17:44:50 raspberrypi python[3119]: refresh: counter: (0) deadline (2020-11-29 22:07:00) timecur (2020-12-01 14:14:5
Dec 01 17:44:50 raspberrypi python[3119]: update_playlist
Dec 01 17:44:50 raspberrypi python[3119]: Generating asset-list...
Dec 01 17:44:50 raspberrypi python[3119]: generate_asset_list deadline: 2020-11-29 22:07:00
Dec 01 17:44:50 raspberrypi python[3119]: get_next_asset after refresh
Dec 01 17:44:50 raspberrypi python[3119]: get_next_asset counter 0 returning asset 1 of 4
Dec 01 17:44:50 raspberrypi python[3119]: Showing asset Pasargad.jpg (image)
Dec 01 17:44:50 raspberrypi python[3119]: Asset URI /home/pi/screenly_assets/55de0f08b0ff465e9441164d3dff66dc
Dec 01 17:44:50 raspberrypi python[3119]: Already showing file:///tmp/screenly_html/black_page.html, reloading it.
Dec 01 17:44:50 raspberrypi python[3119]: Sleeping for 10
Dec 01 17:45:00 raspberrypi python[3119]: Last update: 2020-12-01 10:18:41.020324
Dec 01 17:45:00 raspberrypi python[3119]: get_next_asset
Dec 01 17:45:00 raspberrypi python[3119]: refresh_playlist
Dec 01 17:45:00 raspberrypi python[3119]: refresh: counter: (0) deadline (2020-11-29 22:07:00) timecur (2020-12-01 14:15:0
Dec 01 17:45:00 raspberrypi python[3119]: update_playlist
Dec 01 17:45:00 raspberrypi python[3119]: Generating asset-list...
Dec 01 17:45:00 raspberrypi python[3119]: generate_asset_list deadline: 2020-11-29 22:07:00
Dec 01 17:45:00 raspberrypi python[3119]: get_next_asset after refresh
Dec 01 17:45:00 raspberrypi python[3119]: get_next_asset counter 0 returning asset 2 of 4
Dec 01 17:45:00 raspberrypi python[3119]: Showing asset Hafez.jpg (image)
Dec 01 17:45:00 raspberrypi python[3119]: Asset URI /home/pi/screenly_assets/4456bd4409aa4b6f8f114a11babe420b
Dec 01 17:45:00 raspberrypi python[3119]: Already showing file:///tmp/screenly_html/black_page.html, reloading it.
Dec 01 17:45:00 raspberrypi python[3119]: Sleeping for 10
Dec 01 17:45:10 raspberrypi python[3119]: Last update: 2020-12-01 10:18:41.020324
Dec 01 17:45:10 raspberrypi python[3119]: get_next_asset
Dec 01 17:45:10 raspberrypi python[3119]: refresh_playlist
Dec 01 17:45:10 raspberrypi python[3119]: refresh: counter: (0) deadline (2020-11-29 22:07:00) timecur (2020-12-01 14:15:1
Dec 01 17:45:10 raspberrypi python[3119]: update_playlist
Dec 01 17:45:10 raspberrypi python[3119]: Generating asset-list...
Dec 01 17:45:10 raspberrypi python[3119]: generate_asset_list deadline: 2020-11-29 22:07:00
Dec 01 17:45:10 raspberrypi python[3119]: get_next_asset after refresh
Dec 01 17:45:10 raspberrypi python[3119]: get_next_asset counter 0 returning asset 3 of 4
Dec 01 17:45:10 raspberrypi python[3119]: Showing asset h264-low.mp4 (video)
Dec 01 17:45:10 raspberrypi python[3119]: Asset URI /home/pi/screenly_assets/902596d7542f4de59a5d929307e97e5e
Dec 01 17:45:10 raspberrypi python[3119]: Displaying video /home/pi/screenly_assets/902596d7542f4de59a5d929307e97e5e for 1
Dec 01 17:45:10 raspberrypi python[3119]: current url is file:///tmp/screenly_html/black_page.html

[ealmonte32]

For this Error: "no such file or directory problem" when executing :sudo plymouth-set-default-theme -R Screenly,
I guess the problem is not with case sensitivness, I did both ways but still had the Error, after checking folders in /etc/systemd/system I could not find the screenly related services and also in /usr/.... path also did not find screenly folder and related files, although screenly installation via bash script provided, finished successfully and it asked for reboot ....

@javad87 , sorry but this is incorrect, it is case sensitive and the errors you are getting are because you did not install screenly correctly and the packages, there is no other reason besides that for the error you got and not having the screenly services in systemd is the 100% obvious reason that you did not install screenly properly.

---

I changed pi password to default password of pi which is "raspberry" and run the installation script again, this time services and screenly files installed correctly and not receiving the error....

So, if you changed pi default password, return it back to raspberry and run bash <(curl -sL https://www.screenly.io/install-ose.sh) again...

consider that during installation u will be asked to enter pi password which u have to enter default one and also later for security reason asking to change it...I did not change it u can change it later ...first check if it boots correctly...

Again, this is incorrect, you can install screenly with or without default password, this has nothing to do with screenly installation failing, unless you typed in the incorrect sudo password.. the script simply does a check to see if your current pi user password is still the default of "raspberry", and alerts you to change it, but this has nothing whatsoever to do with your installation failing at first or needing to install it using the default raspberry password..

---

Anyone knows how can I move from splash screen to main X window os environment (rasbian) or opening shell or new tty?
I want to turn my wifi on/off or doing some configuration....
by the way in screenly splash screen when I connected vi WiFi it says can not resolve IP...I found my IP via my access point admin pannel..

Thanks guys for ur help, hope all be well and healthy and wealthy

not sure what you are meaning in the first sentence, but if you want to access the console and you are physically connected to the raspberry pi, you can press Ctrl+Alt+F1... if you want to access it via SSH like most do, you need to enable SSH and just connect to it that way.. then you can run any of the commands you wish to turn on or off the wifi but of course if you are SSH onto it and turn off wifi, this will disconnect you unless you have ethernet and connected to that interface instead... if you are testing and need to access physical console then ctrl+alt+f1 is the way to do it.
not sure why the device was not finding your IP or resolve it, there are too many reasons for something like that happening but it is usually network related to your setup.. which branch are you installing/using?

[ealmonte32]

Ok, but on Pi 4, I only can install development branch (as explain by shaqaruden) however PI 4 crash with Experimental branch.

Well this is expected for experimental branch since it is being updated weekly sometimes so it isn't stable sort of, its specifically for testing only..
We need to separate the issues and narrow down the specifics..
What are the current issues you have with Pi4 and Development branch? we should be specific so we can both tests and I can see what you see..

[javad87]

For this Error: "no such file or directory problem" when executing :sudo plymouth-set-default-theme -R Screenly,
I guess the problem is not with case sensitivness, I did both ways but still had the Error, after checking folders in /etc/systemd/system I could not find the screenly related services and also in /usr/.... path also did not find screenly folder and related files, although screenly installation via bash script provided, finished successfully and it asked for reboot ....

@javad87 , sorry but this is incorrect, it is case sensitive and the errors you are getting are because you did not install screenly correctly and the packages, there is no other reason besides that for the error you got and not having the screenly services in systemd is the 100% obvious reason that you did not install screenly properly.

I changed pi password to default password of pi which is "raspberry" and run the installation script again, this time services and screenly files installed correctly and not receiving the error....
So, if you changed pi default password, return it back to raspberry and run bash <(curl -sL https://www.screenly.io/install-ose.sh) again...
consider that during installation u will be asked to enter pi password which u have to enter default one and also later for security reason asking to change it...I did not change it u can change it later ...first check if it boots correctly...

Again, this is incorrect, you can install screenly with or without default password, this has nothing to do with screenly installation failing, unless you typed in the incorrect sudo password.. the script simply does a check to see if your current pi user password is still the default of "raspberry", and alerts you to change it, but this has nothing whatsoever to do with your installation failing at first or needing to install it using the default raspberry password..

Anyone knows how can I move from splash screen to main X window os environment (rasbian) or opening shell or new tty?
I want to turn my wifi on/off or doing some configuration....
by the way in screenly splash screen when I connected vi WiFi it says can not resolve IP...I found my IP via my access point admin pannel..
Thanks guys for ur help, hope all be well and healthy and wealthy

not sure what you are meaning in the first sentence, but if you want to access the console and you are physically connected to the raspberry pi, you can press Ctrl+Alt+F1... if you want to access it via SSH like most do, you need to enable SSH and just connect to it that way.. then you can run any of the commands you wish to turn on or off the wifi but of course if you are SSH onto it and turn off wifi, this will disconnect you unless you have ethernet and connected to that interface instead... if you are testing and need to access physical console then ctrl+alt+f1 is the way to do it.
not sure why the device was not finding your IP or resolve it, there are too many reasons for something like that happening but it is usually network related to your setup.. which branch are you installing/using?

Thanks @ealmonte32 for ur reply and help,as I said I'm guessing it might be due to the password change that screenly did not installed properly, I'm not sure... it did not give me any error during failed installation and I found out that related services and files don't exist, after changing to default pass and reinstallation, problem get solved...maybe it is due to my netowrk that installation was not complete and successful....

yes with Ctrl+Alt+F1, I can open a shell and new tty but how can I get to Desktop environment (GUI) like before installation of screenly ? my OS is rasbian buster...
I found this link to do that:
https://askubuntu.com/questions/1130535/launch-gui-apps-from-text-mode-tty-without-loading-window-desktop-manager
do you have simpler way to switch to GUI environment?

I get another issue too, I have black screen when getting to MP4 assets...I post log in the above post.

How can I add assets via usb? I generated the key and put the .yaml file beside my assets in a flash and Run this script with python: /usr/local/bin/screenly_usb_assets.sh, nothing happend!
https://github.com/Screenly/screenly-ose/blob/master/docs/developer-documentation.md

I'm new to screenly, and using free OSE version. not on cloud ...

Again appreciate ur help,

[vpetersson]

This ticket is becoming too complex (and going out on tangents). I've created a new milestone instead to track the progress of this.

[vpetersson]

@Monomaniak-Tek Please take a look here if you want to help out. Right now, we mostly need help with getting QT working with hardware acceleration. This is something that UZBL never supported, so it's a big benefit.

[ealmonte32]

yes with Ctrl+Alt+F1, I can open a shell and new tty but how can I get to Desktop environment (GUI) like before installation of screenly ? my OS is rasbian buster...
I found this link to do that:
https://askubuntu.com/questions/1130535/launch-gui-apps-from-text-mode-tty-without-loading-window-desktop-manager
do you have simpler way to switch to GUI environment?

Well, there is a warning when installing Screenly that says you will not be able to use the desktop once screenly installs..
Anyway, sure you can just install the desktop manager, just pick the one you want to use and follow the instructions:
https://raspberrytips.com/upgrade-raspbian-lite-to-desktop/

You cannot simply go back and forth between screenly and desktop version because the display managers will be conflicting and packages and complex to go back and forth, as I mentioned what is it you need to do that you need the desktop.. you can do everything from the command line..

.

I get another issue too, I have black screen when getting to MP4 assets...I post log in the above post.

How can I add assets via usb? I generated the key and put the .yaml file beside my assets in a flash and Run this script with python: /usr/local/bin/screenly_usb_assets.sh, nothing happend!
https://github.com/Screenly/screenly-ose/blob/master/docs/developer-documentation.md

With regards to the black mp4 video assets, I have to test that with the Pi4 and get back to you, bit I suggest you open up a new Issue about this because as viktor pointed out, this post has gotten too big and out of hand with regards to the original intent... so create/open a new issue for this question you asked above.