Hey peeps, we just launched a new guide looking at how to set up the Pi 5 in kiosk mode. A great little tool for accessing things like your Home Assistant or Adafruit IO dashboard, personal calendars, or any cool webpages you might be hosting locally: “How to set up a Raspberry Pi Kiosk - Launch a Fullscreen Webpage on Boot!”
In this guide, we will be transforming your Raspberry Pi into a bespoke device to interface humans with the web. This guide will walk you through setting up a Pi as a dedicated kiosk device, meaning it will seamlessly and automatically launch a full…
Read more
4 Likes
I followed raspberry-pi-kiosk-mode-setup and I am having an issue with my raspberry pi 4 stopping the kiosk.
I would leave the kiosk running and after few hours , I would come a find only the desktop showing. How can I troubleshoot this please?
Hi Tismso,
Welcome to the forum! My guess is the Pi is the Pi is crashing, or experiencing a power issue. Can you send a picture of your setup so we can see what else you have?
I just figured out that the auto start script under wayfire.ini is opening new windows instead of tabs. no wonder chromium was crashing. How do I get it to open tabs instead?
Hey Tismo,
Thats probably what is happening there. Can you share the contents of run_kiosk.sh with us, as that will likely need to be edited to stop the issue you are experiencing?
Cheers,
Blayden
1 Like
Thanks a lot for a great guide! Would it be possible to launch two different sites if there’s two screens connected?
2 Likes
Hey @Johan281155, welcome to the forums!
This should be possible by specifying a display to setup in kiosk mode inside of the run_kiosk.sh file. You can do this by adding the DISPLAY=:n variable to specify a display to output onto.
Modifying the setup instructions in the guide would have run_kiosk.sh looking something like this.
sleep 4
DISPLAY=:0 /bin/chromium-browser --kiosk --ozone-platform=wayland --start-maximized --noerrdialogs --disable-infobars --enable-features=OverlayScrollbar https://time.is/ &
DISPLAY=:1 /bin/chromium-browser --kiosk --ozone-platform=wayland --start-maximized --noerrdialogs --disable-infobars --enable-features=OverlayScrollbar https://imbenwolf.github.io/sanger.dk/ &
Hope this helps!
4 Likes
Thank you kindly for the reply!
Sadly I couldn’t get it to work, they both start on the first display.
Though also having the error that both don’t always start, sometimes only one of them will. If I then close that with ALT+F4 then the second one would start. Seems random if it’ll start both or just one.
Hey @Johan281155,
Have you tried placing a sleep in between the two display functions? It seems unnecessary given that the display function specifies which display to use, but it could be worth a shot. I’m thinking something short like sleep(1) could help with synchronisation issues, if that is the cause.
Hello, yes tried it but no luck. Seems Wayland is having trouble with multimonitor setups. Been reading about other people having trouble with it as well.
For example I couldn’t simple move windows between the monitors with key commands.
Switched back to X11 and got it working there with --windows-position=xxxxx
Will stick with this for now and revisit Wayland in the future 
Thank you all for the help!
1 Like
The Wayland transition has been a little rough and support is getting there but slowly. Great you found a fix!
1 Like
Hello, thanks for this video on youtube!!
I’m looking for a way to auto-close firefox when it’s idle for say 20 seconds (so nobody has clicked anything for 20 seconds) Is that possible in linux?
Thank you!
1 Like
Hi @Pijan283122, Welcome to the Forums!!!
It looks like it may be possible to use a utility such as xprintidle to make a script to check how long a user has been idle and terminate an application once it reaches the time limit.
1 Like
Hello, thanks a lot for your response! I will try to do some research how to use this…may I come back to you if I can’t find a way?
Thank you!
Ok so, I tried to use this script for a start:
The only thing I changed was the class-name to “chromium”.
However when I execute the script it throws out an endless number of the following error:
“xprop: error: Invalid window id format: 0x0.”
I’m a total noob when it comes to coding…can you help me here?
My system is RPI 3 B+ running dietpi.
Thank’s a lot!
Hi @Pijan283122,
The class name for Chromium might change depending on how it’s packaged or installed
You might need to check the actual string by running xprop manually on a Chromium window. The class should either be chromium or Chromium-browser.
Thank’s for your response! I tried both class names but unfortunately it keeps outputting that error…I checked class-name and it’s “chromium”.
Can you share the script your running? It may be easier to have that as a point of reference here.
Hi,
I am following your instructions to display a web page in kiosk mode after boot on a rpi 4.
I have done a fresh install and an update of the 64bit desktop version.
The problem I am having is it just boots into the desktop and does open chromium in kiosk mode.
If I run the run_kiosk.sh manually, it works as expected.
An odd thing is that doing the sudo nano .config/wayfire.ini opens a blank file.
I did manage to find the wayfire.ini in a hidden .config folder in my user folder and added the commands to that, but it still doesn’t work.
What am I doing wrong?
Hi @Andy283734, Welcome to the forums!!!
Some users have experienced similar problems
I recommend making sure you are on the latest release of Pi OS Bookworm.
I’d also suggest trying the alternative commands to see if they work any better when accessing the wayfire.ini file.
1 Like
