On 1/23/22 14:52, Salvatore Bonaccorso wrote:
Source: chromium
Source-Version: 97.0.4692.99-1~deb11u1
On Sun, Jan 23, 2022 at 01:30:04PM -0600, Karl O. Pinc wrote:
Hello,
Upgrading to the latest chromium seems to have fixed the
problem of the window being displayed as a white box
without any controls.
Upgrade: chromium-sandbox:amd64 (97.0.4692.71-0.1~deb11u1,
97.0.4692.99-1~deb11u2), chromium:amd64 (97.0.4692.71-0.1~deb11u1,
97.0.4692.99-1~deb11u2), chromium-common:amd64 (97.0.4692.71-0.1~deb11u1,
97.0.4692.99-1~deb11u2)
Note that I am still getting plenty of error messages
on stdout/stderr when invoking chromium --temp-profile
from the command line. See below.
You may want to close this bug. I would be happy to file
a separate bug report(s) for any of the error messages
below, however you would advise.
Doing so now, but leaving it to the maintainers if they want separate
bugs on it for the remaining issues, okay? Andres?
Thanks!
Karl, the remaining error messages are either benign (like the "stack
smashing detected" ones, which are due to the older version of clang in
bullseye and don't show up in newer versions of clang), or seem to be
related to lack of hardware support from libgl1-mesa-dri. The next steps
to dealing with the mesa issues are trying out a backport of
libgl1-mesa-dri to see if it works better for you, and also going
through mesa's bug list to see if your specific radeonsi issues have
already been reported and/or solved. Your specific gpu hardware would be
listed in the output of chrome://gpu, if that's helpful for reporting a
mesa bug or following up on an existing one.
For the record, I don't know why the new release fixed your issue with
the --temp-profile window. Seems like an upstream chromium bug that got
fixed, as the debian side of things (for X11 at least) remained the
same. ¯\_(ツ)_/¯
At some point I hope to start including swiftshader with chromium, which
would provide an admittedly slow but functional software fallback for
folks whose GL hardware implementations are lacking or broken.
