Package Details: chromium-dev 57.0.2984.0-1

Git Clone URL: https://aur.archlinux.org/chromium-dev.git (read-only)
Package Base: chromium-dev
Description: The open-source project behind Google Chrome (Dev Channel)
Upstream URL: http://www.chromium.org
Licenses: BSD
Submitter: None
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 148
Popularity: 0.198252
First Submitted: 2010-05-17 09:04
Last Updated: 2017-01-18 19:44

Dependencies (35)

Required by (3)

Sources (10)

Latest Comments

sl1pkn07 commented on 2017-01-16 13:55

try to change the line #168 from gnome-keyring to libgnome-keyring

edit: pushed

yacuken commented on 2017-01-16 13:37

ERROR at //build/config/linux/pkg_config.gni:85:17: Script returned non-zero exit code.
pkgresult = exec_script(pkg_config_script, args, "value")
^----------
Current dir: /tmp/yaourt-tmp-yacuken/aur-chromium-dev/src/chromium-57.0.2979.0/out/Release/
Command: python -- /tmp/yaourt-tmp-yacuken/aur-chromium-dev/src/chromium-57.0.2979.0/build/config/linux/pkg-config.py gnome-keyring-1
Returned 1.
stderr:

Package gnome-keyring-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gnome-keyring-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gnome-keyring-1' found
Could not run pkg-config.

Add libgnome-keyring to makedepends (if use gnome-keyring). Thanks

sl1pkn07 commented on 2017-01-13 23:29

try build with internal jinja2,markupsafe and ply

in the next release i will use instead of system ones, because is only for make, not for run

LordAro commented on 2017-01-13 22:52

I'm getting a (several) compile failure around 10000 files in:

gen/v8/src/inspector/protocol/HeapProfiler.h:294:13: error: static assertion failed: property total should not be set yet
static_assert(!(STATE & TotalSet), "property total should not be set yet");


any ideas?

neeks commented on 2017-01-12 16:12

The build tag 57.0.2970.0 happened right at the beginning of real GTK3 integration support. If you use the default adwaita theme - specifically the light version - none of the GTK3 menu text gets styled and the text will appear white on a white background.

The next tagged version should have much better support, but until then you can update `~/.config/gtk-3.0/gtk.css` with the following to make the menu item's visible. This solution is just meant as temporary as the styling won't match up to the theme completely because this version's gtk3 css selector targeting isn't working great with 3.20+:

```

/* Seperator */
.menu .menuitem {
color: rgba(0,0,0.15);
}

/* Menu Item Text Color */
.menu .menuitem * {
color: rgba(0,0,0,.75);
}

/* Menu Item on hover, can't get the text to pick up a different color */
.menu .menuitem:hover {
background-color: #4a90d9;
}

/* Make the menu border more subtle */
.menu {
border: 1px solid rgba(0,0,0,.05);
}

```

You can follow Chromium's gtk3 progress here:
https://bugs.chromium.org/p/chromium/issues/detail?id=132847

joekiller commented on 2017-01-10 20:56

I got the error chromuim /usr/lib/libharfbuzz.so.0: undefined reference to `FT_Get_Var_Blend_Coordinates' and had to rebuild libharfbuzz per instructions I found at https://github.com/jaagr/polybar/issues/310#issuecomment-271353372 which states to rebuild:

$ abs extra/harfbuzz
$ cp -r /var/abs/extra/harfbuzz /tmp
$ # increase patch version in PKGBUILD
$ cd /tmp/harfbuzz
$ makepkg -si

lwin commented on 2017-01-07 14:17

Can confirm vaapi patch is broken for the current 57.0.2970.0-1 release:

patching file media/gpu/gpu_video_decode_accelerator_factory.cc
patching file media/gpu/gpu_video_decode_accelerator_factory.h
patching file media/gpu/ipc/service/BUILD.gn
patching file media/gpu/ipc/service/gpu_video_decode_accelerator.cc
patching file media/gpu/va_stub_header.fragment
patching file media/gpu/vaapi_video_decode_accelerator.cc
patching file media/gpu/vaapi_wrapper.cc
==> ERROR: A failure occurred in prepare().
Aborting...

sl1pkn07 commented on 2017-01-07 10:56

sounds vaapi patch is broken again ¬¬

OneObsession commented on 2017-01-07 10:54

I can not compile chromium because the build fails in prepare(). Patching the files seem to cause errors. Here is the output:

patching file chrome/browser/about_flags.cc
Hunk #1 FAILED at 976.
1 out of 1 hunk FAILED -- saving rejects to file chrome/browser/about_flags.cc.rej
patching file content/common/BUILD.gn
Hunk #2 succeeded at 568 (offset -2 lines).
patching file content/common/sandbox_linux/bpf_gpu_policy_linux.cc
patching file content/common/va_wayland.sigs
patching file content/gpu/BUILD.gn
patching file content/gpu/gpu_main.cc
Hunk #1 succeeded at 80 (offset 1 line).
Hunk #2 succeeded at 135 (offset 1 line).
patching file content/public/common/content_switches.cc
Hunk #1 succeeded at 1003 (offset 5 lines).
patching file content/public/common/content_switches.h
patching file gpu/config/software_rendering_list_json.cc
patching file media/BUILD.gn
Hunk #1 succeeded at 377 (offset 1 line).
Hunk #2 succeeded at 673 (offset 1 line).
patching file media/gpu/BUILD.gn
patching file media/gpu/gpu_video_decode_accelerator_factory.cc
patching file media/gpu/gpu_video_decode_accelerator_factory.h
patching file media/gpu/ipc/service/BUILD.gn
patching file media/gpu/ipc/service/gpu_video_decode_accelerator.cc
patching file media/gpu/va_stub_header.fragment
patching file media/gpu/vaapi_video_decode_accelerator.cc
patching file media/gpu/vaapi_wrapper.cc
==> FEHLER: Ein Fehler geschah in prepare().
Breche ab...

agm28011997 commented on 2016-12-28 22:29

with what graphics is useful the vaapi option? the other chromium with vaapi(samcv repo) gives me problems with amd.. it is only for intel graphics(i got this functioning in intel pc's only)? the only thing where I saw differences between the two graphics (apart of the performance of amd over intel) is the fail of sandbox on amd with gallium(= no hardware accel).. can it be the problem of the accel with that cards?

All comments