Package Details: ungoogled-chromium 131.0.6778.69-2

Git Clone URL: https://aur.archlinux.org/ungoogled-chromium.git (read-only, click to copy)
Package Base: ungoogled-chromium
Description: A lightweight approach to removing Google web service dependency
Upstream URL: https://github.com/ungoogled-software/ungoogled-chromium
Keywords: blink browser privacy web
Licenses: BSD-3-Clause
Conflicts: chromedriver, chromium
Provides: chromedriver, chromium
Submitter: ilikenwf
Maintainer: JstKddng (networkException)
Last Packager: networkException
Votes: 354
Popularity: 4.92
First Submitted: 2016-12-19 08:08 (UTC)
Last Updated: 2024-11-14 21:49 (UTC)

Required by (136)

Sources (14)

Pinned Comments

JstKddng commented on 2022-05-06 14:37 (UTC) (edited on 2022-06-27 13:48 (UTC) by JstKddng)

A new va-api patch for wayland has been added. Required flags for it to work are the following, thanks to @acidunit

--disable-features=UseChromeOSDirectVideoDecoder
--enable-hardware-overlays

JstKddng commented on 2020-07-19 06:34 (UTC)

You can get prebuilt binaries here:

https://github.com/ungoogled-software/ungoogled-chromium-archlinux#binary-downloads

seppia commented on 2018-12-12 21:34 (UTC)

Please do NOT flag this package as out of date in relation to official chromium releases.

This is NOT Google Chromium and new releases come after additional work of the ungoogled-chromium contributors, so they may not be ready, nor available for days or even weeks after a new version of official chromium is released.

Please refer to https://github.com/Eloston/ungoogled-chromium/tags for ungoogled-chromium releases. Use those and please flag this package as out of date only if a newer release is present there. I will update the PKGBUILD as soon as I can every time a new release comes out.

Thanks

Latest Comments

« First ‹ Previous 1 .. 45 46 47 48 49 50 51 52 53 54 55 .. 66 Next › Last »

bsdice commented on 2019-09-23 10:56 (UTC)

@MasterOne To add some more to the confusion, there is AUR chromium-vaapi{,-bin} and that includes the patch https://aur.archlinux.org/cgit/aur.git/tree/vaapi-fix.patch?h=chromium-vaapi which is needed on top of normal chromium. Eloston carried that patch for a while, but at one point has disabled it. No idea why. I don't want any Google phonehomium though.

My problem is, I want everything. Push the envelope security- and feature-wise of what is possible. I want my browser fully ungoogled for data privacy, I want working VAAPI hwdec acceleration, I need it up-to-date, I don't want to fight compilation errors, I want extensions managed by myself using chromexup (to lower risk of getting auto-updated extension malware installed in case an extension author's account is taken over). Also I want state of the art subpixel font rendering on non-retina displays with a bunch of infinality stuff from cairo-ubuntu thrown in, so websites look terrific. Better than Windows 10 at times I think.

Got all that working. Only thing missing imho is auto-update through AUR.

MasterOne commented on 2019-09-23 10:16 (UTC)

@bsdice @seppia @JstKddng

Interesting point about VA-API for Intel GPUs, I didn't know that that's not included in the official build.

If it's not intended or desired, to have that added to the official build by default, can it be managed by a flag before the build process, or would it make sense to have that variant as a separate AUR package (something like "ungoogled-chromium-intel")?

bsdice commented on 2019-09-23 09:56 (UTC)

Maybe "ungoogled-chromium" should be an AUR group effort, instead of single people making (and breaking) each their own packages. No idea how to implement this on AUR, though. At 100+ votes for this AUR alone that sounds not too unreasonable?

For what it's worth I am one of the https://github.com/jstkdng/ungoogled-chromium-archlinux users, because:

  • Kept up-to-date nicely to fight security holes. A conditio sine qua non for a web browser these days.

  • Consistently compiles for me, vs. this or upstream -archlinux AUR variant. Though I haven't checked the latters in a while (months).

  • Implements VAAPI for Intel GPU users to use video decoding hardware acceleration. On laptops playing Youtube this makes a huge difference in battery life. Needs package libva-intel-driver and #ignore-cpu-blacklist enabled in chrome://flags/ and you're good to go. On top I use compton with minimal config for anti-tearing on X11. Works great.

seppia commented on 2019-09-23 08:48 (UTC)

@MasterOne

