Bug#926032: [chromium] Buggy / Solarized videos

2019-06-16 Thread aikhong tan
Replying to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926032#100

Thanks for clarifying.

I was actually confused by your previous comment, since I wasn't using that
version, 75.0.3770.90-1.

Now that I know, there are some bugs in that version which makes hardware
acceleration ON always, and the option to revert to software rendering is
gone.

Regards,
Aik Hong Tan (previously, Wallace)


Bug#926032: [chromium] Buggy / Solarized videos

2019-06-15 Thread victor . boyau
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

2019-06-15 Thread aikhong tan
Replying to victor.bo...@disroot.org comment at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926032#90

I think you have typo in your words.

I am saddened to see the hardware acceleration patch being taken away
totally.

Regards,
Wallace Tan


Bug#926032: [chromium] Buggy / Solarized videos

2019-06-15 Thread victor . boyau
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

2019-06-11 Thread Vincent Bernat
Package: chromium
Version: 75.0.3770.80-1
Followup-For: Bug #926032

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,

I am also hit by this bug and it's still present in 75. It seems to be known 
upstream:

 https://bugs.freedesktop.org/show_bug.cgi?id=109548
 https://bugs.freedesktop.org/show_bug.cgi?id=106490

I have tried the workaround of putting this in /etc/drirc, without much success:


  

  

  


Arch does that too:

 
https://git.archlinux.org/svntogit/packages.git/tree/trunk/chromium-drirc-disable-10bpc-color-configs.conf?h=packages/chromium=2323668d0369f38f9319d88b70d9409b0ca5abb1
 
I have tried to put the file in /usr/share/drirc.d/10-chromium.conf,
like they do, no success either. It's hard to know if this setting is
really used.

I have:

 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Baffin [Radeon RX 550 640SP / RX 560/560X] (rev ff)

