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

Update to Chromium 130 #841

Open
MaxIhlenfeldt opened this issue Oct 17, 2024 · 1 comment
Open

Update to Chromium 130 #841

MaxIhlenfeldt opened this issue Oct 17, 2024 · 1 comment
Assignees

Comments

@MaxIhlenfeldt
Copy link
Collaborator

Release notes:

@MaxIhlenfeldt MaxIhlenfeldt self-assigned this Oct 17, 2024
@AndreasUfert
Copy link

Oh, I am definitely curious about 130, since 129 somehow broke something in our Yocto image. While with 128 everything renders fine, 129 doesn't bother to render any font elements, not only on our kiosk application but also if I redirect the kiosk to youtube.com or something like that. It just shows a more or less gray or white canvas.

I can't really file an actual bug report because there's not much to report on - it worked with 128, it doesn't with 129, while neither the remote debug console nor the Chromium debug log show any hint to what could have been broken.

So my only hope is 130 to see if the problem somehow magically disappears.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants