@thefallenrat
Are you compiling the new version Eloston bumped? It is working for me. I'm using a different pkgbuild though, check it out in my github repo:
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: | 1.38 |
First Submitted: | 2016-12-19 08:08 (UTC) |
Last Updated: | 2025-04-25 11:19 (UTC) |
« First ‹ Previous 1 .. 48 49 50 51 52 53 54 55 56 57 58 .. 67 Next › Last »
@thefallenrat
Are you compiling the new version Eloston bumped? It is working for me. I'm using a different pkgbuild though, check it out in my github repo:
EDIT EDIT: The build works with added is_official_build=false flag
EDIT: Nvm the build failed
@seppia, please update your _archver variable to the latest commit of the project as it contains some removal of flags that will surely fix crashes on startup. See below for details: https://github.com/ungoogled-software/ungoogled-chromium-archlinux/issues/22
Also, please don't use $pkgver reference in your ungoogled_repo variable. Cause I find it annoying that when I try to bump pkgrel, I have to switch all $pkgver reference to $_rev
Can confirm, the new vaapi patch from ungoogled-chromium is causing the crashes. The vaapi patch from chromium-vaapi works as expected. The only option would be to remove the vaapi patch and recompile. That's why I haven't released a new version for my repo.
Edit:
nope, still the same problem, Illegal instruction. We'll have to wait for Eloston now.
no binary build?
@bsdice That is different from what I have seen. It is suspected the bug is related to some patches, not chromium itself. The bug is being tracked here.
@sorice1123 I am getting:
[28336.619583] traps: ThreadPoolSingl[5638] trap invalid opcode ip:564223eb10d7 sp:7f7df77fcda0 error:0 in chromium[56422167b000+695e000]
Is that the same problem? Any link to a public bug-report? The Chromium bug tracker is not fully transparent with some similar bugs.
Be aware that there is a bug in current version that will cause a crash on startup. Better wait for an update.
well this was a total waste of my time, 4 hours of compiling, and it won't run after a successful compile/install ....
Cant build again.
Aborts again at jumbo_3. Tried already -j 3 -l 3 for ninja...
Obsolete version.
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
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