- -- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (101, 
'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  75.0.3770.80-1
ii  libasound2   1.1.8-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libatomic1   8.3.0-7
ii  libatspi2.0-02.30.0-7
ii  libavcodec58 7:4.1.3-1
ii  libavformat587:4.1.3-1
ii  libavutil56  7:4.1.3-1
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcups2 2.3~rc1-1
ii  libdbus-1-3  1.12.14-1
ii  libdrm2  2.4.97-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libgcc1  1:8.3.0-7
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2
ii  libgtk-3-0   3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libicu63 63.2-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libjsoncpp1  1.7.4-3
ii  liblcms2-2   2.9-3
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.21-1
ii  libnss3  2:3.44+really3.42.1-2
ii  libopenjp2-7 2.3.0-2
ii  libopus0 1.3-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpci3  1:3.5.2-5
ii  libpng16-16  1.6.36-6
ii  libpulse012.2-4
ii  libre2-5 20190101+dfsg-2+b1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.3.0-7
ii  libva2   2.4.0-1
ii  libvpx5  1.7.0-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-2
ii  libxdamage1  1:1.1.4-3+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  chromium-sandbox  75.0.3770.80-1

Versions of packages chromium suggests:
ii  chromium-driver  75.0.3770.80-1
ii  chromium-l10n75.0.3770.80-1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.3-1

Versions of packages chromium-common recommends:
ii  chromium-sandbox 75.0.3770.80-1
ii  fonts-liberation 1:1.07.4-9
ii  libgl1-mesa-dri  18.3.6-2
ii  libu2f-udev  1.1.9-1
ii  notification-daemon  3.20.0-4
ii  upower   0.99.10-1

Versions of packages chromium-driver depends on:
ii  libatomic1   8.3.0-7
ii  libc62.28-10
ii  libdbus-1-3  1.12.14-1
ii  libdrm2  2.4.97-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-1
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libgcc1  1:8.3.0-7
ii  libglib2.0-0 2.58.3-2
ii  libharfbuzz0b2.3.1-1
ii  libicu63 63.2-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.21-1
ii  libnss3  2:3.44+really3.42.1-2
ii  libpng16-16  1.6.36-6
ii  libre2-5 20190101+dfsg-2+b1
ii  libstdc++6   8.3.0-7
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  

Bug#926032: [chromium] Buggy / Solarized videos

2019-04-25 Thread victor . boyau
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

2019-04-02 Thread Michael Gilbert
control: forcemerge -1 926151
control: severity -1 minor

On Tue, Apr 2, 2019 at 5:21 AM wrote:
> 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 ?

The vaapi patch is work in progress.  It could be unapplied, but then
hardware acceleration would be completely unavailable, which is
equivalent to the workaround but of course takes away from those that
have hardware that works.

Best wishes,
Mike



Bug#926032: [chromium] Buggy / Solarized videos

2019-04-02 Thread victor . boyau
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#926032: [chromium] Buggy / Solarized videos

2019-04-01 Thread Edwin Lim
Turning off Hardware-accelerated video decode from chrome://flags makes the
video render normally again.

Cheers,
Ed.


Bug#926032: [chromium] Buggy / Solarized videos

2019-03-30 Thread victor.boyau
Package: chromium
Version: 73.0.3683.75-1
Severity: important

--- Please enter the report below this line. ---

A lot of streaming videos are rendered incorrectly and truly
unwatchable. Sound is not affected, however. Youtube videos look good
but not those streamed from other popular web sites like these ones :

https://www.imdb.com (try any movie trailer, e.g.)
https://www.francetvinfo.fr/en-direct/tv.html (any embedded video)

Downgrading to a previous version like 72.x either from stable
ou from testing immedialely solves the problem.

VB

--- System information. ---
Architecture: 
Kernel:   Linux 4.19.32-tz1903270806

Debian Release: 9.8
  990 stable-updates  deb.debian.org 
  990 stable  wire-app.wire.com 
  990 stable  download.webmin.com 
  990 stable  deb.debian.org 
  990 proposed-updates deb.debian.org 
  777 stretch-backports deb.debian.org 
  666 testing deb.debian.org 
  500 unstabledeb.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-=
libasound2   (>= 1.0.16) | 1.1.8-1
libatk-bridge2.0-0(>= 2.5.3) | 2.30.0-2~bpo9+1
libatk1.0-0   (>= 2.2.0) | 2.30.0-1~bpo9+1
libatomic1  (>= 4.8) | 8.3.0-4
libatspi2.0-0(>= 2.9.90) | 2.30.0-2~bpo9+1
libavcodec58  (>= 7:4.0) | 7:4.1.1-1
libavformat58 (>= 7:4.1) | 7:4.1.1-1
libavutil56   (>= 7:4.0) | 7:4.1.1-1
libc6  (>= 2.28) | 2.28-8
libcairo-gobject2(>= 1.10.0) | 1.16.0-4
libcairo2 (>= 1.6.0) | 1.16.0-4
libcups2  (>= 1.4.0) | 2.2.1-8+deb9u3
libdbus-1-3  (>= 1.9.14) | 1.12.12-1
libdrm2   (>= 2.3.1) | 2.4.97-1
libevent-2.1-6 (>= 2.1.8-stable) | 2.1.8-stable-4
libexpat1 (>= 2.0.1) | 2.2.0-2+deb9u1
libflac8  (>= 1.3.0) | 1.3.2-3
libfontconfig1   (>= 2.12.6) | 2.13.1-2
libfreetype6  (>= 2.3.9) | 2.9.1-3
libgcc1   (>= 1:4.0) | 1:8.3.0-4
libgdk-pixbuf2.0-0   (>= 2.22.0) | 2.38.1+dfsg-1
libglib2.0-0 (>= 2.31.8) | 2.58.3-1
libgtk-3-0   (>= 3.9.10) | 3.24.5-1
libharfbuzz0b (>= 2.2.0) | 2.3.1-1
libicu63(>= 63.1-1~) | 63.1-6
libjpeg62-turbo   (>= 1.5.0) | 1:1.5.2-2+b1
libjsoncpp1   (>= 1.7.4) | 1.7.4-3
liblcms2-2  (>= 2.2+git20110628) | 2.9-3
libminizip1 (>= 1.1) | 1.1-8+b1
libnspr4   (>= 2:4.9-2~) | 2:4.20-1
libnss3  (>= 2:3.22) | 2:3.42.1-1
libopenjp2-7  (>= 2.2.0) | 2.3.0-2
libopus0(>= 1.1) | 1.3-1
libpango-1.0-0   (>= 1.14.0) | 1.42.4-6
libpangocairo-1.0-0  (>= 1.14.0) | 1.42.4-6
libpci3   (>= 1:3.5.2-1) | 1:3.5.2-1
libpng16-16 (>= 1.6.2-1) | 1.6.36-5
libpulse0(>= 0.99.1) | 12.2-4
libre2-5   (>= 20160901) | 20190101+dfsg-2
libsnappy1v5 | 1.1.7-1
libstdc++6(>= 6) | 8.3.0-4
libva2(>= 1.0.3) | 2.4.0-1
libvpx5   (>= 1.6.0) | 1.7.0-3
libwebp6  (>= 0.5.1) | 0.6.1-2
libwebpdemux2 (>= 0.5.1) | 0.6.1-2
libwebpmux3 (>= 0.6.1-2) | 0.6.1-2
libx11-6 (>= 2:1.4.99.1) | 2:1.6.7-1
libx11-xcb1  | 2:1.6.7-1
libxcb1 (>= 1.6) | 1.13.1-2
libxcomposite1  (>= 1:0.3-1) | 1:0.4.4-2
libxcursor1   (>> 1.1.2) | 1:1.1.15-2
libxdamage1   (>= 1:1.1) | 1:1.1.4-3+b3
libxext6 | 2:1.3.3-1+b2
libxfixes3(>= 1:5.0) | 1:5.0.3-1