You are not logged in.

#1 Re: Building » compiling chromium 75.0.3770.80 and ungoogled chromium » 2019-06-22 21:34:36

yeah, sorry about that.  since you said the gofile host wasn't working i used the second one from the search.  i have several layers of adblocking so i didn't know anonfile was that bad.  sorry again.

like i've said before, users shouldn't put blind trust in random binaries.  my files should have passed the md5 check at least if you compiled your own pkg and compared hashes.  i totally understand, though.

i won't post again.  if you don't mind, please delete this account.  thank you.

#2 Re: Building » compiling chromium 75.0.3770.80 and ungoogled chromium » 2019-06-21 18:01:18

updated to 75.0.3770.100 with same PKGBUILD

ungoogled chromium 75.0.3770.100 archlinux32 pkg
md5 3a77e487f7b9f28c9642f8aa75924ba4

ungoogled chromium 75.0.3770.100 32bit portable AppImage
md5 4123c2e1844f55aee2c7dda6014d7877

#3 Re: Building » compiling chromium 75.0.3770.80 and ungoogled chromium » 2019-06-15 00:04:30

I checked the links and it seems they work for me, what i see though is for some reason the dots from the filenames got removed, so if you download them you would need to rename them.  sorry i used that file locker but honestly i used the first one i found with no ads and that allowed me to upload without an account.

here's the PKGBUILD and flags i used for ungoogled.  if you want to submit the changes to the AUR, please feel free to do so.  i don't do accounts and i basically modified the one available there.


# Derived from PKGBUILD for Inox
# Original Inox PKGBUILD authors:
# Maintainer: Michael Egger <>
# Contributor: Evangelos Foutras <>
# Contributor: Pierre Schmitz <>
# Contributor: Jan "heftig" Steffens <>
# Contributor: Daniel J Griffiths <>

# Commit or tag for the upstream ungoogled-chromium repo
_ungoogled_revision=$(curl -sL${_ungoogled_version}/revision.txt)
pkgdesc="A lightweight approach to removing Google web service dependency"
depends=('gtk3' 'nss' 'alsa-lib' 'xdg-utils' 'libxss' 'libcups' 'libgcrypt'
         'ttf-font' 'systemd' 'dbus' 'libpulse' 'pciutils' 'json-glib' 'libva'
         'desktop-file-utils' 'hicolor-icon-theme' 'jsoncpp' 'openjpeg2')
makedepends=('python' 'python2' 'gperf' 'yasm' 'mesa' 'ninja' 'git'
             'clang' 'lld' 'gn' 'llvm' 'quilt')
optdepends=('pepper-flash: support for Flash content'
            'kdialog: needed for file dialogs in KDE'
            'gnome-keyring: for storing passwords in GNOME keyring'
            'kwallet: for storing passwords in KWallet'
            'libva-intel-driver: for hardware video acceleration with Intel GPUs'
            'libva-mesa-driver: for hardware video acceleration with AMD/ATI GPUs'
            'libva-vdpau-driver: for hardware video acceleration with NVIDIA GPUs')
