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: 352
Popularity: 4.21
First Submitted: 2016-12-19 08:08 (UTC)
Last Updated: 2024-11-20 21:14 (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 .. 8 9 10 11 12 13 14 15 16 17 18 .. 66 Next › Last »

followait commented on 2022-02-05 04:52 (UTC)

What about making PKGBUILD reenterable?

Relih commented on 2022-01-27 13:27 (UTC)

@JstKddng No worries I just got it fixed myself, I removed the application of chromium-93-ffmpeg-4.4.patch and unbundle-ffmpeg-av_stream_get_first_dts.patch and had the built go through fine.

JstKddng commented on 2022-01-27 12:48 (UTC)

@Relih

You are gonna have to wait until ffmpeg 5 is released on extra.

Relih commented on 2022-01-26 22:43 (UTC)

I am getting the same error as lunainvictum, sadly symlinking the old .so versions doesn't work and chromium is too complex for me to understand where the actual error is.

lunainvictum commented on 2022-01-25 15:49 (UTC)

That's weird, have you tried forcing a repo sync? I updated fine to 97.0.4692.99-2 >from the obs repo.

Yep, even with pacman -Syyu first :)

But seems it is like @networkException said. Because on the Repo like here described https://github.com/ungoogled-software/ungoogled-chromium-archlinux#binary-downloads

it uses the repo where X.71-2 is only available.

I switch actualy to https://github.com/jstkdng/aur. I misunderstood first something, thought first that the first one is your repo :-)

Installed the latest one, but still didnt run anyway because of ffmpeg 5.0.

But that is my problem, because im temporarly using Artix to try out.

networkException commented on 2022-01-25 15:42 (UTC)

The OBS repo at https://build.opensuse.org/package/show/home:ungoogled_chromium/ungoogled-chromium-arch is stuck on 97.0.4692.71-2 right now unfortionately. https://build.opensuse.org/package/show/home:justkidding:arch/ungoogled-chromium is up to date

JstKddng commented on 2022-01-25 15:37 (UTC)

That's weird, have you tried forcing a repo sync? I updated fine to 97.0.4692.99-2 from the obs repo.

lunainvictum commented on 2022-01-25 15:22 (UTC)

Yes, ffmpeg is the problem. On my System is ffmpeg 5.0 already installed.

And what i found out: If i install from your repo, it wants to install

Pakete (1) ungoogled-chromium-97.0.4692.71-2

But like you know, 97.0.4692.99-2 is actual release :)

JstKddng commented on 2022-01-25 15:19 (UTC)

@lunainvictum

not sure about x264 but once ffmpeg 5 is released this package will need an update. And yes, the signature format error is on the OBS side, nothing I can do about it. You could disable signature checking on your pacman.conf to get rid of the error but I haven't tested that.

lunainvictum commented on 2022-01-25 14:50 (UTC) (edited on 2022-01-25 15:07 (UTC) by lunainvictum)

@JstKddng

Yes. Tried multiple times. I think it is because of new x264 or ffmpeg update i got? dont know. Installed from your Repo.

Little OT: Is it normal that if using your repo, to get everytime a warning/error about a wrong signature format? Anyhow to disable that?

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 66 Next › Last »