I’ve been able to reproduce the issue (e.g., Can’t open display) with versions 
117.0.5938.149-1~deb12u1 and 118.0.5993.70-1~deb12u1.

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

cat /proc/cpuinfo:
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 106
model name      : Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz
stepping        : 6
microcode       : 0xffffffff
cpu MHz         : 2793.437
cache size      : 49152 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 21
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm 
constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid 
sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 
3dnowprefetch invpcid_single pti fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid 
rtm avx512f avx512dq rdseed adx smap clflushopt avx512cd avx512bw avx512vl 
xsaveopt xsavec xsaves md_clear
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs taa itlb_multihit mmio_stale_data gds
bogomips        : 5586.87
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 106
model name      : Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz
stepping        : 6
microcode       : 0xffffffff
cpu MHz         : 2793.437
cache size      : 49152 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 21
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm 
constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid 
sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 
3dnowprefetch invpcid_single pti fsgs
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs taa itlb_multihit mmio_stale_data gds
bogomips        : 5586.87 
clflush size    : 64
cache_alignment : 64 
address sizes   : 46 bits physical, 48 bits virtual 
power management:

> Le 12 nov. 2023 à 09:10, Andres Salomon <dilin...@queued.net> a écrit :
> 
> 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