Chromium not working on armhf after version 116.0.5845.180-1~deb12u1

[gulien]

Since we've updated the base image to Debian 12, the armhf variant is no more building successfully.

https://github.com/gotenberg/gotenberg/actions/runs/6682899395/job/18158596958#step:6:9467

300.5 Setting up chromium-common (118.0.5993.70-1~deb12u1) ...
300.5 Setting up dconf-gsettings-backend:armhf (0.40.0-4) ...
300.5 Setting up libgtk-3-common (3.24.38-2~deb12u1) ...
300.6 Processing triggers for libglib2.0-0:armhf (2.74.6-2) ...
301.0 Setting up libgtk-3-0:armhf (3.24.38-2~deb12u1) ...
301.4 Processing triggers for libc-bin (2.36-9+deb12u3) ...
301.6 Setting up chromium (118.0.5993.70-1~deb12u1) ...
301.9 update-alternatives: using /usr/bin/chromium to provide /usr/bin/x-www-browser (x-www-browser) in auto mode
302.0 update-alternatives: using /usr/bin/chromium to provide /usr/bin/gnome-www-browser (gnome-www-browser) in auto mode
302.9 Error: Can't open display: 

[gulien]

What's weird here is that Chromium seems to be waiting for a display.

There are solutions like https://github.com/browserless/browserless/blob/main/start.sh, but, as other platforms do not require such steps, I wonder if it's an upstream bug. No luck so far in finding a corresponding issue.

[gulien]

Repository with a simple version of our Docker image to reproduce the error: https://github.com/gulien/chromium

[gulien]

Reported a "bug" here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055765

[gulien]

Using 116.0.5845.180-1~deb12u1 for armhf for now.

[gulien]

See also: https://lists.debian.org/debian-devel/2023/09/msg00175.html