sha256sums=($(curl -sL${_chromium_version}.tar.xz.hashes | grep sha256 | cut -d ' ' -f3)

# Possible replacements are listed in build/linux/unbundle/
# Keys are the names in the above script; values are the dependencies in Arch
declare -gA _system_libs=(
  #[libpng]=libpng            #

prepare() {

  cd "$srcdir/chromium-${_chromium_version}"

  msg2 'Pruning binaries'
  python "$_utils/" ./ "$_ungoogled_repo/pruning.list"
  msg2 'Applying patches'
  python "$_utils/" apply ./ "$_ungoogled_repo/patches" "$_ungoogled_archlinux_repo/patches"
  msg2 'Applying domain substitution'
  python "$_utils/" apply -r "$_ungoogled_repo/domain_regex.list" -f "$_ungoogled_repo/domain_substitution.list" -c domainsubcache.tar.gz ./

  # Force script incompatible with Python 3 to use /usr/bin/python2
  sed -i '1s|python$|&2|' third_party/dom_distiller_js/protoc_plugins/*.py

  # Remove bundled libraries for which we will use the system copies; this
  # *should* do what the script does, with the
  # added benefit of not having to list all the remaining libraries
  local _lib
  for _lib in ${_unwanted_bundled_libs[@]}; do
    find -type f -path "*third_party/$_lib/*" \
      \! -path "*third_party/$_lib/chromium/*" \
      \! -path "*third_party/$_lib/google/*" \
      \! -path './base/third_party/icu/*' \
      \! -path './third_party/crashpad/crashpad/third_party/zlib/zlib_crashpad.h' \
      \! -path './third_party/pdfium/third_party/freetype/include/pstables.h' \
      \! -path './third_party/yasm/' \
      \! -regex '.*\.\(gn\|gni\|isolate\)' \

  python2 build/linux/unbundle/ \
    --system-libraries "${!_system_libs[@]}"

build() {

  make -C chromium-launcher-$_launcher_ver

  cd "$srcdir/chromium-${_chromium_version}"

  if check_buildoption ccache y; then
    # Avoid falling back to preprocessor mode when sources contain time macros
    export CCACHE_SLOPPINESS=time_macros

  export CC=clang
  export CXX=clang++
  export AR=llvm-ar
  export NM=llvm-nm

  mkdir -p out/Default

  # Assemble GN flags
  cat "../../" >> "out/Default/"

  # Facilitate deterministic builds (taken from build/config/compiler/
  CFLAGS+='   -Wno-builtin-macro-redefined'
  CXXFLAGS+=' -Wno-builtin-macro-redefined'
  CPPFLAGS+=' -D__DATE__=  -D__TIME__=  -D__TIMESTAMP__='

  msg2 'Configuring Chromium'
  gn gen out/Default --script-executable=/usr/bin/python2 --fail-on-unused-args
  msg2 'Building Chromium'
  ninja -C out/Default chrome chrome_sandbox chromedriver

package() {
  cd chromium-launcher-$_launcher_ver
  make PREFIX=/usr DESTDIR="$pkgdir" install
  install -Dm644 LICENSE \

  cd "$srcdir/chromium-${_chromium_version}"

  install -D out/Default/chrome "$pkgdir/usr/lib/chromium/chromium"
  install -Dm4755 out/Default/chrome_sandbox "$pkgdir/usr/lib/chromium/chrome-sandbox"
  ln -s /usr/lib/chromium/chromedriver "$pkgdir/usr/bin/chromedriver"

  install -Dm644 chrome/installer/linux/common/desktop.template \
  install -Dm644 chrome/app/resources/ \
  sed -i \
    -e "s/@@MENUNAME@@/Chromium/g" \
    -e "s/@@PACKAGE@@/chromium/g" \
    -e "s/@@USR_BIN_SYMLINK_NAME@@/chromium/g" \
    "$pkgdir/usr/share/applications/chromium.desktop" \

  cp \
    out/Default/{chrome_{100,200}_percent,resources}.pak \
    out/Default/{*.bin,chromedriver} \
  install -Dm644 -t "$pkgdir/usr/lib/chromium/locales" out/Default/locales/*.pak

  if [[ -z ${_system_libs[icu]+set} ]]; then
    cp out/Default/icudtl.dat "$pkgdir/usr/lib/chromium/"

  for size in 22 24 48 64 128 256; do
    install -Dm644 "chrome/app/theme/chromium/product_logo_$size.png" \

  for size in 16 32; do
    install -Dm644 "chrome/app/theme/default_100_percent/chromium/product_logo_$size.png" \

  install -Dm644 LICENSE "$pkgdir/usr/share/licenses/chromium/LICENSE"

# vim:set ts=2 sw=2 et:





the most problematic flag was the jumbo thingy but with enough ram it's not an issue.  i used a different file for the flags instead of the provided one so i could test stuff. 

if you want to make the pkg put these two files in one folder and run

makepkg -s

#4 Re: Building » compiling chromium 75.0.3770.80 and ungoogled chromium » 2019-06-13 19:56:05

here's the pkg for ungoogled chromium

gofile link deleted
md5 dee016ca68af2f0d5dc9cfb23c155d71

install with

sudo pacman -U ungoogled-chromium-75.0.3770.80-1-any.pkg.tar.xz

all credit to the respective devs.  if there's interest i can post the PKGBUILD and the flags i use to be able to compile this on archlinux32.

now to redo the post that got lost yesterday, in resume if you use the PKGBUILD from the 64bit archlinux and modify the architecture from 'x86_64' to 'any', the package should compile, as long as your computer is capable of doing it. it took me weeks of testing to be able to compile mostly because of how old my hardware is, and every failed attempt would take days of compilation.

my desktop is a pentium 4, and my netbook is an atom n270, both with 2gb of ram, so it's virtually impossible to compile chromium with such low memory.  even using a few gigs swap wouldn't help.  one test i cancelled after 5 days of compiling with no end in sight.

to be able to compile i got access to a newer laptop with an i7-7700hq and 16gb of ram.  first i tried to run an archlinux32 portable install in a usb memory.  to be able to use all the ram you need to use the pae kernel, but there's some bug in 5.1 so it wouldn't even boot.  compiling custom kernels (4.14 worked) and using an hdd with ntfs as filesystem didn't help since just extracting files took hours and the compilation still failed.

what worked for me is to install archlinux32 in a virtual machine asigning 6 threads and 12gb of ram, 64gb ssd space, and for good measure 8gb in swap.  still the compilation takes about 5 hours, compared to a normal archlinux 64bits where it took 20 minutes for the same package.

#5 Building » compiling chromium 75.0.3770.80 and ungoogled chromium » 2019-06-13 08:38:47

Replies: 7


I wrote a long ass post but when i clicked on "Submit" I got logged out and the post was lost. 

I managed to compile chromium on archlinux32

gofile link deleted

install with

sudo pacman -U chromium-75.0.3770.80-1-any.pkg.tar.xz

Of course it would be best to wait for the official package from our devs, though if you compile your own the md5 checksum should match.

Currently I'm compiling again ungoogled chromium since i got an error when building the pkg, but managed to create the portable version

gofile link delete
md5 37c905ead6b03e607fdceb9b770ff078

run with


you'll probably need to install some dependencies for the portable version.  in my case
jsoncpp re2 snappy libxslt minizip

also please read up some considerations for ungoogled, like if you use extensions you need to install/update them manually.  tomorrow i'll post the pkg for ungoogled, and will rewrite the post that got deleted explaining my experience compiling chromium on 32 bits.

if the files are against forum rules, please delete.

#6 Re: Servers & Networking » Broadcom BCM4312 not working » 2019-05-30 02:23:14

i got the same card.  run:

iw dev

on terminal and see how your interface is called (probably "wlan0"). install wicd-gtk and enable/start the wicd service with

sudo systemctl enable wicd.service
sudo systemctl start wicd.service

not sure wht your DE is, but you need to autostart the wicd-gtk interface.  to open manually, in terminal run:

wicd-client --tray

go to preferences and be sure your network interface is correct (wlan0 or whatever you got from iw dev). accept and refresh.  to set your wifi password click on properties and fill your network settings (ip, dns), your password goes on "key".  accept and click connect.

side note:  for me the b43 driver is a bit unstable and sometimes the connection drops.  using the broadcom-wl-dkms i have stable connection, but is a bit tricky to get it working at first.  if b43 works fine for you, don't worry about this.

#7 Re: Installation » Installation of pentium4 optimized packages » 2019-05-29 23:14:21

hello.  i've been thinking a lot about this. wouldn't be easier to assume the default i686 arch as the pentium4 (sse2 supporting cpu)? and then rename the non sse2 as i686-no-sse2 or something?  pentium4 is not an architecture, and not all sse2 supporting cpus are pentium4,  also isn't pentium an intel trademark?

you see posts in the forum complaining some packages from AUR can't be build or issues when pentium4 is not a supported arch.  i think people with a non sse2 cpu would find it easier to switch to "i686-no-sse2" and most people simply stay with "i686" as defaul 32 bit architecture.  i would guess there are a lot more users in need of sse2 to justify i686 as default option.

don't know, though.  just my 2c

#8 Re: Pacman / Pacman Upgrades » [Solved] empathy, gnome-control-center not work, icu packet... » 2019-05-07 19:28:00

radli wrote:

aur/chromium-dev 75.0.3770.15-1 (157) (0,46)
    The open-source project behind Google Chrome (Dev Channel)

not really.  most AUR packages are also 64 bits only.  just to see, i tried.  even modified the pkgbuild file and tried to feed 32 bit dependencies.  no dice.

#9 Re: Pacman / Pacman Upgrades » [Solved] empathy, gnome-control-center not work, icu packet... » 2019-05-07 01:59:55


for people having trouble with chromium 73 and icu 64, i got kind of a temp solution.  although downgrading icu is possible, like others have said it would cause more issues, and with the archive dead as roll back alternative, it's not easier.

now if you upgraded to the pentium4 arch, you need to go back to i686.  my "solution" is to install a precompiled chromium 74.  so with your system updated up and running on the i686 arch, look up for the manjaro archive /x32-testing/extra/ and download the file chromium-74.0.3729.131-0.2-i686.pkg.tar.xz  (about 49MB)

you can install the file manually by doing

sudo pacman -U chromium-74.0.3729.131-0.2-i686.pkg.tar.xz

things to consider: you would be installing a file from another project, though it will work, it will not have any archlinux32 patches or anything to do with archlinux32.  you are trusting the source you are downloading the package from, so if you are trusting the archlinux32 devs,  i don't think there would be a problem trusting manjaro's.  this is a "hack" solution.  if you currently moved to the pentium4 arch, you won't be able to install this as it would be the wrong architecture.

i'm currently running it without issues.  once the package is compiled by our wonderful devs, you could remove this one and get the one from the official archlinux32 repos, and maybe move to the pentium4 arch.

of course every other package depending on icu 63 is still broken.  you could try hunting down the updated precompiled package from manjaro but i havent tried.

good luck!

#10 Re: Installation » Installation of pentium4 optimized packages » 2019-05-04 19:14:53

Hi all.

the last update seems to have caused a ruckus.   i read a few threads but looks like everything is being worked on so big thanks to deep42thought and andreas_baumann.  not sure if you got the message I tried to send within the forum system, so please consider lifting the registration restriction on the irc channel.

at my end, I upgraded my netbook with the pentium4 optimized packages, and almost everything seems to be working aside of a couple of things. lightdm, lightdm-gtk-greeter, openbox all working, but honestly i don't see much of an improvement.  i know this hardware is old and we are lucky it is still somewhat useful.  my netbook has a n270 and 2GB ram, so 2% improvement would be welcome.

currently broken is chromium 73 as it depends on icu 63, so i guess most things depending on icu 63 are broken as the package upgraded to icu 64.  i'm currently using a firefox nightly binary i got directly from mozilla, but in this hardware it sucks.  hopefully chromium gets updated soon.  i would love to be able to compile chromium on my own and even apply ungoogle patches but simply it's impossible with 32 bit hardware.  current chromium snapshot is at version 76.

mpv is broken too, but the one in testing fixed the issue.  qtox is broken.

commenting on @levi's post, video streaming in this hardware is hell.  anything above 360p stutters, 480p would be pushing it but depends on bitrate.  as said before, only chromium seems to work best for this.  firefox even stutters at 160p on twitch.  grabbing links and playing on mpv or external players isn't always possible, and audio/video desynchronization is expected when 720p and up.

anyway, as always, thanks for your hard work.

#11 Re: Pacman / Pacman Upgrades » [solved] pacman -Syu" my System will not start again - great crash » 2019-01-20 19:02:57

today's update of lightdm to 1:1.28.0-1.3 fixed the issue with gtk-greeter.  thanks everybody.

my username is random because I value privacy.  i don't have an online presence,  but try to help whenever possible.  cheers.

#12 Re: Pacman / Pacman Upgrades » [solved] pacman -Syu" my System will not start again - great crash » 2019-01-19 18:56:46

There's been reports as far as december about systemd 240 causing issues with some applications, including lightdm.  In my netbook, lightdm with the gtk greeter results in a coredump, and the webkit2 greeter simply doesn't work for some reason.

lightdm with the webkit2 greeter is 20 packages and 228MB that I consider just way too much resources just for the DM. Regardless after installing and starting it, journalctl simply says " Failed to start Light Display Manager" so i assume it's still a bug on lightdm no matter the greeter, and systemd changing how things work and introducing new bugs.

I tried slim and also didn't work. Haven't tried sddm.  xdm works but at that point i just prefer no display manager and use xinit to get to desktop.

For people struggling with this, if you can't arch-chroot from a live usb, or don't know and have a black screen with the cursor blinking:

1. crt + alt + f2 to switch to a different tty. (because systemd will try to launch lightdm after every crash, you may need to time it right and repeatedly)
2. log in as root
3. stop lightdm service with "systemctl stop lightdm.service".  (you will probably have to constantly switch to this tty with ctr+alt+f2 and enter the letters one by one until lightdm is stopped)
4. once lightdm.service is stopped, disable it with "systemctl disable lightdm.service" so it won't crash loop again next reboot
5. depending on your desktop environment you can get to desktop by manually starting X.  In my case I use openbox so the command is "startx /bin/openbox-session".  You could use xinit to auto launch X after you log in.

Not the prettiest solution but this could help to someone.   When the bugs are hopefully fixed, you need to enable the service with "systemctl enable lightdm.service" and that's it.

#13 Re: Pacman / Pacman Upgrades » [solved] pacman -Syu" my System will not start again - great crash » 2019-01-18 19:05:16

andreas_baumann wrote:

What kind of login manager are you using: lightdm and gtk-greeter are currently broken. Use another greeter or sddm or slim..

Does the machine gome up in non-GUI mode (nomodeset in kernel command line)?


Been tracking this for a few hours now after wasting a day or so reinstalling a system.  Seems it is systemd 240 that is the problem.  I've read downgrading it to 239 "fixes" the lightdm/gtk-greeter issue.  Haven't tried, though, as I disabled the lightdm service and launched a simple startx session to get to desktop.

#14 Re: Pacman / Pacman Upgrades » Xorg stopped working after updating yesterday » 2018-10-06 01:11:59

np.  yeah i wasn't aware of it until i needed it two weeks ago.  I usually install 'downgrade' from the aur and start doing some digging one package at a time.  it is time consuming, though, so this alternative is like a nuke.  i did restore the current servers and commented out the archive link to keep it just in need of another roll back.  i had to switch to noveau when the proprietary nvidia driver got deprecated (it had xorg as dependency, and as it got updated, the nvidia couldn't satisfy dependencies). nouveau works for me, so meh... this is just an internet browsing machine for the most part.


again thank you for your hard work.


#15 Re: Pacman / Pacman Upgrades » Xorg stopped working after updating yesterday » 2018-10-04 21:20:40

Hello.  Like all the others I'd like to thank every dev working hard to keep Arch alive in 32 bits.

I had the same issue that after a full system update my pc couldn't boot anymore and just a blinking underscore on a black screen.  The installation is pretty standard with lightdm and xfce, on a Pentium 4 with a Geforce fx-5200.  Like another poster said, the problem started 20 something of september when Linux got bumped to 4.18.6.  Last time something similar had happened it was a bug on xorg, which was fixed on the next update.  Thinking it happened again, I tried to update from testing, tried to downgrade xorg, thought maybe it was a bug on linux, but no dice.  Disabling the lightdm service I was able to boot into the system but any attempt to launch an xorg session would give a coredump.  I don't use the intel integrated graphics, so i have installed the nouveau driver.  I tried to reinstall the driver and everything I could think of, but the problem persisted.

The only solution I managed at the time, and after reading some posts on the arch forums, was to roll the entire system back to the point before the linux update.  For anyone in need of such fix, this is what I did:

- remove all packages in cache

sudo pacman -Scc

- modify /etc/pacman.d/mirrorlist, and comment out the current servers but adding the last valid date from the archives (september 7th in my case)

sudo nano /etc/pacman.d/mirrorlist

#Server =$arch/$repo
#Server =$arch/$repo
Server =$arch/$repo

- make a full system upgrade

sudo pacman -Syyuu

This last command will downgrade every package up to the date from the archive.  After this my system would boot without issues.  When you want to update normally, you must edit the mirrorlist file again and uncomment the servers and delete the archive entry.

While trying to identify the problematic package, I updated independently everything i thought could be the culprit, but taking a hint from the previous poster (thanks jeverett!) mesa was guilty.  The logs pointed to an 'Illegal instruction' by Tracking this down, after updating mesa from the testing repo everything is well once more.

Updating to mesa 18.2.1-1.0 the problem is gone, and doing a full system upgrade as of the time of this post, everything is fixed.

Again thank you devs and collaborators.

Board footer

Powered by FluxBB