starred/xiosk

Fork 0

mirror of https://github.com/debloper/xiosk.git synced 2026-04-26 21:35:51 +03:00

[GH-ISSUE #124] Mint install on Pi4 doesn't load the website #75

New issue

Open

opened 2026-03-03 11:14:11 +03:00 by kerem · 10 comments

kerem commented

2026-03-03 11:14:11 +03:00

Owner

Originally created by @Demitjev on GitHub (Oct 8, 2025).
Original GitHub issue: https://github.com/debloper/xiosk/issues/124

Hi all,
Looks like a nice project. When I use the install script for version 4, the installation seems to be working fine. I can load the control panel on a remote pc, but on the device itself i just se Raspberrian dektop, wallpaper and all. No errors or anything. I've followed recommendations etc. and have remote access etc.
What error could cause this?

Originally created by @Demitjev on GitHub (Oct 8, 2025). Original GitHub issue: https://github.com/debloper/xiosk/issues/124 Hi all, Looks like a nice project. When I use the install script for version 4, the installation seems to be working fine. I can load the control panel on a remote pc, but on the device itself i just se Raspberrian dektop, wallpaper and all. No errors or anything. I've followed recommendations etc. and have remote access etc. What error could cause this?

kerem commented

2026-03-03 11:14:12 +03:00

Author

Owner

@Sakakidash commented on GitHub (Oct 9, 2025):

runner.sh

has "chromium-browser" and if changed to "chromium" instead you will get the kiosk mode running on startup.

@Sakakidash commented on GitHub (Oct 9, 2025): runner.sh has "chromium-browser" and if changed to "chromium" instead you will get the kiosk mode running on startup.

kerem commented

2026-03-03 11:14:12 +03:00

Author

Owner

@Demitjev commented on GitHub (Oct 9, 2025):

runner.sh

has "chromium-browser" and if changed to "chromium" instead you will get the kiosk mode running on startup.

Hi Sakakidash, I'm unsure if this can be altered after installation - it feels like a bug, as "chromium-browser" has not been around for a long time. I can see that there is fallback to "chromium" but it's doesn't seem to work :/ Any suggestions? :)

@Demitjev commented on GitHub (Oct 9, 2025): > runner.sh > > has "chromium-browser" and if changed to "chromium" instead you will get the kiosk mode running on startup. Hi Sakakidash, I'm unsure if this can be altered after installation - it feels like a bug, as "chromium-browser" has not been around for a long time. I can see that there is fallback to "chromium" but it's doesn't seem to work :/ Any suggestions? :)

kerem commented

2026-03-03 11:14:12 +03:00

Author

Owner

@Sakakidash commented on GitHub (Oct 9, 2025):

runner.sh
has "chromium-browser" and if changed to "chromium" instead you will get the kiosk mode running on startup.

Hi Sakakidash, I'm unsure if this can be altered after installation - it feels like a bug, as "chromium-browser" has not been around for a long time. I can see that there is fallback to "chromium" but it's doesn't seem to work :/ Any suggestions? :)

Original

"chromium-browser
$URLS
--disable-component-update
--disable-composited-antialiasing
--disable-gpu-driver-bug-workarounds
--disable-infobars
--disable-low-res-tiling
--disable-pinch
--disable-session-crashed-bubble
--disable-smooth-scrolling
--enable-accelerated-video-decode
--enable-gpu-rasterization
--enable-oop-rasterization
--force-device-scale-factor=1
--ignore-gpu-blocklist
--kiosk
--no-first-run
--noerrdialogs"

Change to

"chromium
$URLS
--disable-component-update
--disable-composited-antialiasing
--disable-gpu-driver-bug-workarounds
--disable-infobars
--disable-low-res-tiling
--disable-pinch
--disable-session-crashed-bubble
--disable-smooth-scrolling
--enable-accelerated-video-decode
--enable-gpu-rasterization
--enable-oop-rasterization
--force-device-scale-factor=1
--ignore-gpu-blocklist
--kiosk
--no-first-run
--noerrdialogs"

@Sakakidash commented on GitHub (Oct 9, 2025): > > runner.sh > > has "chromium-browser" and if changed to "chromium" instead you will get the kiosk mode running on startup. > > Hi Sakakidash, I'm unsure if this can be altered after installation - it feels like a bug, as "chromium-browser" has not been around for a long time. I can see that there is fallback to "chromium" but it's doesn't seem to work :/ Any suggestions? :) Original "chromium-browser \ $URLS \ --disable-component-update \ --disable-composited-antialiasing \ --disable-gpu-driver-bug-workarounds \ --disable-infobars \ --disable-low-res-tiling \ --disable-pinch \ --disable-session-crashed-bubble \ --disable-smooth-scrolling \ --enable-accelerated-video-decode \ --enable-gpu-rasterization \ --enable-oop-rasterization \ --force-device-scale-factor=1 \ --ignore-gpu-blocklist \ --kiosk \ --no-first-run \ --noerrdialogs" Change to "chromium \ $URLS \ --disable-component-update \ --disable-composited-antialiasing \ --disable-gpu-driver-bug-workarounds \ --disable-infobars \ --disable-low-res-tiling \ --disable-pinch \ --disable-session-crashed-bubble \ --disable-smooth-scrolling \ --enable-accelerated-video-decode \ --enable-gpu-rasterization \ --enable-oop-rasterization \ --force-device-scale-factor=1 \ --ignore-gpu-blocklist \ --kiosk \ --no-first-run \ --noerrdialogs"

kerem commented

2026-03-03 11:14:12 +03:00

Author

Owner

@Demitjev commented on GitHub (Oct 9, 2025):

Right, so I changed the runner.sh as recommended, but the browser still doesn't load on boot :/

@Demitjev commented on GitHub (Oct 9, 2025): Right, so I changed the runner.sh as recommended, but the browser still doesn't load on boot :/

kerem commented

2026-03-03 11:14:12 +03:00

Author

Owner

@Sakakidash commented on GitHub (Oct 9, 2025):

Right, so I changed the runner.sh as recommended, but the browser still doesn't load on boot :/

Have you tried running chromium from the desktop?

if it does not excist you can install it.

try opening the terminal

and do

command -v chromium-browser

command -v chromium

If it does not work

sudo apt update
sudo apt install chromium-browser

@Sakakidash commented on GitHub (Oct 9, 2025): > Right, so I changed the runner.sh as recommended, but the browser still doesn't load on boot :/ Have you tried running chromium from the desktop? if it does not excist you can install it. try opening the terminal and do command -v chromium-browser command -v chromium If it does not work sudo apt update sudo apt install chromium-browser

kerem commented

2026-03-03 11:14:12 +03:00

Author

Owner

@Demitjev commented on GitHub (Oct 9, 2025):

Yes, Chromium is installed, I believe it's also installed automatic by the script if its missing. chromium-browser is depricated. It's "chromium" now :)

