[GH-ISSUE #64] Occassional issue - chromium does not launch into fullscreen #57

New issue

Closed

opened 2026-03-03 11:13:46 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @freedomischaos on GitHub (Feb 5, 2025).
Original GitHub issue: https://github.com/debloper/xiosk/issues/64

Does anyone have anything similar happening?
Does anyone have any suggestions on fixing it? I am looking into some wayland options to check the window and then attempt to make it fullscreen.

It does seem "random" in that I'm not yet able to find anything that leads back to why it sometimes works, if I reboot the rPi there is a decent chance that it works on the reboot. It seemed like it might have been related to the wireless or just general bootup time so I added a brief sleep 15 to the browser.sh startup script and that seems like it handled it in most cases/reduced the frequency but still happens on occassion.

Originally created by @freedomischaos on GitHub (Feb 5, 2025). Original GitHub issue: https://github.com/debloper/xiosk/issues/64 - Does anyone have anything similar happening? - Does anyone have any suggestions on fixing it? I am looking into some wayland options to check the window and then attempt to make it fullscreen. It does seem "random" in that I'm not yet able to find anything that leads back to why it sometimes works, if I reboot the rPi there is a decent chance that it works on the reboot. It seemed like it might have been related to the wireless or just general bootup time so I added a brief `sleep 15` to the `browser.sh` startup script and that seems like it handled it in most cases/reduced the frequency but still happens on occassion.

kerem

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

closed this issue
added the
question

bug
labels

kerem commented

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

Author

Owner

@debloper commented on GitHub (Feb 21, 2025):

Tried to reproduce it, but couldn't. What's the spec of the RPi that you're using?

If you can enable and upload crash-log for Chromium, and/or output of dmesg of that startup (journalctl -b 0) to see what's breaking.

@debloper commented on GitHub (Feb 21, 2025): Tried to reproduce it, but couldn't. What's the spec of the RPi that you're using? If you can enable and upload crash-log for Chromium, and/or output of dmesg of that startup (`journalctl -b 0`) to see what's breaking.

kerem commented

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

Author

Owner

@freedomischaos commented on GitHub (Feb 21, 2025):

RPi5, 8GB RAM, not over clocked. Using an nvme2 hat.

I'll try to get the log soon. I'm using it at a friend's shop for signage so might be a bit to get it to happen and get the log. It does tend to "fix" on a follow up reboot.

@freedomischaos commented on GitHub (Feb 21, 2025): RPi5, 8GB RAM, not over clocked. Using an nvme2 hat. I'll try to get the log soon. I'm using it at a friend's shop for signage so might be a bit to get it to happen and get the log. It does tend to "fix" on a follow up reboot.

kerem commented

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

Author

Owner

@freedomischaos commented on GitHub (Apr 13, 2025):

Sorry for late follow up, just finally got an ounce of time to get into the shop to do some debugging and investigating. I didn't see anything interesting throughout the log, but I think it might have been an chrome extension as I guess I had installed some or it synced one during my initial setup of the system. I think Chrome was throwing an error message about it not longer being supported (UBLOCK ORIGIN) and breaking it out of full screen mode to render the error.

For now, I've just passed the disable extensions on startup with runner.sh which keeps it as clean and lean as possible and in so far couldn't reproduce the occasional full-screen break out; though it never seemed to regularly or on-demand occur, just sometimes and that error message was only visible and weirdly a reboot seemed to clear it for some amount of time.

@freedomischaos commented on GitHub (Apr 13, 2025): Sorry for late follow up, just finally got an ounce of time to get into the shop to do some debugging and investigating. I didn't see anything interesting throughout the log, but I think it might have been an chrome extension as I guess I had installed some or it synced one during my initial setup of the system. I think Chrome was throwing an error message about it not longer being supported (UBLOCK ORIGIN) and breaking it out of full screen mode to render the error. For now, I've just passed the disable extensions on startup with runner.sh which keeps it as clean and lean as possible and in so far couldn't reproduce the occasional full-screen break out; though it never seemed to regularly or on-demand occur, just sometimes and that error message was only visible and weirdly a reboot seemed to clear it for some amount of time.