New install, chromium not launching

[Enginerdy]

Hi,
Rpi 4 with a 64 bit desktop OS, install was successful 5.0.0, and I can access the local ip web interface. I've programmed in my URL, applied, and can hit the start button. The service stops/starts periodically but nothing is happening in the pi desktop os. When the pi is turned off the website updates from start/stop to offline.
From the pi desktop it seems to not be launching the kiosk in chromium, and I'm unable to launch chromium manually either. Firefox starts no problem.
I read previous discussions and switched to wayland, and issues #52 & #53 are listed as resolved. Not sure where to go from here.

[Enginerdy]

Further, running systemctl status *
xiosk-switcher.service active (running with the default number of tabs, not the updated list)
xiosk-dashboard.service active
xiosk-runner.service activating "failed with result exit-code"

I can get the last one to active, but it then goes through a scheduled restart - which explains the stop/start interface issue in my post

**
running journalctl -u xiosk-runnner.service -e
control process exited code=killed status=15/TERM shows up once
Main process exited code=exited status=21/n/a shows up frequently

[Enginerdy]

I was able to get it working. The pi wouldn't reboot, only shutdown. Ethernet lights off, red power led on, no SD card reading LED - so that web-sleuthing led me to try a different micro SD card and it's working like a champ now.

Faulty SD card, or bad sectors is the presumed cause.

Thanks for making this debloper. I've really despised the existing processes and such. This is fantastic. I'm using it to host a screen in my brewery with tapitgood.com showing what beers are on tap.

[debloper]

Thanks for adding the context about what caused the problem. Even though specific cases may differ in root cause, I'm marking this as answer, because this is an excellent example of how sometimes the problems are on a completely different plane of existence than we may initially assume them to be... and no amount of beating the head around the bushes would have given a clear resolution path on my end, to actually solve it on your end.

Still, thanks a lot for doing the initial research, clear communication and specific details that may be useful for debugging (as well finding the solution, that was specific for your case); that's the model way to report issues & contribute solutions.

I went down a rabbit hole thinking what may cause services to not exit and hang the system (cause I was under the impression the reboot is being held back); but I'm glad I didn't post my initial hunch, as that could have derailed your from finding the actual solution.

BTW, that's a nice usecase you got there... Cheers! 🥂