chromium not playing youtube html5 vids properly debian-8

[raah...@gmail.com]

[1:3:0417/163438:ERROR:video_layer_impl.cc(369)] Not implemented reached in virtual void cc::VideoLayerImpl::AppendQuads(cc::RenderPass *, cc::AppendQuadsData *)

Think this started happening after latest debian update, anyone else know how to fix this can't find any info on google.

if I create a new vm, videos play fine when i first run chromium. but when running chromium the second time the videos are messed up again and I get that error.

[raah...@gmail.com]

not sure but might be related to this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821154

[Axon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

raah...@gmail.com:

You might have more luck with this one by reporting the bug directly
to Chromium or by asking around Debian-specific support places.
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXFDGjAAoJEJh4Btx1RPV87ZwP/iHWqcs0xhZD+B578FZRXT3l
sJrICuQfwb0rJNvMSk2lL7IXe4pCk6b4hNKnwTuHqq/1rIgDogUYPat9a/IE7ffz
Q92QgA0tRv9gfKEZMKYRKZPGst+HYzcwtj9xcDa708JO0ow3iROC48Wvm4RPSaWA
11GNYSXdrauNXXUoTHvXuLnaDqHi44/x9ClXpteyC7eW6GkNyaQ2OzvrZaoolG+h
Mb7SzRjmH5RPM8EJzmLaMWC/JJfXSVyD62bNQmiDIUcTBRfDrcnPbJrp5q/nVEDN
1h2WCSZGwUtsW1lVrJuPPC5MpEFY+DVscUZlX9K3dThL7XAfUSbeYqy6BI1+zPvN
FisBF7AAibF8RWCHAaFQuwSZf0ianeKfzJyga9Lc5qrIGH3pgcMs9hoS4rXgTSE4
CWugr9RuzYYhvNe/G3PPDuTVBTl5m/TnxsVijzJYO6S1Nd+cb3HdpT/GWl+Cx8P0
vQwrnu6JeaMtg7Gi5grk3RJJsc6M+nd16Nq9WTtIXDXr9pVOo6IgRRWjbPxyaxMD
TlyQvxH6+9HC/KbhgVTzqJdSNhncN9goYROsXt/G0NtTrXJcw9H4mfbgEQpwaAkK
u9czI72hGR5vU/5pUowDzLoiruhFJObutNPkNRjXwrafRfTR077H64KztBkAeWvm
fAeym0BeRBEX+G4UGxji
=/M2y
-----END PGP SIGNATURE-----

[raah...@gmail.com]

ya apparently latest chromium have issues just posting in case anyone else wondering same thing.

[Dave Ewart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sunday, 17.04.2016 at 18:16 -0700, raah...@gmail.com wrote:

> ya apparently latest chromium have issues just posting in case anyone
> else wondering same thing.

Just in case it's related: I've been having trouble playing videos on
Youtube via Google Chrome on the fedora-23 template since the latest
update too. Anyone else?

Dave.

- --
Dave Ewart da...@sungate.co.uk, http://twitter.com/DaveEwart
All email from me is digitally signed, http://www.sungate.co.uk/
GPG key updated Jan 2013 see http://www.sungate.co.uk/gpg
Fingerprint: CF3A 93EF 01E6 16C5 AE7A 1D27 45E1 E473 378B B197
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQQcBAEBCgAGBQJXFJrSAAoJEEXh5HM3i7GXZAkf/0j2lEMgN+RuM/CghSXH+sIb
Hc8B/mQDADdfsbO4VQALXWGZg6cln7duPdlbZZr18pg0LoTELH3b6/1Xl/WgLOLX
EKSvguZZT1ejHIWzAlVSoxrCc5gnJ6iPqv9h3Pqv+ybMwpbiMgpuHXrk8hZ9PHf2
qwB1/he9rm0SJdKf5R/BaIzkelekHnqdSsP74h2epC3816Z4i7VVmcAnMWcbPM8J
VpVEShq6eq16Zr3TPBZVkxL1TC9UCCqhX7nJqIatXeZj5hRxRujwbkgHqG73NZkj
VMHLMUcAXAdl0PiNW18m3iJpvycXZg+Ri8Po/ADghDLbIsRMpMQqeNB2xqWnGtS6
E4ZVQGUbMYNygs89h2rC8+yniJXi576IUGlyTnEE/62y9AtSGsH2lSPRLrP6+eYd
PePiXQBkcO9y+L5Jxflg6njxZAZjfffgTQ2L8JI0+kGznplryDDtw3NrWLHM5kpl
O0viWKFBqiguZ0bHl51409ZysSfU5Vk47Wgf3yLboWZXFdR20jRBhSwEQLh/XTIR
bn1XhRl8kfl6MlctVAVR751p45Qk99CC7NQ9UWXqbFO49YFF+qSymaqnmcbLLpgp
zSNyXYjwtHyE7H3DrRlmdJGoeb83ExT5cMFy8yFEfdmvhyf91torg6tD5Ho4umP1
2h8cOh1UCjl1ynyGGvp+cuYAddFARDbVR8DKh8YAgaNCnf4APJZpxBRAOIHhPJKP
kxEcrpT7NETQLneu+eGurkv2GAsDXz57FrJFy7N22Vm8v9YxT6b1HhBt3J0frvKa
64BtkIiVAB1OoKjRR1SlW9SqObYVwdHPK326ziFaXrkvf85svqB+6pVq1lZpK9d7
C9zh32oADxH+gqV4xa5wW7Sbs1w5L9JURleDWAu5zNoVm4gI2Ru+9ClQXTjqsyDo
a4Xm/Ueq4wRrDuj1RGaBTgVv4BpwCPt+xvEiS8urXwHhXc0RVHWQYnx5jz4ScK1U
skJCCBm3H/psYObaRBP8CL6R08BEbFZ/XVxgnTgGuHYWQnc4fai92XDftaZBJzDC
ZC5lT3jMnof2KEJBIvXEprHFcjpUSKq33LihngiRmagtJckbz4ElAGJ/vuOwbLWe
BuIGUx8n+nHTG0+K/YdfIV0H1fUbf5epB1rxQ0Ld/pZrcXE8L3wOvn2LCaxenOTm
EcFGQfxMyyknw+fcxUa8UXVWPhE5aC7lM8DA3sO82psjqD+slNz8Fod2xTB4vaYV
TbWX1hrIdtUaim6Lq6om/fUBM9RLKRVC9SnlUZEbc699a2ywF8Juz0Kj6QDaD96V
X1D9PiAOak7fh/gdh1YmGx0xC1N2fryHAK/yNBOoD64JfHv8dCPhl/mjJ/hQKs0=
=yXOl
-----END PGP SIGNATURE-----

[raah...@gmail.com]

mine fixed itself I dont' have the slightest clue what i did but I'm no longer getting the error message and youtube vids play fine now. Only things I did that i'm not sure are even related, are i edited the /usr/share/applications/chromium.desktop file for terminal=true and launch chromium with --disable-background-networking --disable-component-extensions-with-background-pages --dns-prefetch-disable

I also went into advanced settings and unchecked every box under privacy except "send a do not track request"

I also unchecked all the boxes under People, Passwords and forms, Languages, and System.

I also went to On startup selected Open a specific page or set of pages and set it to about:blank

The extensions I use are https everywhere, scriptsafe and ublock origin.

[raah...@gmail.com]

You have to edit the .desktop file from the template. I also use an apparmor profile.

[raah...@gmail.com]

On Monday, April 18, 2016 at 1:23:14 PM UTC-4, raah...@gmail.com wrote:
> You have to edit the .desktop file from the template. I also use an apparmor profile.

in case anyone interested this is the apparmor profile I use. its the basic ubuntu one and probably not that restrictive. and the latest chromium now needs some scary permission like capability sys_admin or else it won't start, but I still think its better then nothing.

dpaste.com/138SEJ7

You might have to load chromium without the profile enabled first, and then close it and then enforce the profile. or instead just create the needed directories manually.

[Dave Ewart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sunday, 17.04.2016 at 13:41 -0700, raah...@gmail.com wrote:

> [1:3:0417/163438:ERROR:video_layer_impl.cc(369)] Not implemented
> reached in virtual void cc::VideoLayerImpl::AppendQuads(cc::RenderPass
> *, cc::AppendQuadsData *)

This is still happening for me and there has been a couple of Google
Chrome updates in the meantime. HTML5 video just doesn't appear and
corrupts the area of the screen where the video would normally play.

Anyone else seen this and know how to fix it?

I noticed that it worked OK in the DispVM - then I realise that this was
because if I clear ~/.config/google-chrome it *works* on the first run
and then fails to run on subsequent runs.

I don't want to install Flash so I can't use Firefox for this.

My template is fedora-23 with Google Chrome (Stable) added to the
template via RPM direct from Google. It has been working OK for months,
FWIW.

Dave.


- --
Dave Ewart da...@sungate.co.uk, http://twitter.com/DaveEwart
All email from me is digitally signed, http://www.sungate.co.uk/
GPG key updated Jan 2013 see http://www.sungate.co.uk/gpg
Fingerprint: CF3A 93EF 01E6 16C5 AE7A 1D27 45E1 E473 378B B197
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQQcBAEBCgAGBQJXHMwTAAoJEEXh5HM3i7GXXC8f/3dXyM0AI7w7MK2hzwaPdjsz
4e2W+JWeOt6ozkWP2ThwzBjRkjfHJwkrUdgKF0tKp4JKPMbSPxpE1uypWlDMiLle
Bed/CwsK3CYbOS5YV5lQki4cHUyCj2hgUVExw2QU6tEAv8zvTf3SdfGcQBrSBn6E
CAUvjAG+ia73CaqLUxzAJLFOMiBX43q8FGhr8Gup+1tXnAty08iIJd4ZGq+H6IEv
iJyB+mFVIuMm9/zffLWO9kTh66u/gqcywk9k7ldzQfZ4VMeiRB9PdQ8s+VPYNZix
SjQBDfSsTAkUTTZE8rpRwbmt/qlNwRL2t9awTwVndlG9qbRyaYZpQ0aDiYQplw46
bvxeX1SsisIbBkmQgIrU6OGrlzRe8WwCK70BieVy5eApmkKuNdFTvGA847WzoNJD
ai/g2Lrd3ZlmtL624jbhfERT5ezKPkFHDnvkvff/GMmjQBQUwiOTqUwoHBAGvbVQ
y2zK9Pbm4iQZu8PrYlm0zmBeuOVy5697jbDggpwR0vivEkHfJdIr9fYkQ/fJU+yU
QbMKdf3NVyQ0QY0BStAUGkMAQrMt9d98Sgd/ohdKuyAo3VZzvnU2P9dm3FAr7mMA
Iu5AivpwGSXaOZ+OBi58lKvx+0/MFuYJO9ZkUxCSFpxpe+P66zXaWyiOQwc6Dt/s
PMz6x+oCI0zluxTq8TVIoAbegj1cY0HjkzRjEM6wZ103ibIp0pLWuqahyQp1ifRX
l8zsQlYRRQrW6/65SqggWybb67NngMWen8+D9R4QvvCag2rdGloWFCh0Uvdo6MSv
SOZ/vCo/SjDNiaFit8KIWnWRUnbKC0GnFnKn3Li/hyIO/L0YqdLAtsK/oR5TcOCt
iMKNyauCHVdGYIETujXsHb/qH08DL30yX19QfdlWcGVnuTvAe4d66+okDYFC9/IA
7aMKM2xSg+VXyO6209/jr3XkglYy3oXdKnjPslkik0mpLmsvszO0FFFz3uR8GQKu
PuqqR9tdjC0x4V4xhYpsEb1McLwSr7Avp1DGyuB0pdBoT16qUAiw5bSuWqh3LL7s
3M+f6ZIuIWYWwXB/YWVM6tdjYMnoHN01RurHA/TIM/VxX7J2S28x87DC1O2d1Ea3
AfLmKNS3d0sKHNJYDvUi091imfYJXxfIg9B0Y4sJUIcQ1+Y2uRHbwCNd0XqbXLsm
UF4aw/mdR1pcSs4A8AegR872i7O/Vhv8qHKECeX8Rrte31CTH8HjjVOyRNM/8lmS
OQ6iTuSarhy7kZxFhAbQG+cR4PHc2kLDFsO5Wj5A+1LYs5DmIDjYwLe9y+KCzxY3
gqZibgVvKmQqXl+eQvcCNgZGG+oJyISNb8BbYrySJR7Qib3nvgVOHy3q1HoXAbc=
=613U
-----END PGP SIGNATURE-----

[Axon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dave Ewart:

> On Sunday, 17.04.2016 at 13:41 -0700, raah...@gmail.com wrote:
>
>> [1:3:0417/163438:ERROR:video_layer_impl.cc(369)] Not implemented
>> reached in virtual void
>> cc::VideoLayerImpl::AppendQuads(cc::RenderPass *,
>> cc::AppendQuadsData *)
>
> This is still happening for me and there has been a couple of
> Google Chrome updates in the meantime. HTML5 video just doesn't
> appear and corrupts the area of the screen where the video would
> normally play.
>
> Anyone else seen this and know how to fix it?
>
> I noticed that it worked OK in the DispVM - then I realise that
> this was because if I clear ~/.config/google-chrome it *works* on
> the first run and then fails to run on subsequent runs.
>
> I don't want to install Flash so I can't use Firefox for this.
>
> My template is fedora-23 with Google Chrome (Stable) added to the
> template via RPM direct from Google. It has been working OK for
> months, FWIW.
>
> Dave.
>

I haven't noticed any issues with this in my fedora-23 templates. It
sounds like it might be something specific to your template. Can you
try installing Chrome in a clone of a fresh (RPM) fedora-23 template
and seeing if the problem occurs there?
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXHNn9AAoJEJh4Btx1RPV8vHAQAPJL37fibckYTrkW+J/jfi8X
0eeeUdUsWQKwneFP8Fmm/dAVODZuukfz7xUmiWdBNre1c/rzMMITVjM6PUyYtHTR
0qizlBQU35obDdtVedkBXpkH/aJ28AismOcKtPh095wbU5ySv6U71zJDLNJJANLF
hZJhC+JtXiqmkLkxhuoHLcKZorvXG/DgUBMPQFXiGM+VPR5H0hVvy9ly7qoTJlKj
4bDvJoTZcaWPb55SHj5Y1LN43CqLooP6uI4HYFHQ861ydkwNEfWUe5bz3cTxmuTW
ol3hEzHNgcb+TvvpGbUTV/5uMLOcAOkFuvFR0ghopRS9UeejRlFlIUfew1ORQ5fA
nOH1DxNDtsLgIi+a7XGE9g7/41UyTVpGDveTNrYHK8v7GDs7y/VU8tA3PsSaEfuf
p23be0SAcaWHU6tqRE2/NOfBC5MsD53DiENTrLdioXgpsxAk/qD6WM6prU6edMKQ
BiXDiMvCf4v2/mk8OUhgAu/iRaFFFhd+l31gBoSbwTiGSBZaeDZkDNySP9aZcyUM
3T0doJSsKaDmayKV/uo+OZcPEl1pSYgeOsXHOzfqdPPYsa/ivrngQn5Q8revhvwj
Ky7gWhKT9oeCQdd0zXMN8GG++dj2w5fkFpL9KjL05BoIO4wkuTFD6YoWyk67qhDk
qMbj7XjK5q31HQD1kByf
=aAso
-----END PGP SIGNATURE-----

[Dave Ewart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sunday, 24.04.2016 at 14:36 +0000, Axon wrote:

> Dave Ewart:
> > On Sunday, 17.04.2016 at 13:41 -0700, raah...@gmail.com wrote:
> >
> >> [1:3:0417/163438:ERROR:video_layer_impl.cc(369)] Not implemented
> >> reached in virtual void
> >> cc::VideoLayerImpl::AppendQuads(cc::RenderPass *,
> >> cc::AppendQuadsData *)
> >
> > This is still happening for me and there has been a couple of Google
> > Chrome updates in the meantime. HTML5 video just doesn't appear and
> > corrupts the area of the screen where the video would normally play.
> >
> > Anyone else seen this and know how to fix it?
> >
> > I noticed that it worked OK in the DispVM - then I realise that this
> > was because if I clear ~/.config/google-chrome it *works* on the
> > first run and then fails to run on subsequent runs.
> >
> > I don't want to install Flash so I can't use Firefox for this.
> >
> > My template is fedora-23 with Google Chrome (Stable) added to the
> > template via RPM direct from Google. It has been working OK for
> > months, FWIW.
>

> I haven't noticed any issues with this in my fedora-23 templates. It
> sounds like it might be something specific to your template. Can you
> try installing Chrome in a clone of a fresh (RPM) fedora-23 template
> and seeing if the problem occurs there?

Good suggestion, but it doesn't seem to help: I downloaded a fresh copy
of the fedora-23 template and made only these changes:

sudo rpm --import ~/QubesIncoming/personal/linux_signing_key.pub sudo
dnf install
~/QubesIncoming/personal/google-chrome-stable_current_x86_64.rpm

and I see the same symptoms. Sound OK, video box is black/corrupted.

Downgrading Chrome to an older version makes the problem go away;
installing instead Chrome Unstable doesn't help. It looks like
something happened between Chrome 49 and Chrome 50 which caused the
issue, but I can't see what and am confused that it's only (apparently)
affecting me!

Dave.

- --
Dave Ewart da...@sungate.co.uk, http://twitter.com/DaveEwart
All email from me is digitally signed, http://www.sungate.co.uk/
GPG key updated Jan 2013 see http://www.sungate.co.uk/gpg
Fingerprint: CF3A 93EF 01E6 16C5 AE7A 1D27 45E1 E473 378B B197
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQQcBAEBCgAGBQJXHOlcAAoJEEXh5HM3i7GXOJgf/jz+ENSnpDskz6PkM1P/622F
UPw5xsvnPzICwHcmt5ThTb0U2FnLk5gBYAOlgWDTwbQrwKZNs1nL2LoZGBYPiD3o
9kyKZWeAYepF8VCtxjYUkQBWoo3BIYCTsunqV0Mq50RkxAZkZXihyOw8OqPuhofI
Amld4Iav2u1KarXiSO/fFbYsIQs8LjxlrVSYlE1bIFzPwK2kfOiM1NZs1zOiQHHO
LxxTUvE+5dpL3qxfak6CnJ9yxebTME2iR9MkeYGgmpACI20kU2q5yPnaTNhICjry
3IWTSPG4icIS+ONjXHCNO4IFnI5uJzG1VhK6G7RD1q3XEsfH8s5fcwlYP8imeXCq
0BUQ003DSys6eubYuh8k4rDJGIocn4XzHWxl8xaoASIqlY2pWtLqqAlsEME2VowL
p6t6bnrpNkfw4ukybi2+uIFuBxKMEXkE6ATIoIOQXc7RXoWMdsSF995GUnYojVOh
GuEqEiMkM7Uu1odirNDDseC8gkIJOphwxCptnwjauqFrmzkGQjy0C+ygUzkDJc2P
sEoV2pPsydD5koI5dIBjc3qU5A/pMCxtYOYfP4BxLYs3SCYSJxTsGJwRZDUtAFwc
xe7hkotBLue5rdObP75lUyOxrnSTD1S57s1W71AXTPhiGQxurxfvh/CDQJcFv9YW
dp3ZcPdcFG7c/twskQ1Lp3XLTpS2VE2jZZkxd8QYxmE4ClJID1p/WB25yVRmVvk8
laEExJ06LLIIZy6aD0tRiIzOkf/FrnJ+gjnrRnJb+wTLihF5VSLdxbZTH0xSrj9+
OPstQidMZJm6ADsLRxe/St5GPKl6N4HEBdHpe7QriUmB1TSydfOWKSlxyBy7xnqQ
UziS0vqwrwf/fVgyfwatKJABQ4To8xYYME3hxXHwpoXxFkMRrRg1sCGDh6nPV/Am
5VPDQkWVqWPtENQtTgkNdmxfH+CPkcLW6GZi1qPyW//Ub5YKBUfxUcsJDBWJZUOu
ld8tJ4FQ/lpDD+O78kZpmBXDX9LLUIx6uy0Gs5Hp6tKxMupn6GtbgkCXuqZAXrdK
wHrGaBE63gmfS6Wgg2FwLT4mJMLJf8re9rbTpAv9CD341zCCf/C8KrNVOWL5nFQ+
PupR/+/4o0KRaF6Ba0ScfeBK5IhdYUwVC86BxxQCAOvcprn5XhDFMvNeA7M1y2/c
Fr5+/Jf6os9ZLo/55lT5+ITY1yU97RcHF+r0YjPLQNEhTgRHPmhUwmuy35coqh1Q
3TSx1iU4stl9hr26EEjhjg7Nl8OOhH3ytM7w3vvBbJYd9Wvx4qiXvAJiH8zbKov0
Bd6mpe5d9otU2x/2/985SrQPUDmxS2YbSYKon9bztvns1gG9knlig1yHhBJYWEo=
=D9As
-----END PGP SIGNATURE-----

[Dave Ewart]

Well, I found a fix: I switched off "Use hardware acceleration where
available" in Chrome's advanced settings. Now everything plays
properly. Don't see any obvious performance issues, so hopefully
that'll be OK.

Does this mean that it was, possibly, a graphics driver issue?

I use the nouveau driver: nVidia card and I've never got round to trying
to use the proprietary driver for it.

Dave.

[raah...@gmail.com]

hmm maybe I also use noveau.

[Daniel Wilcox]

Keep in mind, noveau/nvidia/video-card drivers are only used and exist in dom0.  So if Chrome is linking into libGL and deferring to it for video playback-- it would be issuing commands to a GPU that doesn't exist in your appVM (and which has no direct access to the video card).

My understanding is that there is a custom X.org driver for Qubes to basically pass a framebuffer from appVMs to dom0 via the Xen memory sharing bits -- so the GPU more generally won't do work outside of dom0.  Turning off hardware acceleration in Chrome then is the appropriate solution although it is unfortunate that Google decided that it should default to 'on'.

=D

--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a11c53b0-a583-4aee-93be-cc32368a7d11%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Dave Ewart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sunday, 24.04.2016 at 22:16 -0700, Daniel Wilcox wrote:

> Keep in mind, noveau/nvidia/video-card drivers are only used and exist
> in dom0. So if Chrome is linking into libGL and deferring to it for
> video playback-- it would be issuing commands to a GPU that doesn't
> exist in your appVM (and which has no direct access to the video
> card).
>
> My understanding is that there is a custom X.org driver for Qubes to
> basically pass a framebuffer from appVMs to dom0 via the Xen memory
> sharing bits -- so the GPU more generally won't do work outside of
> dom0. Turning off hardware acceleration in Chrome then is the
> appropriate solution although it is unfortunate that Google decided
> that it should default to 'on'.

That's very useful and helps me understand the possible issue.

"Use hardware acceleration *where available*" (my emphasis) is the
option name, and hardware acceleration is clearly unavailable inside a
Qubes AppVM, so Chrome's bug is (I am guessing) that its detection of
'where available' is broken. Perhaps this was introduced in Chrome 50.

(I'm speculating here, of course, but what I write above is consistent
with what I've seen.)

Dave.

- --

Dave Ewart da...@sungate.co.uk, http://twitter.com/DaveEwart
All email from me is digitally signed, http://www.sungate.co.uk/
GPG key updated Jan 2013 see http://www.sungate.co.uk/gpg
Fingerprint: CF3A 93EF 01E6 16C5 AE7A 1D27 45E1 E473 378B B197

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQQcBAEBCgAGBQJXHeGjAAoJEEXh5HM3i7GXmYgf/R8BSQYv2N2ZBeAb9c/1CBQC
T2QK8ZslkrlDWnIAanF+qTjAECaXK1pAZ1I1OxqIPHkfT91iSQdun/Iwppc0ZkbE
k8IqaylfVJqZ4g/szbvrZJRNXsGNYnkqwZCDU55k8Dbtat9fRmylRWWIug5StrV6
H/5SKpOSZ37/Q6ZjiVdnwUbbELHzz+R7QyCw1Yev8GLVTv8hL6KoAYhf+3cIbyyq
hTx27ywAn2IdokNsqIpk5x0sAYg0LnLSNkao+mOfC5lKgmQ+VWFtRk83l/vdZxsQ
l2SxUrKMM96QZIsYyilfvq36efpOVAIYrRgMIu17LueVK59/GCShoXkA6tThvW7O
9TcLlblhBRBCdMpZL5JcKqD99F9rQ7pFzsPxWDgfcCYisp0jTSNrVJ4eHBsAU80j
dg4P0MC/j4G/qrVtEsMj6tHmARGi3N885QhGCaL94wHx5dTT+FIGVpQG4sy026zD
V3IYUDF/tWidSodeD0pXdCuoSEIfvAEFgp7y36KC2NBnXvAT41DQ4rRYAqc5D+oS
wM6yIHM/l1LYzUQaXrhTpl0MeEVcgNqJQD/Rad274SRzY/3AdTc/wkbGb/QLl3Ng
hxOA874pBChume1INp++DBfmrjayWiz3quF7WKgkwGC24y9H5Blbp5Mh6aDERJjt
MO0JfHEw+4k6vYiAPIbuIV+zpZ38HitGk+jB8Z9TLD+uRLO3AR906sKc9DY6Ji9I
onHUoZ639Ee7CTeWrCJF7NTxkLfanxakHPY9Bzcnal2jt2UeMMxQxO+W7ry6iNT0
u00sEhfJ2fZxkkMuhfhoAiX1VEZl8HoVsTZnon6SVrkazfgJD04NmEmLozvfWmwb
8cDSv4t4H45yCIP5dpRCdMRUWbNk6VC8iGNX92sqoh1WIdmVSwcEMVnPRXdUV8Yv
W22PgXDuTBHuY4DQ0DFuR+S/cDm/e7weWg5KGRflx3blvTnK5qVXXhHljjLHHz/D
TtQtc5blPVPdJdgaQjHqeiEbt994GHxrt5j8qSF2Be6KjSDqqvKmyhSOWWBJkxaS
eTNioJs/6bAJZUgTMECOf0gPe7HYX5+xsKkvItbvbV5ANqARjuEUQSoZMGvmAQB7
zive/O9emX9xoRjdC/X4od9gTbWCPhNNd6hnc/tVqPfszG9i8wnfx2ndphIVPR28
NQSF4OyLUgtOy6BN4nvwiTdRNtKUBlWDlEKUXB5w65XKknBCe9nmKLbICn6hiM/b
FiqaW11ZCnrXWq+iB2o9U+qCVH0tCXDUEam1vgIvsuGD5uuhqeuxB+NESc/6RKBd
nxL2JbCbNl7eYQN9D3Sv0HYTUBS+gxMX2TYhwhURZV3d9rs/Wo2oFI+7V3PP5yY=
=IE2s
-----END PGP SIGNATURE-----

[bryant...@gmail.com]

Confirmed. I have the same issue. Resolved by disabling the "Use hardware acceleration where available".

[212:214:0425/231356:ERROR:video_layer_impl.cc(369)] Not implemented reached in virtual void cc::VideoLayerImpl::AppendQuads(cc::RenderPass *, cc::AppendQuadsData *)

This release is : 50.0.2661.86-1 , looks like it went live on Ubuntu PPA on April 20th. ( http://www.ubuntuupdates.org/package/google_chrome/stable/main/base/google-chrome-stable )

The beta version has the same problem : 51.0.2704.22-1

[kins...@gmail.com]

Confirmed. Uncheck "Use hardware accleration" did the fix.

[raah...@gmail.com]

nice, I must of clicked it and forgot. :)

[kahea...@gmail.com]

That was it. Thanks.

[coend...@gmail.com]

Op donderdag 5 mei 2016 14:18:15 UTC+2 schreef kins...@gmail.com:

yes for me too, disable hardware acceleration in chrome advanced settings