Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chromium crashes after boot. #1

Open
Timmoz opened this issue Mar 27, 2019 · 2 comments · May be fixed by #4
Open

Chromium crashes after boot. #1

Timmoz opened this issue Mar 27, 2019 · 2 comments · May be fixed by #4

Comments

@Timmoz
Copy link

Timmoz commented Mar 27, 2019

Hello,

I get an error after booting Chromium:

Aw, Snap!
Something went wrong while displaying this webpage.

I test it on a RPI 3B, 3B+ and 3A+. All with this same error.
with URL_LAUNCHER_URL=chrome://version/

Here the last log entries from Balena:

27.03.19 09:19:59 (+0100) chromium-kiosk Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
27.03.19 09:20:02 (+0100) chromium-kiosk [154:363:0327/082002.160108:ERROR:bus.cc(396)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
27.03.19 09:20:02 (+0100) chromium-kiosk [154:173:0327/082002.273769:ERROR:service_manager_context.cc(291)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service
27.03.19 09:21:02 (+0100) chromium-kiosk [154:154:0327/082102.349530:ERROR:web_resource_service.cc(196)] Connection error with the json parser process.

Anyone any idea what this is all about and how to solve it?
Thanks!

@jacobrosenthal
Copy link

yeah I started getting this too. remove the --disable-gpu --disable-software-rasterizer --disable-dev-shm-usage
https://github.com/jayatvars/balena-chromium-kiosk/blob/master/app/start.sh#L23

@Timmoz
Copy link
Author

Timmoz commented Apr 5, 2019

Thanks, that solves it! :)

@jacobrosenthal jacobrosenthal linked a pull request Jul 26, 2019 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants