Package Details: chromium-vaapi 75.0.3770.100-2

Git Clone URL: https://aur.archlinux.org/chromium-vaapi.git (read-only)
Package Base: chromium-vaapi
Description: Chromium with VA-API support to enable hardware acceleration
Upstream URL: https://www.chromium.org/Home
Keywords: browser web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: samcv
Maintainer: OneObsession (maximbaz)
Last Packager: maximbaz
Votes: 74
Popularity: 6.775989
First Submitted: 2016-07-09 09:44
Last Updated: 2019-07-04 11:16

Dependencies (48)

Required by (47)

Sources (11)

Terence commented on 2016-09-18 13:39

Updated to last version, getting the following with nvidia 370.28 drivers:

libva info: VA-API version 0.39.3
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_0_35
libva info: va_openDriver() returns 0
libva info: VA-API version 0.39.3
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_0_35
Received signal 8 FPE_INTDIV 7facfb7a32da
#0 0x557e823ff15e <unknown>
#1 0x557e823ff539 <unknown>
#2 0x7fad0ebf1080 <unknown>
#3 0x7facfb7a32da <unknown>
#4 0x7facfb7a61e8 <unknown>
#5 0x7facfb7a6236 <unknown>
#6 0x7facfb7a640c <unknown>
#7 0x7facfb7a71e0 <unknown>
#8 0x7facfbe1339e <unknown>
#9 0x7facfbe142c7 <unknown>
#10 0x557e86cda7ce <unknown>
#11 0x557e86cdcf87 <unknown>
#12 0x557e86cdd17d <unknown>
#13 0x557e86cdd99f <unknown>
#14 0x557e8789f92d <unknown>
#15 0x557e87899a6d <unknown>
#16 0x557e8734bfdd <unknown>
#17 0x557e8684b716 <unknown>
#18 0x557e8684c0ea <unknown>
#19 0x557e872b9be5 <unknown>
#20 0x557e8684b591 <unknown>
#21 0x557e82f440e3 <unknown>
#22 0x557e824701cd <unknown>
#23 0x557e8241ed6d <unknown>
#24 0x557e8241f97d <unknown>
#25 0x557e8241fc68 <unknown>
#26 0x557e8246e661 <unknown>
#27 0x557e82439604 <unknown>
#28 0x557e8241da85 <unknown>
#29 0x557e86847b42 <unknown>
#30 0x557e823ce428 <unknown>
#31 0x557e823cc5e9 <unknown>
#32 0x557e81f38e8a ChromeMain
#33 0x7fad07398291 __libc_start_main
#34 0x557e81f38d3a _start
r8: 0000000000000000 r9: 0000000000000000 r10: fffff413af994106 r11: 00007fad0b9f14d0
r12: 0000000000000000 r13: 00007ffdb6078ba4 r14: 00007facfb7b108c r15: 00000beefc022e00
di: 00000beefc022f50 si: 0000000000000000 bp: 0000000000000000 bx: 00000beefc022f50
dx: 0000000000000000 ax: 0000000000000000 cx: 0000000000000000 sp: 00007ffdb6078b80
ip: 00007facfb7a32da efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
[9328:9328:0918/152637:ERROR:display_info_provider_aura.cc(31)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const display::Display&, extensions::api::system_display::DisplayUnitInfo*)

From chrome://gpu

GPU process was unable to boot: GPU access is disabled in chrome://settings.
Disabled Features: all

Log Messages
GpuProcessHostUIShim: The GPU process exited with code 256.


agm28011997 commented on 2016-09-01 09:02

I don't know why when the gpu sandbox fails the hardware accceleration is disabled in all chromium if vaapi is enabled, have you fix the sandbox problem or the deactivated of all hardware accel avenger? in fgrlx and privative drivers with nvidia there is the problem of fault of vaapi.. fglrx uses a backend like nvidia does, no? and amd open source has vaapi and vdpau but nevermind chromium fails to sandbox gpu proccess and disable all hard accel

samcv commented on 2016-09-01 06:32

@Avenger
Awesome! Intel had been fine but for whatever reason I wasn't able to pin down the problem with some non-Intel cards. I will check out that patch. Assuming it is acceptable for Intel as well, is it okay if I incorporate parts of it and add credit in an updated patchfile?

Avenger commented on 2016-09-01 06:28

I could not get this to work either on radeon open source or nvidia proprietary drivers. I tried another patch that I ported to chromium 52 my self and it works:

https://filebin.net/1zd33dmb10zmpbi9

agm28011997 commented on 2016-08-14 18:53

have you tried with opensource drivers and without vdpau backend? i think the backend is the problem so.. try to put enviromment variables to trye other drivers.. i dont know other thing to do

Gavcheg commented on 2016-08-14 18:34

No luck.
I have nvidia hardware with driver version 340.96.
vainfo:
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_0_35
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.39 (libva 1.7.1)
vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 0.7.4
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointVLD
VAProfileH264High : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD

So when i start chromium:
chromium
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_0_35
libva info: va_openDriver() returns 0
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_0_35
Received signal 8 FPE_INTDIV 7fefec0ad2da
#0 0x556e5b0249fe <unknown>
#1 0x556e5b024dd9 <unknown>
#2 0x7feff9cf3080 <unknown>
#3 0x7fefec0ad2da <unknown>
#4 0x7fefec0b01e8 <unknown>
#5 0x7fefec0b0236 <unknown>
#6 0x7fefec0b040c <unknown>
#7 0x7fefec0b11e0 <unknown>
#8 0x7fefec6db3ae <unknown>
#9 0x7fefec6dc2d7 <unknown>
#10 0x556e5f7d692e <unknown>
#11 0x556e5f7d8727 <unknown>
#12 0x556e5f7d891d <unknown>
#13 0x556e5f7d8e2f <unknown>
#14 0x556e60377a5d <unknown>
#15 0x556e60373ffd <unknown>
#16 0x556e5fe4819d <unknown>
#17 0x556e5f1f2579 <unknown>
#18 0x556e5f1f2f4a <unknown>
#19 0x556e5fdb6c72 <unknown>
#20 0x556e5f1f22e1 <unknown>
#21 0x556e5bab3793 <unknown>
#22 0x556e5b093cad <unknown>
#23 0x556e5b04410d <unknown>
#24 0x556e5b044d1d <unknown>
#25 0x556e5b045008 <unknown>
#26 0x556e5b092439 <unknown>
#27 0x556e5b09247d <unknown>
#28 0x7feffeca9dd7 g_main_context_dispatch
#29 0x7feffecaa040 <unknown>
#30 0x7feffecaa0ec g_main_context_iteration
#31 0x556e5b09218a <unknown>
#32 0x556e5b05e384 <unknown>
#33 0x556e5b043045 <unknown>
#34 0x556e5f1ee9d2 <unknown>
#35 0x556e5aff1d98 <unknown>
#36 0x556e5aff0fd9 <unknown>
#37 0x556e5ab4e77a ChromeMain
#38 0x7feff8127291 __libc_start_main
#39 0x556e5ab4e629 _start
r8: 0000000000000000 r9: 0000000000000000 r10: fffffe5b1fbdd7a0 r11: 00007feffc4034d0
r12: 0000000000000000 r13: 00007ffcb185fc74 r14: 00007fefec0bb08c r15: 000001a64b2d3500
di: 000001a64b2d3650 si: 0000000000000000 bp: 0000000000000000 bx: 000001a64b2d3650
dx: 0000000000000000 ax: 0000000000000000 cx: 0000000000000000 sp: 00007ffcb185fc50
ip: 00007fefec0ad2da efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
[11966:11988:0814/212114:ERROR:browser_gpu_channel_host_factory.cc(119)] Failed to launch GPU process.

And on chrome:gpu:
GPU process was unable to boot: GPU access is disabled in chrome://settings.
Disabled Features: all

I trying enable "Override software rendering list" but also no luck.

BTW, mpv plays video with vaapi, so it works. No idea why in chromium this broken. :(

agm28011997 commented on 2016-08-03 03:30

vboufleur for me with amd graphics in chrome://gpu tell me the exact thing but in options i have enabled gpu acceleration

agm28011997 commented on 2016-08-02 18:44

i receive an error while I launch chromium vaapi enabled in amd graphics pc, i tried with no-sandbox but it didn't anything, the terminal show this.
chromium
[1050:1050:0802/195930:ERROR:browser_main_loop.cc(283)] Gtk: Imposible encontrar el motor de temas en la ruta al _modulo: «adwaita»,
[1050:1050:0802/195930:ERROR:browser_main_loop.cc(283)] Gtk: Imposible encontrar el motor de temas en la ruta al _modulo: «adwaita»,
[1116:1116:0802/195934:ERROR:sandbox_linux.cc(343)] InitializeSandbox() called with multiple threads in process gpu-process.
Received signal 11 SEGV_MAPERR 000000000000
#0 0x55caea8799fe <unknown>
#1 0x55caea879dd9 <unknown>
#2 0x7f15cfcbbf00 <unknown>
r8: 000055caf21ea2b0 r9: fffffffd51a8ab75 r10: ffffe0de8e780635 r11: 00007f15be4d32cc
r12: 000055caf21ea2a8 r13: 000055caf21ea2b0 r14: 000055caf20e1a8c r15: 00007ffcaed8d110
di: 00001f23dfaed800 si: 0000000000000000 bp: 00001f23dfa93780 bx: 000055caf21ea2a8
dx: 0000000000000001 ax: 00001f23dfaed800 cx: 0000000000000000 sp: 00007ffcaed8c618
ip: 0000000000000000 efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000014
trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
[1050:1067:0802/195936:ERROR:object_proxy.cc(583)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
[1050:1067:0802/195936:ERROR:native_backend_kwallet_x.cc(439)] Error contacting kwalletd5 (isEnabled)
[1050:1067:0802/195936:ERROR:object_proxy.cc(583)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files
[1050:1067:0802/195936:ERROR:native_backend_kwallet_x.cc(408)] Error contacting klauncher to start kwalletd5
and with no sandbox this
chromium --no-sandbox
[10457:10457:0802/203001:ERROR:browser_main_loop.cc(231)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.
[10457:10457:0802/203001:ERROR:browser_main_loop.cc(283)] Gtk: Imposible encontrar el motor de temas en la ruta al _modulo: «adwaita»,
[10457:10457:0802/203001:ERROR:browser_main_loop.cc(283)] Gtk: Imposible encontrar el motor de temas en la ruta al _modulo: «adwaita»,
[10457:10468:0802/203002:ERROR:object_proxy.cc(583)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
[10457:10468:0802/203002:ERROR:native_backend_kwallet_x.cc(439)] Error contacting kwalletd5 (isEnabled)
[10457:10468:0802/203002:ERROR:object_proxy.cc(583)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files
[10457:10468:0802/203002:ERROR:native_backend_kwallet_x.cc(408)] Error contacting klauncher to start kwalletd5
[10524:10524:0802/203002:ERROR:sandbox_linux.cc(343)] InitializeSandbox() called with multiple threads in process gpu-process.
Received signal 11 SEGV_MAPERR 000000000000
#0 0x55b83ec049fe <unknown>
#1 0x55b83ec04dd9 <unknown>
#2 0x7fe556ea3f00 <unknown>
r8: 000055b8465752b0 r9: fffffffd523e09b0 r10: ffffe944037864f0 r11: 00007fe5456bb2cc
r12: 000055b8465752a8 r13: 000055b8465752b0 r14: 000055b84646ca8c r15: 00007ffe74e3a7f0
di: 000016b951248800 si: 0000000000000000 bp: 000016b9511ee780 bx: 000055b8465752a8
dx: 0000000000000001 ax: 000016b951248800 cx: 0000000000000000 sp: 00007ffe74e39cf8
ip: 0000000000000000 efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000014
trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
[10457:10457:0802/203200:ERROR:navigation_entry_screenshot_manager.cc(141)] Invalid entry with unique id: 38
[10457:10472:0802/203220:ERROR:simple_version_upgrade.cc(153)] File structure does not match the disk cache backend.
[10457:10472:0802/203220:ERROR:simple_backend_impl.cc(582)] Simple Cache Backend: wrong file structure on disk: /home/agm97/.cache/chromium/Default/Media Cache
[10457:10472:0802/203314:ERROR:simple_version_upgrade.cc(153)] File structure does not match the disk cache backend.
[10457:10472:0802/203314:ERROR:simple_backend_impl.cc(582)] Simple Cache Backend: wrong file structure on disk: /home/agm97/.config/chromium/Default/Storage/ext/knipolnnllmklapflnccelgolnpehhpl/def/Cache
[10457:10457:0802/203352:ERROR:navigation_entry_screenshot_manager.cc(141)] Invalid entry with unique id: 55
[10457:10473:0802/203617:ERROR:connection_factory_impl.cc(369)] Failed to connect to MCS endpoint with error -106
[10457:10653:0802/203635:ERROR:get_updates_processor.cc(250)] PostClientToServerMessage() failed during GetUpdates
[10457:10473:0802/203637:ERROR:connection_factory_impl.cc(369)] Failed to connect to MCS endpoint with error -21

with the regular chromium the sandbox of gpu fails but it didn't any more like in vaapi chromium which disable all gpu acceleration and not use the HW decode

agm28011997 commented on 2016-08-01 10:43

the repository is not trusted by pacman by your gpg key sam
edit: now is fixed, thanks

samcv commented on 2016-08-01 05:11

NOTE: I no longer have time to maintain this package. I am looking for a co-maintainer who would be willing to take over. I am willing to help you, but I no longer have the time to spend compiling and debugging.

The version in the repo/on AUR is outdated and has certificate issues due to some timer inside Chromium that was triggered after a certain length of time from the build. You could also try chromium-dev-vaapi from ArchCN http://repo.archlinuxcn.org/x86_64/


I am now providing a repository in case you don't want to build the entire package yourself. The repository can be used by adding this to you pacman.conf:
[samcv]
Server = https://cry.nu/repo/$arch/
SigLevel = Required

The package is signed with my PGP key, so you must add my key to pacman by doing:
pacman-key -r C3881D62
pacman-key --lsign-key C3881D62

If you have an Intel GPU you should use the chromium-vaapi package, but if you use Radeon/NVIDIA you should use another package in my repository called chromium-vaapi-other (If you want compile it yourself, please rename the package name in the PKGBUILD to chromium-vaapi-other and it will use the chromium-vaapi-other patch instead of the intel one). If someone can test it out and email me if it works along with the make and model of your video card that would be great. Contact information is samantham@posteo.net Thank you.

Other useful info:
Run "vainfo" in terminal to see what your card supports. Most don't support VP9 encoding which is used by default on YouTube and other sites. If so you may try this plugin https://chrome.google.com/webstore/detail/h264ify/aleakchihdccplidncghkekgioiakgal If your card doesn't support 60fps H.264, make sure to go into the options for the plugin and disable 60fps video.
To see if it is working properly, when a video starts playing you should see the following in your terminal:
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0

This message also shows up twice when chromium first opens when chromium checks if the computer supports VAAPI.