Un-Googled Chromium 'portable' - now at v112.0.5615.169 (includes manual updater from Fred...)

[mikewalsh]

Now with updater script.....courtesy of fredx181. Cheers, Fred!

-------------------------------------------------------

Afternoon, kiddiwinks. Uncle Mike's got something here that should please some of you....

Following an exchange of info & ideas with Mikeslr last night - and bearing in mind how much some of you distrust Big Brother! - here is a 'portable' build of Ungoogled Chromium.

Currently, this is at v112.0.5615.169.

This version will now run in ALL the "official" Puppies. Slacko Pups may not be able to run it, since I know Micko tends to use older versions of deps'n'stuff than the 'buntu Puppies......need feedback on this, guys.

Please be aware that since this is disconnected from Google completely, a lot of stuff you take for granted in the other 'clones' isn't functional here. You can go to the WebStore, and view any extension or theme you want.....but the 'Download/Install' button doesn't exist. So:-

• No extensions.

• No themes.

• You need to sign-in to every web-site manually, every time you visit - so something like KeePassXC will come in useful.

• You can't 'sync' with a Google a/c.

This build, in addition to including all the VAAPI, hardware acceleration stuff OOTB, also includes WideVine as standard. The developer, "Marmaduke", has built this along the same principles as most of the 'clone' devs.....against very much older dependencies, unlike 'vanilla' Chromium (which is always built against the very newest of everything).

An explanation for how to add extensions to Ungoogled_Chromium can be found here:-

viewtopic.php?p=18966#p18966
-----------------------------------------------

For anyone interested, and whenever practically possible, I will attempt to maintain as up-to-date a package as I can, here:-

https://mega.nz/folder/jXhVkYjB#Pz2plOQjETINrYv9coT7KQ

Instructions as always; d/l, unzip, locate where you want. Click to enter, click 'LAUNCH' to fire it up. (See 'explainer' script for information about these).

Posting from it in Fossapup64 now. Enjoy!

Mike.

[rockedge]

@mikewalsh
While watching Bundesliga this morning (6 hour difference) on TV I suddenly thought, "Gee I wonder if this will work in the new WeeDog I just made"......so here I am posting from it.
Fresh WeeDog64-Void
added a user "spot"
added the script "run-as-spot" in the $PATH (/root/my-applications/bin)
installed library "libatomic"
symlinked /usr/lib/libpciaccess.so.0.11.1 to /usr/lib/libpci.so.3
Modified by adding a line to Launch. Although I think I will try to give X sever permissions to user "spot". Or I could really be slick and fancy and start Xnest as DISPLAY=:1 and have LAUNCH start this ungoogled chrome in a Xnest instance.

Code: Select all

#!/bin/sh
xhost +
#
# Launcher for 'portable' Ungoogled-Chromium browser
#
HERE="$(dirname "$(readlink -f "$0")")"
chown -R spot:spot "$HERE/chromium"
#
"$HERE/chromium/chromium-pup" "$@"

[xenial]

@mike walsh.
I have heard it rumoured that the pepperflash will run until june 2021 although not certain if true,

[mikeslr]

I'm breaking the protocol of keeping posts to the subject of the thread for what I believe is a good reason. Rather than leaving many of us to covet thy neighbor's Web-browser, may I suggest if your Puppy's glibc isn't 2.28 or above or your programming skills aren't on rufwoof's level, the following combination will go a long way toward protecting your privacy:
1) Mike Walsh's portable-iron, https://forum.puppylinux.com/viewtopic.php?p=4865#p4865.
2) Ditching your current Search Engine for one suggested on this site, for the reasons given there, https://restoreprivacy.com/private-search-engine/

Edit March 17, 2021: Or perhaps even better if your computer has sufficient resources*, Mike Walsh's chrooted Iron, viewtopic.php?p=4748#p4748. I recently examined the default configuration settings of the chrooted Iron against Un-Googled Chromium and discovered very few differences.
=-=-=-=-=-=--
* The best way to find out is download the Chrooted-Iron.sfs, sfs-load it; and give it a test run.

[mikeslr]

Just a link to my post about metager search engine which I finally got working in Un-Googled Chromium, viewtopic.php?p=11128#p11128

I also managed to set Qwant as my Home Page. Somehow --don't ask-- after adding Swisscows as a search engine, when I type terms into the URL/Search box a drop-down appears offering to use it rather than metager.

[Marv]

