Package Details: chromium-gtk2 62.0.3202.62-1

Git Clone URL: (read-only)
Package Base: chromium-gtk2
Description: A web browser built for speed, simplicity, and security (GTK2 version)
Upstream URL:
Keywords: browser web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: WorMzy
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 3
Popularity: 0.346341
First Submitted: 2017-06-07 19:09
Last Updated: 2017-10-18 18:14

Dependencies (37)

Required by (29)

Sources (8)

Latest Comments

WorMzy commented on 2017-10-18 14:43

Great! Thanks for testing this and letting me know. I'll push out an updated PKGBUILD shortly.

lahwaacz commented on 2017-10-18 14:21

I was able to build version 62 with this patch ;-)

lahwaacz commented on 2017-10-18 12:21

As far as I understand the code, kUseGtkNavButtonLayoutManager makes a difference only with GTK3. Based on the error message I'm trying to build with '#include "nav_button_layout_manager.h"' added to chrome/browser/ui/libgtkui/gtk_ui.h so we'll see...

WorMzy commented on 2017-10-18 11:43

Yeah, I *think* this is related to so I'm trying a build with kUseGtkNavButtonLayoutManager disabled.

lahwaacz commented on 2017-10-18 11:36

It seems that the ca40720.diff patch is not needed anymore since version 62, but the build still fails with different error:

In file included from /usr/include/c++/7.2.0/memory:80:0,
from ../../chrome/browser/ui/libgtkui/gtk_ui.h:9,
from ../../chrome/browser/ui/libgtkui/
/usr/include/c++/7.2.0/bits/unique_ptr.h: In instantiation of ‘void std::default_delete<_Tp>::operator()(_Tp*) const [with _Tp = libgtkui::NavButtonLayoutManager]’:
/usr/include/c++/7.2.0/bits/unique_ptr.h:268:17: required from ‘std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp = libgtkui::NavButtonLayoutManager; _Dp = std::default_delete<libgtkui::NavButtonLayoutManager>]’
../../chrome/browser/ui/libgtkui/ required from here
/usr/include/c++/7.2.0/bits/unique_ptr.h:76:22: error: invalid application of ‘sizeof’ to incomplete type ‘libgtkui::NavButtonLayoutManager’

frankspace commented on 2017-08-17 13:20

For what it's worth, the entire reason I'm using Chromium now instead of Firefox is because Firefox stopped supporting ALSA entirely and now only uses Pulseaudio. Which, to me, is a dealbreaker. Chromium may not compile without libpulse installed (I haven't actually tested that), but I also use ALSA exclusively. Performing "ldd /usr/bin/chromium" reveals no direct dependency on any pulse library, so I have no idea whether libpulse could safely be moved to makedepends and then uninstalled after compilation, but it might be worth an experiment! In any event, the point is, I'm not persuaded you do in fact need to look for a different browser.

Klyachkivsky commented on 2017-08-08 17:07

OK, sorry . I'll go look for another browser on gtk2 and without pulse :)

WorMzy commented on 2017-08-08 13:39

No idea. Look into the source code if you're interested in that. If it turns out that chromium doesn't build without pulseaudio support, then you could try using apulse as a workaround.

Klyachkivsky commented on 2017-08-08 00:07

How to disable pulse ? I do not use pulseaudio . Only alsa .

WorMzy commented on 2017-07-28 09:01

Unfortunately, the patch does not apply to the current version of, and I'd need to pull in half a dozen other patches to bring the file up to date enough for it to apply, and even then I have no guarantees that the patches I've pulled in don't rely on other changes to the source code that I haven't pulled in.

I'm going to stick with the current situation, with the single patch reversed, and hope that the next release of chromium includes the fix you linked to.

If anyone wants to read up on the changes that didn't make it into 60.0.3112.78, and make a patch that either pulls in the necessary changes, or else rewrite the newest patch to apply directly onto 60.0.3112.78, please feel free. If you come up with a working solution I'll be happy to update the package with what you come up with.

All comments