Bug#926032: [chromium] Buggy / Solarized videos
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/ Graphics Feature Status Canvas: Hardware accelerated Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Native GpuMemoryBuffers: Hardware accelerated Out-of-process Rasterization: Hardware accelerated Hardware Protected Video Decode: Hardware accelerated Rasterization: Hardware accelerated Skia Renderer: Disabled Surface Control: Disabled Surface Synchronization: Enabled Video Decode: Hardware accelerated <= does not work for me Viz Service Display Compositor: Enabled Viz Hit-test Surface Layer: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated Regards V.B.
Bug#926032: [chromium] Buggy / Solarized videos
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 on instead of being disabled by default. Maybe this bug occurs only with some GPU models. I am only using AMD GPUs since almost 20 years. The bug hits me when using a Radeon HD6770 (Juniper) or a Radeon RX560 (Baffin) either with radeon or amdgpu drivers, respectively. Regards V.B.
Bug#926032: [chromium] Buggy / Solarized videos
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.
Bug#926032: [chromium] Buggy / Solarized videos
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 ? Regards, VB
Bug#902560: [console-setup] Bad (thousands) separator symbol in the console font
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 whatever language I can read is chosen. This occurs with at least Lat-15, Uni1, Uni2 and Uni3 console character sets. --- System information. --- Architecture: amd64 Kernel: Linux 4.14.52-custom Debian Release: 9.4 990 stable-updates deb.debian.org 990 stable deb.debian.org 990 proposed-updates deb.debian.org 777 stretch-backports deb.debian.org 666 testing deb.debian.org --- Package information. --- Depends (Version) | Installed ==-+- console-setup-linux| 1.184 OR console-setup-freebsd | OR hurd | xkb-data (>= 0.9) | 2.19-1+deb9u1 keyboard-configuration (= 1.184) | 1.184 liblocale-gettext-perl | 1.07-3+b1 console-setup-linux| 1.184 OR console-setup-freebsd | OR hurd | xkb-data (>= 0.9) | 2.19-1+deb9u1 keyboard-configuration (= 1.184) | 1.184 kbd (>= 0.99-12) | 2.0.4-3 OR console-tools (>= 1:0.2.3-16) | keyboard-configuration (= 1.184) | 1.184 init-system-helpers(>= 1.29~) | 1.51 OR initscripts| Package Status(Version) | Installed ===-+-=== kbd | 2.0.4-3 console-tools | console-data| 2:1.12-6 console-common | 0.7.90 gnome-control-center| systemd | 237-3~bpo9+1 Package's Recommends field is empty. Suggests (Version) | Installed -+-=== lsb-base (>= 3.0-6) | 9.20170808 locales | 2.27-3 lsb-base (>= 3.0-6) | 9.20170808 locales | 2.27-3 console-setup| 1.184
Bug#895047: Missing thousands separator symbol in the default console font
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 irrelevant regarding the current bug in console-setup-linux.
Bug#895047: Missing thousands separator symbol in the default console font
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. V.B.
Bug#887404: libreoffice: LibreOffice eats up 100%CPU even without any document loaded
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.
