Hello,
Replying to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926032#95
My answer is probably confusing. I am still hit with the bug reported as being
closed. Because hardware video decode is now ON by default and cannot be
disabled with the previous workaround anymore.
chrome://gpu/
Hello,
Removing the option to enable/disable hardware accel is the right move to get
rid of the problem at the moment. However this last patch (Source-Version:
75.0.3770.90-1) does the exact opposite of its intent : the option to
enable/disable accel is removed AND hardware accel is now always
Hello,
Unfortunately the new release 74.0.3729.108-1 does not fix anything regarding
this issue. As soon as I disabled the workaround we discussed earlier in order
to use hardware decoding again, solarized videos came back on many web sites.
Regards
V.B.
Hello,
This workaround works well, thank you, Ed.
However it is a short term solution. Why would we have to disable a feature
like hardware acceleration and revert to a sluggish (and cpu hungry) software
rendering in order to (barely) make things work like they did before in
previous releases
Package: console-setup
Version: 1.184
Severity: normal
Hello,
Unfortunately, bug 895047 is still unsolved with console-setup 1.184. Using
UTF-8 French locales here. The new "narrow no-break space" seems to be also
replaced anywhere else with the same "diamond" character on the console
My bad...
> This new "narrow no-break space" is also replaced with the same "tofu"
> character on
> the console. For example, in aptitude, reading the checksecurity package
> description.
Sorry, these ones appear to be standard no-break spaces in French translation.
So this is probably
Hello,
Unfortunately, this bug is still present and unsolved with console-setup 1.184.
Using UTF-8 French locales here. This new "narrow no-break space" is also
replaced with the same "tofu" character on the console. For example, in
aptitude, reading the checksecurity package description.
Hello,
I found that this bug came back since libglib2.0-* packages were upgraded from
2.54.2-5 (previous testing version) to 2.54.3-1 (unstable -> testing).
Reverting to the previous testing version solves the problem.
https://bugs.documentfoundation.org/show_bug.cgi?id=108246
V.B.
8 matches
Mail list logo
