Package Details: ungoogled-chromium 131.0.6778.85-1

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: 353
Popularity: 4.28
First Submitted: 2016-12-19 08:08 (UTC)
Last Updated: 2024-11-20 21:14 (UTC)

Dependencies (54)

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 .. 35 36 37 38 39 40 41 42 43 44 45 .. 66 Next › Last »

arch-dev commented on 2020-04-26 10:29 (UTC)

@seppia: This package is 4 releases behind the upstream. Can you please update it?

eita commented on 2020-04-25 08:44 (UTC)

Hi, I have a question why it build too long ? Thank you.

nathanielcwm commented on 2020-04-25 07:59 (UTC)

Maybe you should try using ccache?

Jojosh commented on 2020-04-12 04:16 (UTC)

@JstKddng After 12 hours of building I can confirm that this helped. Thank you.

JstKddng commented on 2020-04-10 20:12 (UTC)

@Jojosh

you have to recompile, say no to partial upgrades

Jojosh commented on 2020-04-10 19:13 (UTC)

The latest update of Jsoncpp broke Ungoogled Chromium for me. Regardless if it's this one or the bin version. It says that libjsoncpp.os.21 cannot be found. Downgrading to the older version of jsoncpp helped with that issue. I'm not sure if that is the right place to post this here as I'm new to this but it hope that it helps some people.

malcolm commented on 2020-04-07 20:31 (UTC)

you're not managing to keep this package up to date as you should. So, the right thing to do would be for someone else to take over the maintenance of that package.

Blind55 commented on 2020-03-11 15:08 (UTC)

@seppia: You make a good point, and I understand your sentiment. My only comment would be: since there is a simple workaround (a 'sed' one-liner), we can look for the issue while using an up-to-date package as well; the story would be different if the fix was difficult to implement.

seppia commented on 2020-03-11 12:44 (UTC)

Last weeks I've been trying to find out what could cause the linking failure issue, but with no success. I was hoping for someone of the ungoogled contributors, specifically for the archlinux version, to discover if the issue could be due to a particular way the linking is performed, since I have no time and resources to investigate it myself.

I must say I personally don't like this solution especially because I have always tried to keep this script as close as possible to the "official" ungoogled one, to avoid confusion and encourage contributions on github repo instead of modifications on various aur scripts. Of course this solves the issue, for now, and it isn't much of a big deal, but I would really like to encourage every one who can or simply hasn't thought about it, to join the discussion on github in order to find better solutions or at least determine some are just the only solutions feasible. Anyway I appreciate every contribution here, I'm just saying this because I would rather spend a little time investigating and waiting, if possible, to find a proper solution, as in arguably better for the most, then let this easily and rapidly become a patchwork whith little track of the changes and evatually difficulty to properly revert o modifiy further when needed (what instad github is better suiter for).

Please tell me if my concerns seems excessive to you and feel free, as I have always said, to contribute here in every way you might find helpful.

JstKddng commented on 2020-03-09 20:15 (UTC)

@jfk

I think so, if nothing happens in some days, I'll open an orphan request.

« First ‹ Previous 1 .. 35 36 37 38 39 40 41 42 43 44 45 .. 66 Next › Last »