Bug#1055765: chromium: Error: Can't open display (armhf) while other platforms (amd64, arm64, i386) are OK

Sun, 12 Nov 2023 00:15:15 -0800

Probably the easiest way is to manually download the chromium and chromium-common deb packages, and then 'sudo apt install /path/to/chromium_117.x.y.z-1~deb12u1_armhf.deb /path/to/chromium-common_117.x.y.z-1~deb12u1_armhf.deb'.
If you go to https://snapshot.debian.org/package/chromium/117.0.5938.149-1~deb12u1/ in your browser, scroll down to the "chromium 117.0.5938.149-1~deb12u1" section, and then click on the link for "chromium_117.0.5938.149-1~deb12u1_armhf.deb" (or right click and click 'save link as', or copy the link and supply it to wget/curl in the qemu environment), it should download it. Do the same thing in the "chromium-common 117.0.5938.149-1~deb12u1" section. 


https://snapshot.debian.org/package/chromium/118.0.5993.70-1~deb12u1/ 
has more armhf deb packages, if the 117 packages aren't broken in your 
test. Unfortunately it looks like 118.0.5993.117-1 never successfully 
built for armhf on debian 12..





On Sun, Nov 12 2023 at 08:20:36 AM +01:00:00, Julien Neuhart 
<neuhart.jul...@gmail.com> wrote:

Could you guide me on how ton install those versions? As far as I 
know, they are not available in bookworm directly. Thanks!



 Le 11 nov. 2023 à 21:51, Andres Salomon <dilin...@queued.net> a 
écrit :



 Okay, so not distribution-specific. Between 116 and 119 there were 
a considerable number of changes in the debian packaging, including 
switching from clang-14 to clang-16 for build (done in 
118.0.5993.117-1~deb12u1) and enabling NEON for armhf (done in 
117.0.5938.132-1~deb12u1). My immediate suspicion is the NEON 
change, so it would helpful if you could try those versions as well 
and report back. Also, if it turns out to be the NEON change, having 
the output of `uname -a` and `cat /proc/cpuinfo` (inside of qemu's 
armhf emulation) would be helpful.



 On Sat, Nov 11 2023 at 12:08:42 PM +01:00:00, Julien Neuhart 
<neuhart.jul...@gmail.com> wrote:

 Hello Andres,
 Thanks for the quick follow up.

 So I’ve tested with Chromium 116.0.5845.180-1~deb12u1 and it 
works as expected on Debian 12.
 Note that I also had to explicitly install the chromium-common 
package:
 DEBIAN_FRONTEND=noninteractive apt-get install -y -qq 
--no-install-recommends chromium-common="116.0.5845.180-1~deb12u1" 
chromium="116.0.5845.180-1~deb12u1"

 Distributor ID:        Debian
 Description:   Debian GNU/Linux 12 (bookworm)
 Release:       12
 Codename:      bookworm

 Kernel: Linux buildkitsandbox 6.2.0-1015-azure #15~22.04.1-Ubuntu 
SMP Fri Oct  6 13:20:44 UTC 2023 armv7l GNU/Linux

 Architecture: armhf
 chromium —version:

 ind: '/root/.config/chromium/Crash Reports/pending/': No such file 
or directory
 Chromium 116.0.5845.180 built on Debian 12.1, running on Debian 
12.2

 Le 10 nov. 2023 à 22:01, Andres Salomon <dilin...@queued.net> a 
écrit :

 Hi,

 Can you please try other versions if possible?  
119.0.6045.123-1~deb12u1 is currently in bookworm-security. 
116.0.5845.180-1~deb12u1 is still in bookworm. It would be helpful 
to know if this is a bookworm-specific regression, since it worked 
on bullseye's 116, or something broken in general with chromium 
119.
 It looks like a version of 117 and 118 also successfully built 
for armhf, as other option to try:
 
https://snapshot.debian.org/package/chromium/118.0.5993.70-1~deb12u1/
 
https://snapshot.debian.org/package/chromium/117.0.5938.149-1~deb12u1/
 On Fri, Nov 10 2023 at 09:49:00 PM +01:00:00, Julien Neuhart 
<neuhart.jul...@gmail.com> wrote:

 Package: chromium
 Version: 119.0.6045.105-1~deb12u1
 Dear maintainers,

 While building with QEMU a Docker image based on Debian bookworm 
using the chromium package, I found out that the « armhf » 
variant seems broken, which is not the case for others platforms.

 Indeed, after having installed chromium with:

 DEBIAN_FRONTEND=noninteractive apt-get install -y -qq 
--no-install-recommends chromium
 Running « chromium —version » failed on armhf (Error: Can't 
open display) while working as expected in others platform 
(amd64, arm64, i386).
 Please note it is working fine in Debian 11 & package version 
116.0.5845.180.
 Full installation logs may be found here: 
https://github.com/gulien/chromium/actions/runs/6829257786

 armhf:
 Distributor ID: Debian
 Description: Debian GNU/Linux 12 (bookworm)
 Release:       12
 Codename: bookworm

 Kernel: Linux buildkitsandbox 6.2.0-1015-azure 
#15~22.04.1-Ubuntu SMP Fri Oct  6 13:20:44 UTC 2023 armv7l 
GNU/Linux

 Architecture: armhf
 chromium —version:
 Error: Can't open display:
 i386:
 Distributor ID: Debian
 Description: Debian GNU/Linux 12 (bookworm)
 Release:       12
 Codename: bookworm

 Kernel: Linux buildkitsandbox 6.2.0-1015-azure 
#15~22.04.1-Ubuntu SMP Fri Oct  6 13:20:44 UTC 2023 x86_64 
GNU/Linux

 Architecture: i386
 chromium —version:

 find: '/root/.config/chromium/Crash Reports/pending/': No such 
file or directory
 Chromium 119.0.6045.123 built on Debian 12.2, running on Debian 
12.2

 arm64:
 Distributor ID: Debian
 Description: Debian GNU/Linux 12 (bookworm)
 Release:       12
 Codename: bookworm

 Kernel: Linux buildkitsandbox 6.2.0-1015-azure 
#15~22.04.1-Ubuntu SMP Fri Oct  6 13:20:44 UTC 2023 aarch64 
GNU/Linux

 Architecture: arm64
 chromium --version:

 find: '/root/.config/chromium/Crash Reports/pending/': No such 
file or directory
 Chromium 119.0.6045.105 built on Debian 12.2, running on Debian 
12.2

 amd64:
 Distributor ID: Debian
 Description: Debian GNU/Linux 12 (bookworm)
 Release:       12
 Codename: bookworm

 Kernel: Linux buildkitsandbox 6.2.0-1015-azure 
#15~22.04.1-Ubuntu SMP Fri Oct  6 13:20:44 UTC 2023 x86_64 
GNU/Linux

 Architecture: amd64
 chromium --version:

 find: '/root/.config/chromium/Crash Reports/pending/': No such 
file or directory
 Chromium 119.0.6045.123 built on Debian 12.2, running on Debian 
12.2

 Thanks,
 Julien





























					Reply via email to