-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only whitescreen in Chromium / no wifi #587
Comments
Does it work, if you delete the second URL entry in /boot/firmware/fullpagedashboard.txt? |
Thats seems to be one of my problems here, I did not find any information how to reload the /boot/firmware/fullpagesdashboard.txt. I changed entries there and tried to reload it with the scripts located in the scripts folder but seems not to work like this. Even restarting the whole raspberry does not reload the fullpagesdashboard.txt Do I need to delete something that it can be re-read? I found the URLs in the json file as well, seems it does not change? Feel a bit like reengineering as I have no clue right now where to search :) btw: I get the welcome screen if I put in fullpageos.txt the issue seems really something with fullpagesdashboard.txt or after... Thanks a lot for more tips and tricks. |
FullPageOS uses FullPageDashboard as the default App (located in the Webserver directory of FullPageOS) to display single or multiple websites. FullPageDashboard initially reads the web addresses from fullpagedashboard.txt. It then saves user defined sites in a file called urls.json in the web root dir. If this file exists, it will no longer read any entries from fullpagedashboard.txt in favor of urls.json. You can force reading from fullpagedashboard.txt again by deleting the urls.json file and reload the App. Unfortunately there is a bug in the interaction between FullPageOS and FullPageDashboard. Another possible problem could be, that not every website can be correctly displayed with FullPageDashboard as it uses iFrames to load each site content which is not supported by every website. The easiest way if you just want to display a single page is placing that address into FullPageOS /boot/firmware/fullpageos.txt. If you need multiple auto rotating websites based on FullPageDashboard functionality (and if they work using iFrames) you can try manually adding the addresses via the web GUI available on the standard FullPageDashboard welcome page (use the + at the upper address tab to manually add websites). This will disable fullpagedashboard.txt and create a urls.json file and instruct FullPageDashboard to read from there. Hope this helps… |
Thanks a lot! I really like the deletion urls.json and reload, that works great to update the urls.json and to play arround. Unfortunately I need that feature with mulitple websites. So I tried the workaround with the GUI (now I know what is meant by GUI for Fullpagesos). Unfortunately it does not work as well. I noticed that it writes a urls.json (btw with a total different syntax than the one created with the initial fullpagesdashboard.txt) but it does not display any website, really tried multiple from google to my router logon page, wheater pages... The only page here which seems to work is the https://localhost/welcome Seems there is another problem here as well.. do you have any external website which should work 100% with this setup? |
urls.json |
Thank you very much, I am now some steps further. It really seems that a lot of websites do not support iFrames. I already use FullPageOS 0.14.0. Is it possible if I use this gui mode to go to fullscreen? So that the single tabs are not longer visible? Are there any ideas how to use websites with login credentials with fullpagesos or personal calenders like ical or directly the google calender? Thanks :) |
There are ways to disable the FullPageDashboard top navigation bar.
One possibility is using a regular mouse and keyboard to interact with the website in the standard way. |
I just loaded the nightly build for the first time, I have an Ethernet connection. No modification of anything except the Pi Imager unique login information. I also have the "White Screen of Death" after boot and after package updating. What am I supposed to be seeing on a fresh install? I also tried the nightly build with no modification to the boot information and still got a WSOD. Pi 4 2GB |
You are supposed to see the logo of FullPageOS untill the browser loads. |
Okay. This is weird. Today I powered up the test Pi to do what you asked, and it worked! I then tried the other builds that I flashed that was failing yesterday and they too all worked. I'm not sure what the heck happened yesterday... Maybe it is a timing issue with DHCP receiving a good IP addresses versus the check that is mentioned? If there is no internet, then you get a white page? What log should I be looking at if it happens again? Also, it is worth noting that in all instances, I was able to SSH into the various test builds. |
Just flashed 0.14 nightly, only update was manually editing Interestingly I had the opposite problem with the image installed by RPi Imager (never did figure out which version) - wifi worked like a charm, but I could never get the window manager to launch, never saw a splash screen or dashboard page. Irony is, I'm trying to set up a product launch countdown display for the team - and now I've wasted 3h trying to get this to work. 🤦 Running on a Pi3B+ that has been used plenty in the past hosting OctoPi driving a 3d printer, so I know networking works and there are no known hardware issues. |
AFAIK the stable version installed by RPi Imager is 0.13.0 which I believe is based on Debian 11 (Bullseye). If I understand the maintainer correctly, he has no plans to add updates to the old 0.13.0. Hope this helps a bit… |
Update - just saw @apartmedia wrote most of this, thanks!
@arpieb wpa-supplicant support has been dropped by raspberypi os: raspberrypi/bookworm-feedback#72 I am in the process of adding a workaround with an option to set up a connection via NetworkManager, its what is blocking me from releasing FullPageOS 0.14.0, progress is shown here: Pr for that is here: |
Wifi with WPA and wired network is working fine for me! But a have the issue with : /boot/firmware/fullpagedashborad.txt contains multiple websites like: This does not work for me, tried deleting urls.json and it did not do the trick! |
See here for more details and possible reasons. It explains the functionality and also one of the bugs and limitations when it comes to multiple site rotation in the current versions. |
Duplicate of #534 |
What were you doing?
Installed FullPageOs latest nightly build via Raspberry PI installer on a Raspberry Pi 2.
Added Wifi Information and 3 different URLs in fullpagedashboard.txt
What did you expect to happen?
Wifi was not working, but I could solve it via raspi-config quite easily. -> ok
Website is not displayed. Please confirm the following stettings are correct:
/boot/firmware/fullpageos.txt contains this entrance only:
http://localhost/FullPageDashboard
/boot/firmware/fullpagedashborad.txt contains multiple websites like:
http://localhost/welcome
http://www.google.com
With this settings I should see the welcomepage and the google websites alternating?
What happened instead?
Nothing, whitescreen in Chromium after FullpageOs Logo.
Was there an error message displayed? What did it say?
Just a blank Chromium page
Version of FullPageOS?
0.14.0
Screenshot(s) showing the problem:
[If applicable. Always include if unsure or reporting UI issues.]
If you are building FullPageOS - provide a build.log that is created for the build
N/A
Did I do something completly wrong? Tried with different image files.. once I had the welcome page displayed.
It there somewhere an explanation how to setup the pages after the first boot? I read somewhere on github that the .txt file with the URLs is only loaded at "first boot"?
I read something about a GUI for configuration. I guess it is /scripts/start_gui? If I try to start it, chromium is just blinking the white screen but not showing anything.
Thanks for any help/ideas.
The text was updated successfully, but these errors were encountered: