Pi Zero 2 W - Not launching browser on boot #29
Comments
|
What happens if you reboot after the installation? Also (if rebooting didn't work) after the reboot, can you please run these following scripts and post the output? $ # run as the same user that set up PiOSK
$ less $HOME/.config/wayfire.ini
$ ps aux | grep piosk
$ ps aux | grep chrom
$ journalctl -fbAll of this assumes that you are using PiOS with wayland+wayfire (latest bookworm build with graphical user interface) & ran the script as the same user that the desktop is auto logging-in to. |
|
I am also experiencing issues getting the kiosk to display. The desktop loads up correctly and I can access the webpage at the pi's ip address. I am using a Raspberry Pi Zero 2W, RaspOS 32bit Full, with this screen. Output from the above commands:
|
|
Thanks @MBennin this is super helpful!
This tells us that neither of the the processes (the chrome browser, or the wtype tab switcher) are running (except for the process that you're querying it with, i.e. As the next step, what happens if you open up a terminal (in desktop mode, not over SSH), and run the following: # the args don't have to be broken into new lines, it's just for better readability
# here's the actual script: https://github.com/debloper/piosk/blob/main/scripts/browser.sh
chromium-browser \
https://google.com/ \
--kiosk \
--fast \
--fast-start \
--no-first-run \
--noerrdialogs \
--disable-infobars \
--ozone-platform=wayland \
--enable-features=OverlayScrollbar \
--enable-accelerated-video-decode \
--enable-gpu-rasterization \
--enable-oop-rasterization \
--ignore-gpu-blocklist \
--disable-smooth-scrolling \
--disable-low-res-tiling \
--enable-low-end-device-mode \
--disable-composited-antialiasing \
--start-maximizedI don't see why this won't run as it's clearly set up in the wayfire config (unless Wayfire on startup is expected to work differently on Pi Zero 2 W). And I don't see any eyebrow-raisers on the journal either. This might need a deeper dive (and not just for PiOSK). Anyone stumbling across this issue, please post your anecdotes/experiences/findings, so it helps to piece together the puzzle. |
|
I got the following output from the above command:
I made sure to enable wayland from raspi-config, so I'm not sure why it can't connect to the display. |
|
After looking into it for a bit, found out that Wayland is disabled on older SoCs. Seems like an imposed restriction (not a technical limitation). Can you please try this workaround:
Thanks for the help to get to the bottom of this. I'd update the docs to reflect it. |
debloper
added
wontfix
|
I have the same issue on my Raspberry Pi zero 2W, adding |
|
I was having the exact same issues as above (w RPi3). I ran ~/piosk/scripts/browser.sh and got the below: After a bit of investigation I found that Wayland doesn't work on the RPi3 without 'wayland=on' in /boot/firmware/cmdline.txt So I added that, rebooted, and Bam! Success. Note: I should highlight that it's REALLY sluggish. Will likely swap the Pi3 out for a Pi4B tomorrow. No such thing as overkill :-) |
|
I have same issue with Rpi zero 2W... "wayland=on" in cmdline.txt helps, partly. Now, i need to confirm this window before browser starts. |
|
It's in the browser scripts I think. I found this. I'm looking: https://issues.chromium.org/issues/373891800 |
|
Apparently --no-memcheck should fix it according to the /usr/bin/chromium-browser script |
|
Didn't work. I added that to the browser.sh script and it still prompted me |
|
Doesn't look like it's using the startup flags because the 'restore' shows too, so I think the usr bin will have to be modified or something. |
|
Sound promising for me just baught two raspi zero 2w 😄 |
|
Just delete |
|
Remote browser (Chrome on OSX 10.13.6) not opening PIOSK web page on remote PIOSK target. Made all checks noted in this thread and get what I think are correct responses - see below. I have checked to see what ports are open on the remote PIOSK and only see port 22 and not port 80. I can ssh into PIOSK IP but browsing to the same local IP gives me a "This site can't be reached - unexpectedly closed by remote host". Both PIOSK and MAC are on same wifi network. I have a hdmi monitor, keyboard and mouse connected to the target PIOSK which is a Pi3A+ running fresh and clean 32 bit Bookworm with Wayland/wayfire. Desktop loads but nothing else. Running /scripts/browser.sh directly on the target spawns an error message But opening the browser first and then repeating the script command brings up the browser with several tabs that do eventually load. Remote browsing is however still not working. Connection is refused, due to no web server running and port 80 not open. piosk@piosk:~ /piosk/$ ./scripts/browser.sh Results obtained using ssh to target piosk@piosk:~ $ ps aux | grep chrom piosk@piosk:~ $ ps aux | grep piosk piosk@piosk:~ $ journalctl -fb Please advise what I should check further or how I should initialise the PIOSK web server? |
|
@arqtv I think you have 2 issues:
|
|
If Pi Zero W 2 is not an option due to incompatibility, I recommend removing from your description stating that RPi Zero W 2, Pi 4 and 5 are all compatible. |
|
The piosk needs to use systemd to manage its three scripts that are running. Here is an example of a systemd service that should be used instead of the way piosk currently sets itself up to be autorun: install in /etc/systemd/system/ and then run sudo systemctl daemon-reload, sudo systemctl enable piosk-browser and sudo systemctl start piosk-browser (repeat for other two) piosk-browser.service[Unit] [Service] [Install] Note that it has a small sleep delay before the service fires, and it depends on graphical.target so it will launch (with a delay) after the GUI comes up, and it hijacks the pi user's environmental variables for the X display adapter. Note that this will only work if the user is named "pi". If you configured the raspberry pi user with a different username then you'd have to adjust this. The savvy developer could include these three files as a template in the install script and then use sed to add in the actual user name so that it would always work. You'd need a seperate version of this for the switcher.sh and also one to run the index.js if you wanted it to switch tabs and have the webserver running, here are the ones I used: piosk-switcher.service[Unit] [Service] [Install] piosk-webserver.service[Unit] [Service] [Install] Ideally you should have three of these, including one to run your index.js. Putting things in rc.local is ugly, there is no functionality to restart it if it fails and a bunch of other things. This will solve the "after X hours the piosk stops switching tabs" issue which is undoubtedly the switcher.sh script failing for some random reason or another, but systemd will automatically restart it as long as "browser.sh" is running. Edit: I removed the After/Requires section in piosk-switcher.service as this seems to get hung up on boot often and just replaced it with a 30 second delay and hoping for the best, which seems to work well! |
I have followed all of the setup steps multiple times, and tried with multiple different installations of RaspOS (32bit, 64bit, Legacy, etc) and none seem to want to launch the browser once the system is running. The install script runs without any issues, and I am able to access the dashboard, update the piosk URLs and apply the changes to the Pi.
The text was updated successfully, but these errors were encountered: