Hey @Slos
0. Who is "we"?

Also, if you want an older version they are available for download here.

1. When you get a blank screen - Is this after the boot sequence (boot lines or bootspalsh?) Because if its completely blank it would not matter what website you configure. Its not even reaching that stage.

2. FullPageOS tests if it can connect to website before switching on the browser. So it does not load a broken page. A blank screen might mean its not managing to preform that test. You can try to disable that by creating a file at /boot/check_for_httpd and see if that helps.

Also - I am working on this software 100% in my free time. I have no clients who pay me for it. If you want to help develop it to become even more stable I welcome contributions and pull requests. I hope you figure out how to fix the issue. When you do I kindly reminder that there is a donation button in the readme file.

Hey, trying to link this with #509
When it does not start - do you have a cursor?

Hey @guysoft,

Thanks for getting back to me. I very much appreciate you taking your time to respond to issues and for keeping this repository going in your free time.

To answer your first question as to "Who is we?". I'm more than happy to help get to the bottom of the issue at hand. I just need to set up an environment where I can see what exactly is going on by looking at some log files while replicating the issue. On the other hand, whoever made the breaking change should be involved in getting things back on track but I'm afraid we're way past that point unfortunately.

1. When do I get the blank screen? This is after the boot sequence... probably when it is trying to load the browser and display the page.

2. I will try your suggestion of disabling 'check_for_httpd' in the config. I was not aware of the behavior you're describing where it first tries to connect to the site and only then launches the browser. Is there a good rationale for this workflow? I'd say launch the browser ALWAYS and let the browser connect to the site. This way if there is an error with the connection, at least there will be some visual feedback on the screen (certificate invalid, no internet connection... etc). At the moment, with the black screen, the user has no clue what it going on. Am I missing something (or many things)?

Cheers,

Slos

Hey, trying to link this with #509 When it does not start - do you have a cursor?

I did see a cursor if I remember correctly (to be honest, I did not look for these kind of details). I will do a few more tests and let you know.

I'm running into this too sometimes. Are there any logs that we can check?

Another clue from this morning. Blank screen, no cursor. I logged in via ssh and tried to run this, but apparently X wasn't running:

pi@mm-pi:~/scripts $ ./start_chromium_browser
dpkg-query: no packages found matching bluealsa
[1335:1335:0208/074359.754701:ERROR:ozone_platform_x11.cc(239)] Missing X server or $DISPLAY
[1335:1335:0208/074359.758356:ERROR:env.cc(257)] The platform failed to initialize.  Exiting.

I did sudo init 3, sudo init 5 to switch runlevels but to no avail. sudo reboot solved it 😛

Hi

/boot/check_for_httpd solution did not work.
There is a cursor.

I am using the latest version from the mirror. (2023-12-11-fullpageos-bookworm-armhf-lite-0.14.0)

Also splash screen .png could not be loaded.

Is there anybody who can tell me what version is actually working? Tired an old one from 2018 on a PI4 but it is just not works at all....

This is a very nice project, but now it is unfortunately useless indeed. :(

Hey, so there was an issue with the nighties which was fixed on the 2014-02-23. YOu can try it now.
Related #498

Closing if no reply

Hi, i'm also experimenting this behavior. Unfortunately i can't see all the boot process because i'm not physically with the device. But for example, executing the refresh bash, fixed it. I'm serving a react app using pm2 and serve command. The OS loads locally the webpage through localhost:3000. So any idea?

@AlfaOmega777 None that I can think of :-/

@AlfaOmega777 None that I can think of :-/

Don't worry, this project is a great idea, but as a developer I can tell you just relax and try to make it ultimately simpler. For example, yesterday I took a standard bullseye 11 distro from raspberry pi imager. Almost only modifying the autostart file of the raspberry pi you can achieve the same functionality that fullpageos already has. I can tell you that all of us sometimes in our brain overthink a lot everything, when sometimes the key is make it as simple as possible.

@AlfaOmega777 FullpageOS has a lot of small things that were added to it over the years. It really depends what you wanna do with it. The fact that FullPageOS is the same image that has been run and tested by tens of thousands tends to be its strong point. But if you want to do something different, using your own could be your way.

Hi!
I have the same problem!
https://orf.at - works
https://kultur-hafnerbach.at - black screen after boot section. I can connect via ssh but even sudo reboot does not work, I have to power off the device.

@stgreimel What version of FullPageOS?