@mikewalsh I added the libraries required for the slackware derivs (same additional 6 lib package used for SlimJet or regular chromium), spotified it (thanks rockedge), set it up with metager as the default search engine, imported my bookmarks, rolled a .desktop for it so I could get it in the LXDE panel easily, and it is really quite usable in my daily - the current LxPupSc64. First runs on the portables are always noticeably faster than on the SFS based browsers I usually use as they are already unpacked. The searches I have done (car brake parts, microswitches, and a wee dash of politics) have all been pretty good. I miss the extension that kept chromium from closing with tab closure, the adblocker and cookie-autodelete extensions, but all in all it's good. The god gurgle in my chromium based SlimJets was getting quietly more and more irksome behind the scene.

Thanks again for the nudge mikewalsh and for the launch as spot guidance rockedge,

[mikewalsh]

@Marv :-

You're very welcome, mate. Enjoy.

Mike.

[mikeslr]

Just a link to my post about the SwissCow Search engine. I like it more than metager. viewtopic.php?p=11223#p11223

[Marv]

A week or so now using Un-Googled Chromium alongside SlimJet 28.0.3.0 (regular flavor chromium based). I changed the launch scripts slightly so it would use the symlinked preconfigured spot directory on my data partition, changed the launch-as-spot script to use peebees system for changing ownership on downloaded files to root on exit, and added a line at the end of that script to delete its' cache files on exit as the ungoogled chromium doesn't have (that I could find) a way to limit cache size. Just my preferences. Runs well under LxPupSc64 on my i5 based laptops circa 2012. Opens quickly, nothing I've seen that it wouldn't open or play, and no 'AwSnaps'. SwissCow and metager both work well enough but I've used ddgd for so long that I'm hooked on its look. Trying to keep an open mind here.

Interestingly, gurgle doesn't only censor in its search engine. There are a few sites (political, not porn) that it refuses to open in the SlimJet, gives a 'page can't be found sorry that's all I can tell you', but switch to ungoogled and it immediately opens correctly. 'Safe browsing' is turned off in Slimjet for this test. I've seen it enough and reproduced it enough times so I'm sure it's real.

Cheers,

[mikeslr]

A week or so now using Un-Googled Chromium alongside SlimJet 28.0.3.0 (regular flavor chromium based). I changed the launch scripts slightly so it would use the symlinked preconfigured spot directory on my data partition, changed the launch-as-spot script to use peebees system for changing ownership on downloaded files to root on exit, and added a line at the end of that script to delete its' cache files on exit as the ungoogled chromium doesn't have (that I could find) a way to limit cache size. Just my preferences. Runs well under LxPupSc64 on my i5 based laptops circa 2012. Opens quickly, nothing I've seen that it wouldn't open or play, and no 'AwSnaps'. SwissCow and metager both work well enough but I've used ddgd for so long that I'm hooked on its look. Trying to keep an open mind here.

Interestingly, gurgle doesn't only censor in its search engine. There are a few sites (political, not porn) that it refuses to open in the SlimJet, gives a 'page can't be found sorry that's all I can tell you', but switch to ungoogled and it immediately opens correctly. 'Safe browsing' is turned off in Slimjet for this test. I've seen it enough and reproduced it enough times so I'm sure it's real.

Cheers,

Emphasis supplied.
Hi Marv,
For those of us who haven't memorized how could you post a link or, better yet, add a thread to this Browser & Internet Section showing how.
Along the same lines, your previous post mentioned " I added the libraries required for the slackware derivs (same additional 6 lib package used for SlimJet or regular chromium" could you make it clear which. One of the reasons I rarely use Slackos is the learning curve involved if I want to use applications which work OOTB under 'Ubuntus'.

[mikewalsh]

Just want to add that although peebee's system for moving files on shutdown to /root/Downloads with normal root:root permissions certainly works, it ONLY works for downloads, NOT uploads.....and the browser has to be closed before you can access them (unless you perform a manual move/chown.)

This is why I developed 'Spot2Root', because it's independent.....and you can move/change permissions of files in both directions, regardless of whether the browser is still running or not. Some may consider it a bit clunky, but it works for me, and probably others, too.

We all have different 'use-cases'. As Mike says, not all browsers that insist on "running-as-spot" actually respect those limitations. Experimentation usually highlights the culprits.

Mike.

[Marv]

@mikeslr
Here is the snippet I added to the end of the ungoogled chromium launch-as-spot script. The locations reflect my use of a common spot folder on my data partition, symlinked to /home/spot and to /root/spot. For a true 'portable' stick to the original addressing scheme in that script. The chromium browsers recreate the cache index without complaining on next use so I just blitz the works.

