nightly builds are broken, stable version is broken, no working distribution

[artbild]

Plain install from Raspberry Pi Imager. (Both nightly builds, 2024-03-07, 2024-03-31 and the stable version 2022 are broken tested on Raspberry Pi 4 and Raspberry Pi Zero 2W

Stable version (2022)

Stable version, after install is missing /home/pi/scripts/start_gui (directories and file) If I add it manually the hdmi output is broken and config.txt commands are ignored. Fullpageos.txt is ignored also but I can add the url in the start_gui script after I register the service. However the hdmi output is broken and ignores config.txt commands. I did not continue to override more things.

Nightly build 2024-03-31

Both current nightly builds are broken. The last nightly build 2024-03-31 does successfully accept config.txt commands but ignores fullpageos.txt url. Instead it loads a blank screen (users reported this on other forums and on youtube as well) Turning the display works, toggeling overscan works, specifying screen resolution also working fine. No connection is made to the link provided in fullpageos.txt

Nightly build 2024-03-07

This nightly build does ignore config.txt commands and also loads a blank screen. netstat proofes that there is no connection made to the link provided in fullpageos.txt

[frutabruta]

The last working version for me is 2024_03_24, also installed from RPi Imager. Accepts webpage set in fullpageos.txt. I didn't need to edit config.txt, so that might not work. The only needed change was rotation of the screen - done via screen orientation parameter in start_gui script.

[artbild]

Wich Pi did you run it on?

[frutabruta]

Pi4, 2G RAM

[artbild]

It does not work for me out of the box. I will try to stick with 03-31 and try to override fullpageos.txt since it does get ignored here. I did fiddle around with HDMI modes but that does not resolve the problem. However at least the config.txt commands do work fine here.

It's either a chromium problem or the fullpageos.txt is simply not loaded here.

[frutabruta]

In one of the versions I remember that the system booted, but after I changed the orientation to "left" and rebooted, it got stuck on black screen. I think it was the newest: 2024-03-31 and that's why I used a bit older one.

[artbild]

Okay, i read about the black screen problem and how it is fixed but that is not a problen here. The splash screen and the fullpageos picture are loaded fine, have the correct orientation and resolution. That really works fine here. For me it's just the url that does not load.

[frutabruta]

And the SSH is working fine? Maybe it cannot connect to the internet. I guess you know that you can skip to the terminal via Ctrl+Alt+F1 to do the ’ip a’ or ’ping 8.8.8.8’ as a connection test.

[artbild]

Yes the Pi can successfully sudo apt update and I do all configuration with SSH. It is the distreibution that ignores fullapgeos.txt

[guysoft]

1. Hey @artbild i tested the latest nightly and it worked for me- how are you flashing the image? Are you changing anything in the rpi-imager. please provide reproduction stepss, otherwise I cant determine why it doesnt work for you, but does for me.

2. What forums? If you dont give a refence have no idea what you are talking about

[Slos]

nightly build works for me

[guysoft]

@Slos glad to hear - did something not work for you before?

[guysoft]

Can this be closed? @artbild any input as original poster?

[Slos]

@Slos glad to hear - did something not work for you before?

Hi,

Yes, some time ago I wanted to set up a kiosk using a raspberry Pi so I turned to FullPageOS. I tried configuring FullPageOS using the txt files contained in the image (fullpageos.txt, full-age-wpa-suplicant.txt, etc...). This did not work unfortunatelly (I opened an issue about that some time ago).

Now, last week I decided to give it another go but I used a different approach. I use the default fullpageOS dashboard instead of the txt system files to add my tabs/websites that I want to see on screen and everything works as expected.

I also managed to customize the start_chromium_browser file to add a default zoom level to chrome when it starts up, this also worked fine.

One thing I did not manage to get working is the fullpageos-wpa-supplicant file so that after reboot the raspberry pi would connect to another wifi network than the one which was set up using the raspberry pi imager.

[apartmedia]

One thing I did not manage to get working is the fullpageos-wpa-supplicant file so that after reboot the raspberry pi would connect to another wifi network than the one which was set up using the raspberry pi imager.

As @guysoft already mentioned in this issue here RPi OS bookworm dropped wpa_supplicant.conf support for configuring WiFi and moved to Network Manager. Therefore, the method used in FullPageOS to configure WiFi will currently not work, as it is no longer supported by Bookworm (and might never be in the future). @guysoft is thinking about or already working on a replacement mechanism for the old wpa_supplicant.conf method.

[Slos]

One thing I did not manage to get working is the fullpageos-wpa-supplicant file so that after reboot the raspberry pi would connect to another wifi network than the one which was set up using the raspberry pi imager.

As @guysoft already mentioned in this issue here RPi OS bookworm dropped wpa_supplicant.conf support for configuring WiFi and moved to Network Manager. Therefore, the method used in FullPageOS to configure WiFi will currently not work, as it is no longer supported by Bookworm (and might never be in the future). @guysoft is thinking about or already working on a replacement mechanism for the old wpa_supplicant.conf method.

I see. Thanks for the info.

[guysoft]

I am working on having a wpa-supplicant OR network manager file you can edit based on what the distribution has, but its moving slow. Its the last thing before I make a new RC

[apartmedia]

Its the last thing before I make a new RC

Will your new RC also address the bug regarding using multiple urls in fullpagedashboard.txt? As far as I can see the FullPageDashboard code will not read multiple lines initially defined in fullpagedashboard.txt. Therefore it’s currently not possible to configure multiple tabs and/or tab rotating by filling fullpagedashboard.txt with more than one line/one url (apart from the fact that using iframes will limit the ability of loading any website; e.g. I could not open Home Assistant‘s dashboard inside an iframe).