No problem. Obviously I now updated in a hurry and missed this: https://github.com/ungoogled-software/ungoogled-chromium-archlinux/issues/30 so PKGBUILD is now broken and fails in the patching phase. Since it seems they've already solved the issues, I will wait for upstream to fix and then update this package again. So do not attempt to build now or just use the old version (just go back to the previous commit).

MasterOne commented on 2019-09-23 08:04 (UTC)

@seppia

Sorry, I did not want to imply that you don't keep this package up-to-date, I just found my way to ungoogled-chromium yesterday and it seemed confusing and not straight forward that there are three AUR packages for the same software.

I very much appreciate the maintenance of the official AUR package and I'm eagerly awaiting the update as I don't want to use a third-party binary.

So please keep up the good work :)

seppia commented on 2019-09-23 07:40 (UTC)

@MasterOne @JstKddng

I really don't understand why people keep saying I don't keep this package up to date. It has been less than two weeks since I last updated it and less than one since the new version came out. I may have taken my time in the past to update the package but I always have eventually. Every time I update I have to be sure the package is working with the new version, especially if it is a major (version) update and so even wait for the build to complete. It takes time and I can't spare it every day of the week, but I try to keep up. In addition to all of this you must know that it is not always that simple to update this PKGBUILD, since when a new ungoogled-chromium version comes out some changes may need to be performed on the ungoogled-chromium-archlinux patching scitps, which is the official repo you mentioned and which doesn't have a proper verioning and that creates the most confusion. And this changes are not always made proptply, so I usually wait for them since I don't have time to loose doing in advance some work that someone will eventually do better than me. If you are interested in my concerns and the decisions made to version that repo, please read the relative issue on github and feel free to add your contribution. I would just repeat here that this PKGBUILD is exactly the same as any offical PKGBUILD you would find on the ungoogled-chromium repos reguarding build operations. The modifications I make are some minor adjustments to make it compatible to AUR guidelines and work around the very confusing versioning scheme adopted upstream which is, again, really confusing to any user that just wants to install the software.

Anyway, about the AUR packages... bin is bin and if you are ok with it... go on and istall it. I honestly never look at the -archlinux one and I can't say what are the changes or the scopes of that PKGBUILD but if I must guess... the final package would not change a bit. I you are in doubt, trust the community, this package is the most voted and popular (which is more important the the number or votes) and this assures me that what I'm doing is actually ok to most of the userbase of this package, so, again, if in doubt, you could always trust them and the feedbacks.

MasterOne commented on 2019-09-23 06:33 (UTC)

@JstKddng

So you maintain an own copy of the PKGBUILD in your github repo but don't have it as a package in AUR although there already is an official github repo for ungoogled-chromium-archlinux, which in turn points to this AUR package (ungoogled-chromium) with the AUR packages ungoogled-chromium-bin and ungoogled-chromium-archlinux not being related.

Maybe it would be a good idea to get in touch with @seppia to figure out who wants to keep maintaining the official AUR package?

Or do you have any plans to create your own AUR package?

I just want to use ungoogled-chromium and the current (quite unclear) situation is not really user-friendly. A PKGBUILD on github is no good in my opinion, there really should be a properly maintained AUR package.

JstKddng commented on 2019-09-22 20:03 (UTC)

@MasterOne

you should obviously use my PKGBUILD: https://github.com/jstkdng/ungoogled-chromium-archlinux /t

now, jokes aside, ungoogled-chromium-archlinux was a response to this package not being updated (afaik), it is a copy of the PKGBUILD maintained by upstream ungoogled-chromium (the aur package hasn't been updated in a while though).

ungoogled-chromium-bin is separate from ungoogled-chromium and exists for those unable to compile this behemoth of a browser.

If you don't trust some shady fork, use the upstream PKGBUILD. https://github.com/ungoogled-software/ungoogled-chromium-archlinux

MasterOne commented on 2019-09-22 16:56 (UTC)

I'm a little confused as to which build to use, because there are now 3 in AUR:

  • ungoogled-chromium (76.0.3809.132-1)
  • ungoogled-chromium-bin (77.0.3865.90-1)
  • ungoogled-chromium-archlinux (76.0.3809.132-1)

Obviously only the binary version is currently up-to-date, but I don't want to use a prebuilt binary.

What's the deal with ungoogled-chromium vs ungoogled-chromium-archlinux?

@seppia are you not using ungoogled-chromium anymore? Can you please post an update to the latest version?

NullRoute commented on 2019-09-15 14:29 (UTC)

@ seppia - Please make proper ungoogled-chromium-bin with latest version. Thank you!

« First ‹ Previous 1 .. 45 46 47 48 49 50 51 52 53 54 55 .. 66 Next › Last »