Thanks for the help.
FWIW, if you didn't notice, in the original bug report
I note that I'm using X over the network -- with
client and server on different boxes.
Video playback stopped working (meaning: I get
maybe a frame a second-ish (with avplay/vlc ?)) somewhere around
Stretch. It worked for years before that.
(But I never tried to play video in a browser,
except perhaps by accident, and can't speak
to what chromium did.)
On Sun, 23 Jan 2022 15:57:38 -0500
Andres Salomon <dilin...@queued.net> wrote:
> 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.
I will dig into it. (I'm never sure what/how video acceleration
is supposed to work with the client and server on different boxes.)
It may take a while for me to look around. As you may guess,
I don't care much about video.
> 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.
Regards,
Karl <k...@karlpinc.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
