[Pkg-chromium-maint] Bug#822170: confirmation: chromium: HTML5 video not working in chromium 50

[Tomas Pospisek]

Hello,

I can confirm the bug reported by Jürgen Bausa.

My system has a both an onboard integrated Intel GPU and an additional 
AMD Radeon one. I am only using the Intel one though:

$ cat /var/log/X.org.0.log
[...]
Integrated Graphics Chipset: Intel(R) HD Graphics 3000
[...]

$ lshw
[...]
         *-display
              description: VGA compatible controller
              product: 2nd Generation Core Processor Family Integrated
                       Graphics Controller
              vendor: Intel Corporation
              physical id: 2
              bus info: pci at 0000:00:02.0
              version: 09
              width: 64 bits
              clock: 33MHz
              capabilities: msi pm vga_controller bus_master cap_list rom
              configuration: driver=i915 latency=0
              resources: irq:54 memory:c0000000-c03fffff
                         memory:b0000000-bfffffff ioport:6000(size=64)
[...]

$ lspci -v
[...]
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA 
controller])
         Subsystem: Hewlett-Packard Company Device 1659
         Flags: bus master, fast devsel, latency 0, IRQ 54
         Memory at c0000000 (64-bit, non-prefetchable) [size=4M]
         Memory at b0000000 (64-bit, prefetchable) [size=256M]
         I/O ports at 6000 [size=64]
         Expansion ROM at <unassigned> [disabled]
         Capabilities: <access denied>
         Kernel driver in use: i915

[...]
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Seymour [Radeon HD 6400M/7400M Series] (rev ff) (prog-if ff)
         !!! Unknown header type 7f
         Kernel driver in use: radeon

Additional discussion and some ideas about the cause of the 
bug can be found here:

    https://groups.google.com/forum/?_escaped_fragment_=topic/qubes-users/bdU_oOUcO94#!topic/qubes-users/bdU_oOUcO94

I have worked around the bug by disabling chromium's usage of the GPU from 
the command line:

    chromium --disable-gpu ...

Thanks,
*t