Grafana-image-renderer stopped working after Chromium upgrade

Grafana Installation
1

Grafana-image-renderer stopped working after Chromium upgrade to 150.0.7871.46-1~deb13u1
Using a binary install of image-renderer.
grafana-image-renderer version 6d2d090beb3d7d9170639005c52d9b0a95e86bef (committed 2026-06-29T12:24:50Z) (go1.26.4)

O/S: Debian Trixie 13.

Error from syslog.
2026-07-05T20:19:45.912478-04:00 debian-vm03 grafana-image-renderer-linux-arm64[5313]: time=2026-07-05T20:19:45.911-04:00 level=ERROR source=/home/runner/work/grafana-image-renderer/grafana-image-renderer/pkg/api/render.go:248 msg=“failed to render” error=“failed to run browser: chrome failed to start:\n[5329:5356:0706/001945.630480:ERROR:dbus/bus.cc:405] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")\n[5329:5356:0706/001945.630911:ERROR:dbus/bus.cc:405] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")\n[5329:5356:0706/001945.816337:ERROR:dbus/bus.cc:405] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")\n[0706/001945.883466:ERROR:third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)\n[0706/001945.883600:ERROR:third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)\n” trace_id=cb7b81decf7c6c47f797416967a82ef1

Had to rollback Chromium to Chromium 146.0.7680.71 built on Debian GNU/Linux 13 (trixie)

Any information available on when image-renderer should work with the latest Chromium?

3

Thanks for the detailed report.

Since rolling back from Chromium 150 to 146 restores rendering, it does suggest a regression or compatibility change between those versions. However, based on the log you’ve shared, it’s difficult to determine the root cause because it doesn’t include the complete browser startup failure.

Could you enable debug logging (if possible, Chromium’s verbose output) and share the complete renderer/browser output? The additional logs should help identify the browser startup failure and narrow down the underlying cause.

The official Grafana image rendering troubleshooting guide also recommends increasing logging when diagnosing renderer startup issues:

4

Upgraded Chromium to Chromium 147.0.7727.137 built on Debian GNU/Linux 13 (trixie)
from Chromium 146.0.7680.71 built on Debian GNU/Linux 13 (trixie).

Grafana-image-renderer is still working fine.
When I get a chance I will upgrade to 150.0.7871.46-1~deb13u1 and provide debug logs from
image-renderer.