Code: Select all

#handles run-as-spot ala peebees system
chown -R root:root /root/spot/Downloads/*
/usr/lib/gtkdialog/box_splash -placement center -bg yellow -fg black -timeout 4 -text "REMINDER: Any downloads will have SPOT ownership but any items in /root/spot/Downloads have been changed to ROOT ownership" &

#deletes Cache files on exit as ungoogled chromium can't limit cache size
rm -rf /root/spot/.config/ungoogled_chromium/Default/Cache/*  

The library files I add for slackware derivs (thanks peebee) are in listed below, roughly 9Mb so too big to upload. I try to keep them fairly current, the set shown works fine with the version of ungoogled being discussed in the current LxPupSc. SlimJet needs a couple more but I haven't included those here.

libatk-bridge-2.0.so -> libatk-bridge-2.0.so.0.0.0
libatk-bridge-2.0.so.0 -> libatk-bridge-2.0.so.0.0.0
libatk-bridge-2.0.so.0.0.0
libatspi.so -> libatspi.so.0
libatspi.so.0 -> libatspi.so.0.0.1
libatspi.so.0.0.1
libgailutil-3.so -> libgailutil-3.so.0.0.0
libgailutil-3.so.0 -> libgailutil-3.so.0.0.0
libgailutil-3.so.0.0.0
libgdk-3.so -> libgdk-3.so.0.2200.29
libgdk-3.so.0 -> libgdk-3.so.0.2200.29
libgdk-3.so.0.2200.29
libgtk-3.so -> libgtk-3.so.0.2200.29
libgtk-3.so.0 -> libgtk-3.so.0.2200.29
libgtk-3.so.0.2200.29

@mikewalsh
I'm a simple cuss and mostly download so just changing the permissions on exit works in my case but I can appreciate the utility of the two way switcher.

Cheers,

[Marv]

Continuing to run un-googled chromium with the structure and added libraries above, mostly in the Slackware deriv LxPupSc64. It is now up to chromium version 87 (I'm running Version 87.0.4280.88), and requires two additional libraries for the slackware derivs

Code: Select all

libxkbcommon.so.0 -> libxkbcommon.so.0.0.0
libxkbcommon.so.0.0.0

They are present in the current fossapup64. I found the setup information here https://avoidthehack.com/how-to-install ... al-privacy useful. In the flags, there is also an option to set the browser not to close on closing the last tab, something I like. Loads like lightning with the version 87 and really quite serviceable for me on both the i5 based laptops and the Bay Trail based desktop. My longtime other browser, SlimJet, is now also up to chromium 87 with its' current version 29.0. I run it from SFS, both 32b and 64b, and the additional libs above are required for both in slackware derivs. Runs fine in my fossapup64 install (no adrv, custom ydrv with CUPS, LXDE, look'n'feel etc.) also. Fair amount of use in both 64b pups, no glitches at all seen.

[mikeslr]

Hi all,

I've run this under Fossapup64 and think, over all, it's a very nice web-browser. I was just going to post about one thing I didn't like. But reviewing the thread to see if it was already mentioned I discovered that Marv has posted about another and provided a work-around. viewtopic.php?p=11884#p11884 It's well worth spotlighting:

"Here is the snippet I added to the end of the ungoogled chromium launch-as-spot script.... Code:

#deletes Cache files on exit as ungoogled chromium can't limit cache size
rm -rf /root/spot/.config/ungoogled_chromium/Default/Cache/*
"
See Marv's post if you also want the files downloaded into /spot/Downloads to automatically have root privileges. I don't.

The one thing I didn't like is that I can find no method by which Un-Googled Chromium can accept extensions. Ordinarily Chromium extensions are obtained from Google's Webstore. Whether you access the Webstore via Menu>More Tools> Extensions>Webstore or web-browse into it no "button" to download/install extensions appears. Also absent is a "File >Open" modules. So even if you were able to download an extension, you couldn't modify UG-Chromium by opening it.

I can appreciate the objective of obtaining independence from Google-Chrome. But there could be other websites from which extensions might be obtained. And some people might like to employ addons such as privacy badger or those which mask the user's location.

Until I find some reason to do otherwise, Iron will remain by Chromium-based web-browser.

[mikeslr]

I went to edit my LAUNCH script to include Marv's argument. But decided first to see how much cache had accumulated. Well, running UG-C from /mnt/home/Pup-Apps my /root/spot was only a symlink to /home/spot and my /home/spot folder only contained a Download folder. LAUNCH calls /mnt/home/Pup-Apps/Ungoogled_Chromium-Fossa64/chromium/chromium-pup. And that script has the argument:

mkdir "$HERE/PROFILE" 2> /dev/null
chown -R spot:spot "$HERE/PROFILE"
#
run-as-spot "$HERE/chrome" --user-data-dir=$HERE/PROFILE --disable-infobars "$@"

So, it turns out that on my system cache is stored in .../PROFILE/Default/Cache. Despite that I had supposedly set Privacy to Clear everything, over 2500 items had been cached. Manually deleting them appeared to have no adverse effects. But checking Settings>Privacy again revealed 39 Mbs of Junk still remained. There is a More Tools>Clear Browsing Data listing on the drop-down menu. But there's no 'Customization' tool to directly add it to the Toolbar. It would be nice to be able to use something like the Click & Clean extension. But as I noted previously, there appears to be no method by which extensions can be used in UG-C.

I don't have the knowledge of how to edit the UG-C's scripts to delete /mnt/home.../PROFILE/Default/Cache files. I think it may be easier to follow Marv's lead to do so on Start-up; 'though I also think on Closing would be preferable.

Perhaps the easiest way to manage UG-C would be to revert to some variation of Mike's previous building technique: place UG-C in /root/spot or /home/spot. Or just move the entire portable folder there. Running a Puppy with Automatic Save removed (Save Session interval =0, Ask at Shut-down) the current session's accumulated Cache would simply not be preserved into another session. But, of course, during the session cache would accumulate in RAM.

[mikewalsh]

@mikeslr :-

Mike, I think the easiest thing would be to add Marv's code snippet from above to the very end of the 'chromium-pup' wrapper....after the exec line. Edit it to read

Code: Select all

#!/bin/sh
#
# Wrapper-script to launch Ungoogled-Chromium browser - Mike Walsh © Nov 2020 (with thanks to Fredx181...)
#
HERE="$(dirname "$(readlink -f "$0")")"
#
mkdir "$HERE/PROFILE" 2> /dev/null
chown -R spot:spot "$HERE/PROFILE"
#
run-as-spot "$HERE/chrome" --user-data-dir=$HERE/PROFILE --disable-infobars "$@"
#
#deletes Cache files on exit as ungoogled chromium can't limit cache size
rm -rf $HERE/PROFILE/Default/Cache/*

That should, I think, do what you want. Give it a try....see what happens. Can't hurt anything to experiment, especially if you try this with a copy of the portable first. The "$HERE" variable is referring to the contents of the 'chromium' directory, regardless of actual location; that's what the

Code: Select all

HERE="$(dirname "$(readlink -f "$0")")"

.....code snippet does, y'see. There's no NEED to include /mnt/home, etc, in the $PATH. (It's what enables much of this 'portable' tomfoolery to happen.)

Let us know what happens, please.

T'other Mike.

[mikeslr]

Thanks, Mike.
As soon as I read your post I went "Duh. I should have known that. ". I've always said "Languages are not my strong suit". And bash is a language.

Well, it almost worked as written. When it didn't I thought of all the complexities which might be involved. But it turned out to be something simple: "Profile" wasn't capitalized. The line which works reads:

rm -rf $HERE/PROFILE/Default/Cache/*

Which proves that secretaries and proof-writers aren't paid enough.

A point of interest. Still having the /PROFILE/Default/Cache folder open as I wrote this, the "cache" at startup of about 28 IIRC has by now grown to 163. Drop-down Menu>More Tools>Clear Browsing Data shows that 2.5 Mbs was occupied.

[mikewalsh]

D'oh! My 'bad'... Sorry about that.

(Good catch, BTW!)

I've edited the offending item in the above post. I KNOW what I did; I copied this manually from the post further back, rather than copy/paste, followed by editing to suit.....and wasn't QUITE paying attention to what I was doing at the time. As usual...

Mike.

[Marv]

Hi Mike,
Still using -and playing with- Un-Googled. FossaPup64 is my current playpup so... I have rolled Un-Googled, your full portable install, not my 'share-able' one, into my ydrv driven FossaPup64 install. MetaGer as the primary search engine. Took a bit of fiddling to get all of the defaults and setup into the ydrv, none with the Un-Googled part, but it is all working well . No save file or folder at all, no drives mounted. Cache deleted on browser exit with a box-splash line thrown in saying it's been done. The install uses the 95Mb stock FossaPup core SFS and kernel, has pcmanfm, can print, do email, editing, pdfs etc. and comes in at 275Mb total with the browser and CUPS being a fair chunk of that. Since I usually run a 256Mb savefile for each pup and either share browsers from the Data drive or SFS, I can't squeak too much about the size. Posting from that bundle now. Every boot a fresh start

Thanks again for your portable labors,

[mikewalsh]

Okey-doke, kiddiwinks. Since some of you seem to be quite enthused about this here browser (!!), here's an update for y'all:-

Ungoogled Chromium 87.0.4280.141

Parallel with the current Chrome release, but without the 'nosiness' that you all seem to hate so much...

A 'portable' build as always.....along with the usual instructions. D/l; unzip; place anywhere you want outside the 'save'. Click to enter, click 'LAUNCH' to fire it up.Couldn't be simpler.

Still only suitable for very new Pups.

@Marv :- I've included your cache-deletion 'tweak' for the wrapper script. I've put it at the end, so it'll clear itself on exit....okay?

-------------------------------------------------------

You can find it here, for anyone who's interested:-

https://drive.google.com/drive/folders/ ... sp=sharing

Posting from it now.....and just about to help myself to another episode of Star Trek 'Voyager'!

Enjoy.

Mike.

[Marv]

@mikewalsh : Having the cache cleanup onboard is good. It works either at the end of the chromium-pup script or at the end of the LAUNCH script as control is returned to the LAUNCH process when chromium-pup exits. I'm at 87.0.4280.88 now and haven't had any problems at all with it. I'll update when I add or subtract anything else from my ydrv. Posting from it in my 'save-less' FossaPup64.

Cheers,

[s243a]

Hello Mike,

I was just wondering if you've made a .desktop file for this browser, which I will of course have to modify based on wherever I put the portable.

[mikewalsh]

Hello Mike,

I was just wondering if you've made a .desktop file for this browser, which I will of course have to modify based on wherever I put the portable.

@s243a :-

I have indeed. You'll just need to modify the Exec script "uG-C" in /root/my-applications/bin, to point to wherever you run it from.

Attached below.

Mike.

[user1111]

Whilst on the other side of the fence .... Googled Chromium !!!

https://hackaday.com/2021/01/26/whats-t ... intainers/

A Open Source land grab to take Chromium into closed source and more likely see its demise (as starting 15th March 2021). Arch and Fedora are already considering pulling Chromium from their repos with others looking to follow that lead.

Hmm! Open Source Chromium, so many partake in the development, but under a BSD3 licence conditions where the 3 is that it 'requires written approval by Google'. Google waves goodbye to all of those free (no cost) developers to claim it as their own ... suckers! Oh and rip you off by offering 'free' products/services - that in reality the payment is 'yourself' ... suckers!

If the US doesn't jump on Google soon, others will, one way or another. A leaning tower of Googles own making.

[s243a]

Whilst on the other side of the fence .... Googled Chromium !!!

https://hackaday.com/2021/01/26/whats-t ... intainers/

A Open Source land grab to take Chromium into closed source and more likely see its demise (as starting 15th March 2021). Arch and Fedora are already considering pulling Chromium from their repos with others looking to follow that lead.

Hmm! Open Source Chromium, so many partake in the development, but under a BSD3 licence conditions where the 3 is that it 'requires written approval by Google'. Google waves goodbye to all of those free (no cost) developers to claim it as their own ... suckers! Oh and rip you off by offering 'free' products/services - that in reality the payment is 'yourself' ... suckers!

If the US doesn't jump on Google soon, others will, one way or another. A leaning tower of Googles own making.

Are you sure it's not just the ability to sync your data (e.g. bookmarks and aps) with Google cloud that is being removed?

https://www.google.com/amp/s/chromeunbo ... dent%3famp

I don't think that ungoogled chromium would have this feature anyway.

[vin]

Okey-doke, kiddiwinks. Since some of you seem to be quite enthused about this here browser (!!), here's an update for y'all:-

Ungoogled Chromium 87.0.4280.141

Parallel with the current Chrome release, but without the 'nosiness' that you all seem to hate so much...

A 'portable' build as always.....along with the usual instructions. D/l; unzip; place anywhere you want outside the 'save'. Click to enter, click 'LAUNCH' to fire it up.Couldn't be simpler.

Still only suitable for very new Pups.

@Marv :- I've included your cache-deletion 'tweak' for the wrapper script. I've put it at the end, so it'll clear itself on exit....okay?

-------------------------------------------------------

You can find it here, for anyone who's interested:-

https://drive.google.com/drive/folders/ ... sp=sharing

Posting from it now.....and just about to help myself to another episode of Star Trek 'Voyager'!

Enjoy.

Mike.

Hi !
I downloaded tar.gz file from the above url.
(Running Xenialpup64).
Unzipped to /opt folder.
Then fired LAUNCH file from PCManFM.
But it just flashes terminal and goes away.
Nothing happens next.

Maybe I am doing something wrong?
Thanks.

p.s. (I have normal 'Chrome' and also 'Iridium' installed on this xenialpup64. Can it mess it with ungoogled chromium?)

[mikewalsh]

@vin :-

Umm.... Quite a simple one, actually!

Bottom line; Xenialpup64 is too old to run UnGoogled Chromium. UGC requires a minimum glibc of 2.29; Xenialpup64 uses 2.23. That's why it won't run...

I may look into making a 'glibc-tweaked' version of UnGoogled Chromium (using Fossapup64's 2.31), so that folks with older Puppies can use it. Watchdog's 'tweak' technique has worked well in the past with Mozilla-based browsers, though I'm not certain whether this will work for the clones.

We'll see.

Mike.

[s243a]

@vin :-

Umm.... Quite a simple one, actually!

Bottom line; Xenialpup64 is too old to run UnGoogled Chromium. UGC requires a minimum glibc of 2.29; Xenialpup64 uses 2.23. That's why it won't run...

I may look into making a 'glibc-tweaked' version of UnGoogled Chromium (using Fossapup64's 2.31), so that folks with older Puppies can use it. Watchdog's 'tweak' technique has worked well in the past with Mozilla-based browsers, though I'm not certain whether this will work for the clones.

We'll see.

Mike.

@wiak , might have a way for you to upgrade the core libs Xenialpup64. I was able to do this with Puli/Xenial64 but I did something slightly different. I did this in a folder called "/cont" where the Xenail files were hardlinked to /cont and then I used his WDLGO_Focal64 firstrib_rootfs to replace the core libs in the /cont folder with those in WDLGO_Focal64 firstrib_rootfs (see post).

In my case, I modified the folder structure in /cont to match the proper debian/ubuntu multi-arch structure. This is fine is you only want to run Un-Googled Chromium in a container, sandbox or chroot. If this is what you want to do then I could create a hardlinked sfs from my scripts for xenial which you should be able to replace your main sfs with. However, if you just want to upgrade your main system, then you should keep the multi-arch symlink hack rather than modify the folder structure.

These changes could be done in the main sfs or they could be done as an add-on an as wiak is proposing where are A-drive is used as a layer that resides above the main sfs to override these core files. See post:
Released: WDLGO_UbuntuFocal64 mini-apt/dpkg experimental system

All this is experimental and a work in progress so if you try any of this you should back-up your save file or folder first.

[s243a]

I'm curious what are the requirements to run this as spot. I presume it works on Fossapup64 because the startup script uses "run-as-spot". However, this "run-as-spot" doesn't work on my Puli/Xenial64 that I've upgraded by replacing the core libs with those of the rootfs from ""WDLGO_UbuntuFocal64"" (see post).

When trying to use run-as-spot with this system I get the error:

Code: Select all

+ chroot /cont.QTAlT23 /opt/Ungoogled_Chromium-portable/chromium/chromium-pup
[30451:30451:0206/070922.968761:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.9oo91esource.qjz9zk/chromium/src/+/master/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
Trace/breakpoint trap

Maybe it would work this way if I install firejail? That said with my Puli/Xenial system it runs well as root using the --no-sandbox option. I have a sed script to modify the startup script to use the --no-standbox option (see post).

[wiak]

Whilst on the other side of the fence .... Googled Chromium !!!

https://hackaday.com/2021/01/26/whats-t ... intainers/

A Open Source land grab to take Chromium into closed source and more likely see its demise (as starting 15th March 2021). Arch and Fedora are already considering pulling Chromium from their repos with others looking to follow that lead.

Painful. I really really like the official Arch compilation of Chromium and use it, always, on my WeeDogLinux_Arch64 desktop.

Anyway, upgraded my WDL_Arch64 last night and note now have:

Chromium 88.0.4324.182 Arch Linux and glibc 2.33

The restricted Chromium takes place from Chromium 89 onwards so I've pinned this latest(last?) 88 version using /etc/pacman.conf. It will do for a long time for me, and I'll wait and see what happens thereafter.