@Demitjev commented on GitHub (Oct 9, 2025): Yes, Chromium is installed, I believe it's also installed automatic by the script if its missing. chromium-browser is depricated. It's "chromium" now :)

kerem commented

2026-03-03 11:14:12 +03:00

Author

Owner

@debloper commented on GitHub (Oct 15, 2025):

@Demitjev does the Pi4 have 1GB or less RAM by any chance? If it does, then that's your suspect... chromium doesn't like too low memory (and we've removed forcing the low-memory mode, as it results into a bad experience anyway). But if it does have 2GB or more memory, then try running systemctl status piosk-runner.service and see if you can find the issue in there (or just post its output here verbatim as a code-block).

@Sakakidash /usr/bin/chromium-browser is internally symlinked to /usr/bin/chromium so either of them should work just fine (and changing between those names in the script won't give different results). As the base binary is chromium-browser still (even though the package name has changed) we keep the invocation by that name.

@parthsidpara however, I think in future we should look for the available browser (or give users choice to select the browser on dashboard) instead of hardcoding the binary name.

@debloper commented on GitHub (Oct 15, 2025): @Demitjev does the Pi4 have 1GB or less RAM by any chance? If it does, then that's your suspect... chromium doesn't like too low memory (and we've removed forcing the low-memory mode, as it results into a bad experience anyway). But if it does have 2GB or more memory, then try running `systemctl status piosk-runner.service` and see if you can find the issue in there (or just post its output here verbatim as a code-block). @Sakakidash `/usr/bin/chromium-browser` is internally symlinked to `/usr/bin/chromium` so either of them should work just fine (and changing between those names in the script won't give different results). As the base binary is `chromium-browser` still (even though the package name has changed) we keep the invocation by that name. @parthsidpara however, I think in future we should look for the available browser (or give users choice to select the browser on dashboard) instead of hardcoding the binary name.

kerem commented

2026-03-03 11:14:13 +03:00

Author

Owner

@Sakakidash commented on GitHub (Oct 15, 2025):

@debloper I installerad 3x rpi4b 8gbs throughout last week with Piosk, had to manually change it for the kiosk to launch.

@Sakakidash commented on GitHub (Oct 15, 2025): @debloper I installerad 3x rpi4b 8gbs throughout last week with Piosk, had to manually change it for the kiosk to launch.

kerem commented

2026-03-03 11:14:13 +03:00

Author

Owner

@debloper commented on GitHub (Oct 15, 2025):

@debloper I installerad 3x rpi4b 8gbs throughout last week with Piosk, had to manually change it for the kiosk to launch.

Interesting! Will check out if the new Trixie based build is using different convention (and dropped the old name for chromium). This wasn't the case until very recently.

@debloper commented on GitHub (Oct 15, 2025): > @debloper I installerad 3x rpi4b 8gbs throughout last week with Piosk, had to manually change it for the kiosk to launch. Interesting! Will check out if the new Trixie based build is using different convention (and dropped the old name for chromium). This wasn't the case until very recently.

kerem commented

2026-03-03 11:14:13 +03:00

Author

Owner

@Ellegon commented on GitHub (Oct 21, 2025):

@debloper I installerad 3x rpi4b 8gbs throughout last week with Piosk, had to manually change it for the kiosk to launch.

How did you do that? I have the same issue (chromium not runing on a pi4 b), but chromium is installed. Can I change the runner.sh after the installation? Where is that located?

edit: Nevermind, I found it. (For future readers: it's in /opt/piosk/scripts

@Ellegon commented on GitHub (Oct 21, 2025): > [@debloper](https://github.com/debloper) I installerad 3x rpi4b 8gbs throughout last week with Piosk, had to manually change it for the kiosk to launch. How did you do that? I have the same issue (chromium not runing on a pi4 b), but chromium is installed. Can I change the runner.sh after the installation? Where is that located? edit: Nevermind, I found it. (For future readers: it's in /opt/piosk/scripts