It has landed in our upstream but upstream Debian has not yet updated. I intend to wait until then as we need to maintain history compatibility to a large degree with them. If anyone feels like trying to do this earlier then please do so but also please leave a comment in this issue if you are. I would just ask you make all patch updates in a single commit so we can easily revert it later when Debian finally does update.

clang-7: error: unknown argument: '-fsplit-lto-unit'
ninja: build stopped: subcommand failed.
make[1]: *** [debian/rules:140: override_dh_auto_build-arch] Error 1
make[1]: Leaving directory '/usr/src/sources/2019/browser/ung73/build/src'
make: *** [debian/rules:114: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

I've changed it to clang-8, then the compiling continues to run.

Using debian amd64, building fails with.......

make[1]: Entering directory '/home/berkley4/ungoogled-chromium/build/src'
./tools/gn/bootstrap/bootstrap.py --skip-generate-buildfiles -j2
ninja: Entering directory `/home/berkley4/ungoogled-chromium/build/src/out/Release/gn_build'
ninja: error: build.ninja:34: bad $-escape (literal $ must be written as $$)
  cflags = -resource-dir= -resource-dir=$(clang-8 --print-resource-dir) ...
                                        ^ near here

This looks like it's related to 462460d, as the following change to debian/rules allows the build to continue....

-export CXXFLAGS+=-resource-dir=$$($(CC) --print-resource-dir) \
+export CXXFLAGS+=-resource-dir=$(shell $(CC) --print-resource-dir) \

-export CPPFLAGS+=-resource-dir=$$($(CC) --print-resource-dir) \
+export CPPFLAGS+=-resource-dir=$(shell $(CC) --print-resource-dir) \

-export CFLAGS+=-resource-dir=$$($(CC) --print-resource-dir) \
+export CFLAGS+=-resource-dir=$(shell $(CC) --print-resource-dir) \

It's been 10 months since this branch was last updated. It doesn't appear to me that anyone has any interest in keeping this branch updated so it should probably be deleted.

I would attempt this myself but I'm not sure how to refresh the patches in a way that makes the patch validator happy. I'm stumped as to what it is complaining about.

It seems upstream still hasn't pushed any revisions to their chromium repository so I think I will try exploring the upgrade myself. Either way we may want to track the progress here.

Waiting for Debian to publish a new release.

The patch ungoogled-chromium/unknown-clang-warning-flags.patch removes -Wno-implicit-int-float-conversion, as its unknown for not-cutting-edge clang.

But this produces massive warning bloat, the log has now 9.5MB, before it was <3MB.
I suggest adding -Wno-implicit instead.
After all, we don't care about such warnings, thats chromium-team's duty.

Note: -Wno-implicit-float-conversion is also possible, but sadly not supported by clang 7.

I thought I would leave this as a reminder that we will need a branch for ubuntu_focal in the near future.

Would it be possible to explain this in the Wiki? Does it differ at all? Is there a reason to prefer one over the other? Do you collaborate?

bd859eb results in a build that crashes with SIGILL, i.e. Illegal operation. Will need to be investigated, possibly with a debug build.

(wrong repo)

Have you looked into this?
Is there something blocking this from happening?

Background info: ungoogled-chromium#17

74.0.3729.108-1 is now available in unstable.

EDIT: Currently waiting for Debian to publish changes to the git repo for their chromium package.

EDIT2: Will work on it when I can.

Hello
File name contains "focal2". What is this #2?

dpkg -I ungoogled-chromium_83.0.4103.116-1.focal2_amd64.deb:

Conflicts: libgl1-mesa-swx11, libnettle4, libsecret-1-0 (<< 0.18)
Breaks: chromium, chromium-browser, chromium-lwn4chrome (<= 1.0-2), chromium-tt-rss-notifier (<= 0.5.2-2)

If I try to execute I got:

Fatal error in , line 0

Failed to deserialize the V8 snapshot blob. This can mean that the snapshot blob file is corrupted or missing.

#FailureMessage Object: 0x7ffde33a28e0#0 0x559fc6920919 (/usr/lib/chromium/chromium+0x42c3918)
Received signal 4 ILL_ILLOPN 559fc920c682
#0 0x559fc6920919 (/usr/lib/chromium/chromium+0x42c3918)
r8: 0000000000000000 r9: 00007ffde33a1b60 r10: 0000000000000011 r11: 0000000000000000
r12: 0000003000000008 r13: 00007ffde33a2bf0 r14: 0000559fc385a7e5 r15: 00007ffde33a2ba0
di: 00007f6cab3984b0 si: 0000000000000000 bp: 00007ffde33a28d0 bx: 00007f6cab396780
dx: 0000000000000001 ax: 0000000000000000 cx: 0000000000000001 sp: 00007ffde33a28d0
ip: 0000559fc920c682 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000006 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated

Thank you.

Wait for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945920 to be fixed before releasing version 79.

I think this would be the best time to delete the branch as Focal will be official by then and there won't be much if any support left for Eoan by that point.

I've finished implementing the structure, workflow, and supporting code (in ungoogled-chromium) for this repo. Now, I'll need to merge upstream (i.e. Debian) changes for master and stretch.

It has landed in our upstream. How long will it take to land in Debian upstream now?

Ubuntu Disco Dingo has reached its EOL. I advise deleting it as there is no point in updating it anymore.

Ok, so I tried a build with the default master branch to see if there were any other build failures. Now I am getting this error:
ninja: error: '../../third_party/catapult/third_party/polymer/components/polymer/polymer-micro.html', needed by 'gen/content/browser/tracing/about_tracing.html', missing and no known rule to make it

I don't know what this file is but it is included in the file tree prior to starting the build so I don't know why it is missing. I did this test build in a Debian 10 container.

Any chance of updating to 78?

It doesn't seem like Debian's chromium package is going to be updated any time soon, it seems to be stuck on 76 and currently unmintained [1] [2] [3] [4] [5], so with the number of CVEs for the outdated 76 growing I wanted to give an up-to-date ungoogled-chromium a try, but can't get the deb packages to build. In fact, I didn't even get to the building part yet, I have spent 4 hours setting the build up, finding out that patches don't apply anymore, learning quilt and trying to fix the patches, just to get to:

$ ./debian/rules setup-debian
python3 -B debian/ungoogled-upstream/ungoogled-chromium/utils/patches.py merge -p debian/patches debian/ungoogled-upstream/ungoogled-chromium/patches
Traceback (most recent call last):
  File "debian/ungoogled-upstream/ungoogled-chromium/utils/patches.py", line 160, in <module>
    main()
  File "debian/ungoogled-upstream/ungoogled-chromium/utils/patches.py", line 156, in main
    args.callback(args)
  File "debian/ungoogled-upstream/ungoogled-chromium/utils/patches.py", line 117, in _merge_callback
    merge_patches(args.source, args.destination, args.prepend)
  File "debian/ungoogled-upstream/ungoogled-chromium/utils/patches.py", line 97, in merge_patches
    source_dir, patch_intersection))
FileExistsError: Patches from debian/ungoogled-upstream/ungoogled-chromium/patches have conflicting paths with other sources:
...

at which point I gave up.

It would probably be a good idea to have an official system for automated builds. Given that, this is one of the available options but it comes with some limitations.

1. It is only available to Ubuntu derivations.
2. It can only use packages from official repositories or an existing PPA.
3. It has an initial limit of 2GB for source and binary packages combined.

To setup a PPA and build packages, you essentially have to do these steps:

1. Create a Launchpad account
2. Create a new GPG key capable of signing and verifying packages
3. Upload the public key to the Ubuntu keyserver
4. Wait for the key to propagate
5. Add the key to the Lauchpad account created in step 1
6. Complete the verification process for the key addition
7. Create a new PPA
8. Configure the PPA settings; I would advise disabling builds for i386 at the very least.
9. Create a source package to upload; ensure it is signed with the GPG key you created earlier.
10. Upload the source package via dput. E.g., dput ppa:user/repo package.changes

Now how could this be done automatically? Most of the setup work is manual but the uploading of packages can be done automatically after that. To do so it would need access to a signing key associated with the account of the PPA. The rest is just a matter of scripting a series of commands that generate a source package to push out via dput.

I'm running Ubuntu 18.04 LTS, and I installed both ungoogled-chromium and keepassxc-browser from your PPA.
Keepass-XC was installed from the official PPA.

I'm getting the following error when clicking on the extension's icon:

Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings.

Trying to connect from the extension's settings won't work either. Integration is enabled for all browsers in KeepassXC's settings, and the extension works just fine in Firefox (there, it was installed from addons.mozilla.org).

One thing I noticed which could be the cause of the issue is that when using Firefox I can see that the process keepassxc-proxy is running, while when using Ungoogled Chromium it's not. I checked it because it was mentioned in the troubleshooting guide.

I'm reporting the issue here because that's what the PPA description said to do.

I find this error:

$ ./debian/rules setup-local-src
make: clang-10: No se encontró el programa
test -d ../download_cache || mkdir ../download_cache
python3 -B debian/ungoogled-upstream/ungoogled-chromium/utils/downloads.py retrieve -i debian/ungoogled-upstream/ungoogled-chromium/downloads.ini -c ../download_cache
INFO: Downloading "chromium" to "chromium-80.0.3987.162.tar.xz" ...
INFO: Downloading ../download_cache/chromium-80.0.3987.162.tar.xz ...
Progress: 100.0% of 796,961,972 B
INFO: Downloading hashes for "chromium"
INFO: Downloading ../download_cache/chromium-80.0.3987.162.tar.xz.hashes ...
Progress: 100.0% of 650 B
INFO: Verifying hashes for "chromium" ...
python3 -B debian/ungoogled-upstream/ungoogled-chromium/utils/downloads.py unpack -i debian/ungoogled-upstream/ungoogled-chromium/downloads.ini -c ../download_cache ./
INFO: Unpacking "chromium" to ./ ...

python3 -B debian/ungoogled-upstream/ungoogled-chromium/utils/prune_binaries.py ./ debian/ungoogled-upstream/ungoogled-chromium/pruning.list
./debian/scripts/remove_copyright_excluded
Traceback (most recent call last):
File "./debian/scripts/remove_copyright_excluded", line 89, in
main()
File "./debian/scripts/remove_copyright_excluded", line 55, in main
_remove_files(map(Path, regular_paths))
File "./debian/scripts/remove_copyright_excluded", line 38, in _remove_files
shutil.rmtree(filepath)
File "/usr/lib/python3.5/shutil.py", line 471, in rmtree
onerror(os.lstat, path, sys.exc_info())
File "/usr/lib/python3.5/shutil.py", line 469, in rmtree
orig_st = os.lstat(path)

TypeError: lstat: illegal type for path parameter
debian/rules:215: fallo en las instrucciones para el objetivo 'setup-local-src'
make: *** [setup-local-src] Error 1

I think it's time the delete the ubuntu_cosmic branch as it is now EOL.

Hello. I find this error:

make: clang-10: No se encontró el programa

python3 -B debian/ungoogled-upstream/ungoogled-chromium/utils/patches.py merge -p debian/patches debian/ungoogled-upstream/ungoogled-chromium/patches
File "debian/ungoogled-upstream/ungoogled-chromium/utils/patches.py", line 195
f'--patch-bin "{args.patch_bin}" is not a command or path to executable.')

SyntaxError: invalid syntax
debian/rules:210: fallo en las instrucciones para el objetivo 'setup-debian'
make: *** [setup-debian] Error 1

When I create JSON file in /usr/share/chromium/extensions/ as said here (External Extension Descriptor), browser from PPA says "Failed to load extension from: /usr/share/chromium/extensions/[extension-id].json. Manifest file is missing or unreadable", but the browser loads the extension normally. @braewoods, could you check it? When I use portable build, it's alright.

I setup a working directory, attempting to get a set of files I could upload to an automated build service. However I keep getting an error when the prune_binaries script is run. It fails to remove 18405 files which happens to be how many paths are specified in the list given to it. I think the issue is that the script is given the current working directory as the base instead of the extracted tarball directory so this pruning only works if the local source is extracted first. I suspect this is an oversight and not the intended result. I think changing ./ to use $(extract) instead in the debian/rules file should resolve the matter. Here are the commands I used to produce the issue from a debian 10 container:

git clone --recurse-submodules https://github.com/ungoogled-software/ungoogled-chromium-debian.git
git -C ungoogled-chromium-debian checkout --recurse-submodules 78.0.3904.108-2.bionic1 mkdir ungoogled-chromium
cp -r ungoogled-chromium-debian/debian ungoogled-chromium
cd ungoogled-chromium
debian/rules setup-debian
debian/rules get-orig-source

I would like to make a personal build with wayland ozone support so that I can remove x11/xorg packages from my system. What exactly do I need to change from the build instructions in README.md to do this?

Edit: If anyone cares to work on this or research it then please report your results here. Thanks.

I followed the build instructions but the build fails.
First I get some errors about missing files after I run ./debian/scripts/setup local-src
ungoogled_chromium1.txt

Then the build fails after dpkg-buildpackage -b -uc
ungoogled_chromium2.txt

The clang-10 tool is used in the debian/rules file, before it's eventually installed during the mk-build-deps process. It seems a bit chicken-and-egg. The software eventually ends up being installed, but a restart of the whole build process is required since unknown things were happening with the use of missing binaries. At the very least the README could use language to say restart again if the mk-build-deps adds more tools.

Following this process from the README:

# Final setup steps for debian/ directory
./debian/rules setup-debian

# Install remaining requirements to build Chromium
sudo mk-build-deps -i debian/control

This output is seen:

focal:/local/ungoogled-chromium/build/src root# ./debian/rules setup-debian
make: clang-10: Command not found

focal:/local/ungoogled-chromium/build/src/debian root# grep CC rules
export CC=clang-$(LLVM_VERSION)
RESOURCE_DIR:=$(shell $(CC) --print-resource-dir)

focal:/local/ungoogled-chromium/build/src root# sudo mk-build-deps -i debian/control
[...]
Unpacking ungoogled-chromium-build-deps (80.0.3987.162-1.sid1) ...
[...]
Correcting dependencies...Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following additional packages will be installed:
  clang-10 libc-ares2 libclang-common-10-dev libnode64 lld-10 nodejs
Suggested packages:
  clang-10-doc npm
Recommended packages:
  libomp-10-dev nodejs-doc
The following NEW packages will be installed:
  clang-10 libc-ares2 libclang-common-10-dev libnode64 lld-10 nodejs

It can be argued that folks who choose to compile instead of apt install would know to fix and repeat, but then projects like this are full of similar logged Issues where first time users encounter the same gotchas.

As an FYI, this is my entire build cut-and-paste which resulted in the above output:

setenv UGTAG 80.0.3987.162-1.sid1
mkdir -p /local/ungoogled-chromium
cd /local/ungoogled-chromium/
rm -rf ungoogled-chromium-* build/src
git clone --recurse-submodules https://github.com/ungoogled-software/ungoogled-chromium-debian.git
git -C ungoogled-chromium-debian checkout --recurse-submodules ${UGTAG}
mkdir -p build/src
cp -r ungoogled-chromium-debian/debian build/src/
cd build/src
perl -n -i.bak -e 'print unless m/^ lld-9,$/' debian/control
perl -n -i.bak -e 'print unless m/^ python,$/' debian/control
./debian/rules setup-debian
sudo mk-build-deps -i debian/control
rm ungoogled-chromium-build-deps_*.deb
./debian/rules setup-local-src
setenv PATH "/root/bin:/usr/local/bin:/bin:/usr/ccs/bin:/etc:/usr/etc:/usr/bin:/usr/local/X11/bin:/usr/bin/X11:/usr/proc/bin:/usr/local/sbin:/sbin:/usr/local/go/bin:/root/go/bin:/usr/local/etc:/usr/sbin"
touch /local/ungoogled-chromium/compile_`date +%Y-%m-%d-%H:%m:%S`_start
dpkg-buildpackage -b -uc
touch /local/ungoogled-chromium/compile_`date +%Y-%m-%d-%H:%m:%S`_stop
cd ..
rm *-dbgsym_*
apt -y purge chromium-browser chromium-browser-l10n ungoogled-chromium-driver
apt -y purge ungoogled-chromium ungoogled-chromium-build-deps ungoogled-chromium-common
apt -y purge ungoogled-chromium-sandbox ungoogled-chromium-shell
dpkg -i \
    ungoogled-chromium-common_${UGTAG}_amd64.deb \
    ungoogled-chromium-driver_${UGTAG}_amd64.deb \
    ungoogled-chromium-sandbox_${UGTAG}_amd64.deb \
    ungoogled-chromium-shell_${UGTAG}_amd64.deb \
    ungoogled-chromium_${UGTAG}_amd64.deb

I've been getting APNG flicker in Chromium for a little while. Warnings match those as discussed in https://bugs.chromium.org/p/chromium/issues/detail?id=752403#c10

Unfortunately, it seems Debian also patches their libpng with APNG support.

The crbug referenced an Arch issue, but there seems to be no solution to using Chromium with libpng patched with APNG support.

@braewoods Should we use the bundled libpng library instead?

I have discovered a difference between how the two modes setup the source tree. The end result is that I get build failures such as this when I try to build from a source tree created by get-orig-source:
ninja: error: '../../third_party/breakpad/breakpad/src/common/convert_UTF.c', needed by 'obj/third_party/breakpad/client/convert_UTF.o', missing and no known rule to make it

And why does this occur? It occurs because the copyright file's excluded files includes wildcard patterns which are honored by the get-orig-source but not by setup-local-src so setup-local-src has the required files but get-orig-source does not. I traced this back to a difference in how debian/scripts/remove_copyright_excluded works. Apparently it ignores wildcard file patterns.

What can be done resolve this inconsistency? Thanks.

Hi,

https://software.opensuse.org/download/package?package=ungoogled-chromium&project=home:ungoogled_chromium

This line sudo wget -nv https://download.opensuse.org/repositories/home:ungoogled_chromium/Ubuntu_Focal/Release.key -O "/etc/apt/trusted.gpg.d/home:ungoogled_chromium.asc" does not correctly add the key and on subsequently trying to add PPA to the sources the partially installed ungoogled_chromium key causes failure to import the PPA signing key.

steve@steve-VirtualBox:~$ sudo wget -nv https://download.opensuse.org/repositories/home:ungoogled_chromium/Ubuntu_Focal/Release.key -O "/etc/apt/trusted.gpg.d/home:ungoogled_chromium.asc"
2020-06-28 05:22:11 URL:https://download.opensuse.org/repositories/home:/ungoogled_chromium/Ubuntu_Focal/Release.key [1126/1126] -> "/etc/apt/trusted.gpg.d/home:ungoogled_chromium.asc" [1]
steve@steve-VirtualBox:~$ apt update
Hit:1 http://download.opensuse.org/repositories/home:/ungoogled_chromium/Ubuntu_Focal  InRelease
Hit:2 http://dl.google.com/linux/chrome/deb stable InRelease                   
Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease                        
Hit:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease                
Hit:5 http://archive.ubuntu.com/ubuntu focal InRelease                         
Hit:6 http://archive.ubuntu.com/ubuntu focal-updates InRelease                 
Hit:7 http://archive.ubuntu.com/ubuntu focal-backports InRelease               
Hit:8 http://security.ubuntu.com/ubuntu bionic-security InRelease              
Hit:9 http://security.ubuntu.com/ubuntu focal-security InRelease    
Ign:10 http://packages.linuxmint.com ulyana InRelease
Hit:11 http://archive.canonical.com/ubuntu focal InRelease
Hit:12 http://packages.linuxmint.com ulyana Release
Reading package lists... Done
Building dependency tree       
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
steve@steve-VirtualBox:~$ sudo add-apt-repository ppa:phoerious/keepassxc
You are about to add the following PPA:
 KeePassXC Password Manager (official upstream PPA)

https://keepassxc.org/download/
 More info: https://launchpad.net/~phoerious/+archive/ubuntu/keepassxc
Press Enter to continue or Ctrl+C to cancel

Executing: /tmp/apt-key-gpghome.96c7RW0TWW/gpg.1.sh --keyserver hkps://keyserver.ubuntu.com:443 --recv-keys D89C66D0E31FEA2874EBD20561922AB60068FCD6
gpg: key 61922AB60068FCD6: public key "Launchpad PPA for Janek Bevendorff" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: invalid key resource URL '/tmp/apt-key-gpghome.96c7RW0TWW/home:ungoogled_chromium.asc.gpg'
gpg: keyblock resource '(null)': General error
gpg: key 7721F63BD38B4796: 2 signatures not checked due to missing keys
gpg: key 02456C79B2FD48BF: 1 signature not checked due to a missing key
gpg: key A6616109451BBBF2: 12 signatures not checked due to missing keys
gpg: key 3B4FE6ACC0B21F32: 3 signatures not checked due to missing keys
gpg: key D94AA3F0EFE21092: 3 signatures not checked due to missing keys
gpg: key C8CAB6595FDFF622: 2 signatures not checked due to missing keys
gpg: key 871920D1991BC93C: 1 signature not checked due to a missing key
gpg: Total number processed: 8
gpg:       skipped new keys: 8
steve@steve-VirtualBox:~$ apt update
[sudo] password for steve:               
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease                
Get:3 http://ppa.launchpad.net/phoerious/keepassxc/ubuntu focal InRelease [18.0 kB]
Hit:4 http://archive.ubuntu.com/ubuntu focal InRelease                         
Hit:5 http://archive.ubuntu.com/ubuntu focal-updates InRelease                 
Hit:6 http://dl.google.com/linux/chrome/deb stable InRelease                   
Hit:7 http://archive.ubuntu.com/ubuntu focal-backports InRelease               
Hit:8 http://archive.canonical.com/ubuntu focal InRelease                      
Hit:9 http://security.ubuntu.com/ubuntu bionic-security InRelease              
Hit:10 http://security.ubuntu.com/ubuntu focal-security InRelease              
Ign:11 http://packages.linuxmint.com ulyana InRelease                          
Hit:12 http://download.opensuse.org/repositories/home:/ungoogled_chromium/Ubuntu_Focal  InRelease
Hit:13 http://packages.linuxmint.com ulyana Release
Err:3 http://ppa.launchpad.net/phoerious/keepassxc/ubuntu focal InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 61922AB60068FCD6
Reading package lists... Done
W: GPG error: http://ppa.launchpad.net/phoerious/keepassxc/ubuntu focal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 61922AB60068FCD6
E: The repository 'http://ppa.launchpad.net/phoerious/keepassxc/ubuntu focal InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.

The solution - on adding the ungoogled-chromium repo the key can be correctly added with this alternative command

Focal / Mint 20
wget -nv https://download.opensuse.org/repositories/home:ungoogled_chromium/Ubuntu_Focal/Release.key -O /tmp/home:ungoogled_chromium.asc; sudo apt-key add /tmp/home:ungoogled_chromium.asc

Bionic / Mint 19.x
wget -nv https://download.opensuse.org/repositories/home:ungoogled_chromium/Ubuntu_Bionic/Release.key -O /tmp/home:ungoogled_chromium.asc; sudo apt-key add /tmp/home:ungoogled_chromium.asc

Please consider updating the instructions at https://software.opensuse.org/download/package?package=ungoogled-chromium&project=home:ungoogled_chromium

Cheers

83.0.4103.116-1 frequently crashes. This is fixed in 83.0.4103.116-2.

Quite often latest Ungoogled Chromium get closed unexpectedly. It's hard to say why, nothing interesting in logs at first sight.
Is it possible to install previous version of Ungoogled Chromium somehow? I can't find previous release.

$ apt-cache madison ungoogled-chromium

ungoogled-chromium | 83.0.4103.116-1.focal1 | http://download.opensuse.org/repositories/home:/ungoogled_chromium/Ubuntu_Focal  Packages

Is it possible to leave at least few versions in official repository? Thanks.

I was pondering this possibility while looking through the work that went into buster. It may be possible even though bionic is older.

Need to convert the ungoogled_debian_minimal branch to the new format.

Version: 73.0.3683.103-1.buster1

VA-API VP9 decoding does not seem to be working under X11. A black area appears where the video should be shown, and it won't play. No errors are printed out to stdout/stderr.

Here's a test site: https://base-n.de/webm/VP9%20Sample.html
YouTube videos also have the same problem.

The workaround is to disable chrome://flags/#disable-accelerated-video-decode so that software rendering is used.

Wayland works, but I don't think hardware acceleration is being used because it logs an error from vaapi_wrapper.cc that vaInitialize failed: unknown libva error.

Hardware: Intel HD 620 and UHD 630

@riyad Do you have this issue in your Ubuntu Cosmic build?

@xsmile Does VA-API acceleration work for you under Arch Linux?

I have followed instructions and tried five times and same warnings comes every time. What I've done wrong?

In file included from ../../chrome/browser/media/router/discovery/mdns/dns_sd_device_lister.cc:5:
../../chrome/browser/media/router/discovery/mdns/dns_sd_device_lister.h:51:24: warning: private field 'delegate_' is not used [-Wunused-private-field]
DnsSdDelegate* const delegate_;
^
1 warning generated.
[18753/21809] CXX obj/chrome/browser/ui/ui/ui_jumbo_50.o
In file included from gen/chrome/browser/ui/ui_jumbo_50.cc:16:
In file included from ./../../chrome/browser/ui/sync/one_click_signin_links_delegate_impl.cc:5:
../../chrome/browser/ui/sync/one_click_signin_links_delegate_impl.h:25:18: warning: private field 'browser_' is not used [-Wunused-private-field]
Browser* const browser_;
^
1 warning generated.
[18770/21809] CXX obj/chrome/browser/ui/ui/ui_jumbo_52.o
In file included from gen/chrome/browser/ui/ui_jumbo_52.cc:13:
In file included from ./../../chrome/browser/ui/webui/signin/inline_login_handler_impl.cc:5:
../../chrome/browser/ui/webui/signin/inline_login_handler_impl.h:186:8: warning: private field 'confirm_untrusted_signin_' is not used [-Wunused-private-field]
bool confirm_untrusted_signin_;
^
1 warning generated.
[18908/21809] CXX obj/chrome/common/common/google_url_loader_throttle.o
In file included from ../../chrome/common/google_url_loader_throttle.cc:5:
../../chrome/common/google_url_loader_throttle.h:39:8: warning: private field 'is_off_the_record_' is not used [-Wunused-private-field]
bool is_off_the_record_;
^
1 warning generated.
[21494/21809] CXX obj/v8/v8_base_without_compiler/v8_base_without_compiler_jumbo_27.o
In file included from gen/v8/v8_base_without_compiler_jumbo_27.cc:10:
./../../v8/src/objects/js-list-format.cc:336:22: warning: implicit conversion loses integer precision: 'std::vector::size_type' (aka 'unsigned long') to 'int' [-Wshorten-64-to-32]
int length = items.size();
~~~~~~ ~~~~~~^~~~~~
1 warning generated.

dpkg-genbuildinfo --build=binary
dpkg-genchanges --build=binary >../ungoogled-chromium_78.0.3904.97-2.buster1_amd64.changes
dpkg-genchanges: info: binary-only upload (no source code included)
dpkg-source --after-build .

dpkg-buildpackage: info: binary-only upload (no source included)

While building ungoogled-chromium-debian and running the command 'sudo mk-build-deps -i debian/control', I ran into the following error:

Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) ungoogled-chromium-build-deps:amd64 < 83.0.4103.116-1.sid3 @iU mK Nb Ib >
Broken ungoogled-chromium-build-deps:amd64 Depends on python:amd64 < none @rc H >
  Considering python:amd64 1 as a solution to ungoogled-chromium-build-deps:amd64 -2
  Removing ungoogled-chromium-build-deps:amd64 rather than change python:amd64
Done

The code proceeds to uninstall ungoogled-chromium-build-deps, breaking the installation of requirements to build Chromium.

I am not entirely sure if this is a problem for everyone (I am on the latest Debian Sid updates), but I easily fixed this problem by configuring debian/controls and changing python -> python2

Hello. I use a MX Linux based on Debian 9 (Stretch) and my version of git is 2.11.0.

In the installation step:
git -C ungoogled-chromium-debian checkout --recurse-submodules TAG_OR_BRANCH_HERE

i need change for:
git -C ungoogled-chromium-debian checkout -b TAG_OR_BRANCH_HERE

Since you fixed the bug with remove_copyright_excluded, I have been examining how close the resulting source code trees created by setup-local-src and get-orig-source are. They are nearly identical now and I am going to see if I can make them 100% identical.

If this is successful I think I can modify get-orig-source to replace the more expensive method of removing the copyright exclusions with remove_copyright_excluded. This would make the differences between the two much smaller which should reduce the incidence of bugs that are specific to one or the other and also make get-orig-source faster.

On Ubuntu 18.04 (current LTS) the available version of libharfbuzz-dev is 1.7.2.

But in this line, the dependency is explicitly set to libharfbuzz-dev (>= 2.1.1)

Is there a reason why this is particularly set to >= 2.1.1 ?

What about removing debian/disable/tracing.patch from debian/series/?
Background info: [1] [2].
opinions?

I found a significant bottleneck in the get-orig-source target of the debian/rules makefile. The line that reads while read line; do rm -rf $line; done < $(removed) is slow due to executing the rm command once for every file to be removed. This can be greatly sped up by doing more work for each execution of the rm command by utilizing xargs. I replaced this line with xargs rm -rf < $(removed) and I saw that the total time taken was reduced by approximately 7 minutes. I think this could be worth incorporating as it should be a drop-in replacement. Thanks.

Update to ungoogled-chromium 73.

We should change the branch that tracks upstream (Debian) be a new branch called debian_sid that targets Debian sid. This will better match the target Debian version for upstream's master branch, and makes it easier separate changes specific to stable Debian versions from testing or unstable.

The current Debian stable branch debian_buster should track this new debian_sid branch. Also, Ubuntu versions should target either a specific Debian branch or debian_sid, depending on when they were released and/or the versions of their packages.