Control: found -1 117.0.5938.149-1~deb12u1
Thanks. More questions below:
On Mon, Nov 13 2023 at 08:28:41 PM +01:00:00, Julien Neuhart
<[email protected]> wrote:
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 armv7l3 GNU/Linux
Okay, this looks fine. You're running qemu on an Ubuntu x86 host, so
inside the VM it sees the Ubuntu kernel but as an armv7l architecture.
Chromium's startup script should run `uname -m`, see 'armv7l', and do
its 32-bit ARM checks.
cat /proc/cpuinfo:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 106
model name : Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz
Wait, what? Qemu doesn't bother to change /proc/cpuinfo for the VM, so
it's going to think it's running an x86 CPU?
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
Ugh, nor does it change cpu flags. The chromium script
(/usr/bin/chromium) should've errored out with a message about NEON
once it saw that the flags it needed in /proc/cpuinfo weren't present.
So there's two problems here.
Can you please run `bash -x /usr/bin/chromium --version` and provide
the output from that? Something's going wrong there. What *should* be
happening is that you should be seeing the message:
"The hardware on this system lacks support for NEON SIMD extensions.
We now require NEON or equivalent architecture extensions on ARM-based
machines. See
https://lists.debian.org/debian-devel/2023/09/msg00175.html
for more information."
Instead, it seems to be going ahead and launching chromium, which is
likely then getting confused for other reasons. Feel free to use the
latest available version of chromium for that test, you don't need to
stick with 117 or whatever.
Now, there's also the separate question of what qemu's armhf emulation
actually supports. It looks like, according to
https://www.qemu.org/docs/master/system/qemu-cpu-models.html , you're
running qemu in "Host passthrough" mode. That shouldn't work with
chromium unless you modify /usr/bin/chromium to not check for
NEON/ASIMD, and even then will probably have issues. I only see x86 and
mips documented on that page, but I would suggest running qemu with
something like "-cpu cortex-a15".
