Puppy Linux Discussion Forum

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.

@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.

#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,

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

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.

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.

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.

@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

#!/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

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.

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.

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.

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,

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.

@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,

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 wrote: ↑Tue Feb 02, 2021 12:42 pm

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.

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.

rufwoof wrote: ↑Tue Feb 02, 2021 6:14 pm

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.

mikewalsh wrote: ↑Sun Jan 17, 2021 8:48 pm

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?)

@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.

mikewalsh wrote: ↑Thu Feb 04, 2021 1:38 pm

@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.

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:

+ 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).

rufwoof wrote: ↑Tue Feb 02, 2021 6:14 pm

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.

Now then, gang...

Following some of the advice from this thread of peebee's:-

viewtopic.php?f=90&p=18951#p18951

.....where he quotes from Alien Bob's blog, I've figured out the easiest way to at least get your "must-have" extensions into Ungoogled Chromium.

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

First, download the .crx file from below (remove the fake ".gz" after you've d/l'ed it). It couldn't get much newer, since this was updated less than 10 days ago. To install it, follow these instructions:-

• In Ungoogled Chromium, open a new tab & enter

  Code: Select all

  chrome://extensions

  .....and hit Enter. You'll be presented with a blank page (naturally). Top right, temporarily toggle the 'Developer Mode' button to the 'On' position.

• Open A ROX window at the location of the CRX file. Drag the "Get Crx" extension on to the Extensions page, and drop it; you'll be asked if you want to install it. Allow it to do so, since this extension makes everything else possible.

• Now, go to

  Code: Select all

  https://chrome.google.com/webstore/category/extensions

  .....and browse the Web Store to find the extensions you want. When you find them, go to the extension's Store page; right-click, and from the context menu select "Get CRX of this extension". The browser will download it for you.

• To install your extensions, it's basically rinse & repeat; as above, drag the CRX files onto the Extensions page, followed by allowing the installation to proceed. (You can also use the same procedure if you have a favourite theme you like to use.)

• When you've finished, toggle the 'Developer Mode' button back to the 'Off' position; it only needs to be 'On' for installation.

Result? Your favourite extensions, without involving Google in the process (aside from having to visit the WebStore to find the things).....and still no connections to Google's 'nosy' stuff. I know it's a bit long-winded.....but it only needs doing once.

Hope that helps some of you.

Mike.

Very nice! That worked. I like to add Dark Reader and the Power Saver theme. So far the most aesthetically pleasing browser I have is Libre Wolf with Dark Reader and the Black Code theme. I haven't been able to download anything with Un-googled Chromium though. I don't know how to set up spot correctly for it. Can I download using developer mode with the getcrx extension installed?

This getcrx extension worked great in Fossapup Jackal remaster. But I noticed that I now have a permission changer (root to spot, spot to root) option in my sys tray. I don't remember if it was always in Jackal Remaster, or if I installed it When I use the getcrx on regular Fossapup and try to download an extension from the webstore, I'm getting permission denied on the download, even in spot. So I'm not sure what the difference is. The getcrx is installed, the versions are the same (and not running off the same portable directory, I'm using seperate copies) so I'm confused. It's not critical at the moment, since I have many browsers, but you know, I'm always trying to learn something new.

Since I had the extensions crx files downloaded on Jackal, I just copied them in to the google extensions on Fossa, and so I have them installed. I guess what I'm saying is in Jackal I seemed to have download permissions granted, while in Fossa chromium does not have that permission even in /spot/downloads.

Now I'm a little curious about just running chromium from the same directory on both fossa installs. It should work, right? (I tried and yes it does work of course!)

thanks as always
you guys are amazing.

~geo

In my WDL_Arch64 system I'm currently running Chromium:

Version 89.0.4389.90 (Official Build) Arch Linux (64-bit)

Up to version 88.xxx Chromium supported Chrome sync and some other now Chrome-only stuff.

Arch Linux wiki explain how to re-enable sync in this latest version:

https://wiki.archlinux.org/index.php/chromium

using, I think: https://www.chromium.org/developers/how-tos/api-keys

However, they advice moving to open source xbrowsersync for bookmark syncing between browsers from now on:

https://xbrowsersync.org/

I notice that peebee also mentions xbrowsersync here: viewtopic.php?p=18941#p18941

wiak

Right, kiddiwinks.

Here, for your delectation, is the current 'portable' release of UnGoogled-Chromium.....v89.0.4389.90.

Now; I could apologise for the humungous size of this version, but.....I'm not going to. You wanna know why? Because, mes amis, this one has been compiled with all the VAAPI hardware acceleration stuff built-in.....the very stuff that I reported on a few years ago.....that Google couldn't be arsed to provide in Chrome itself. "Too much hard work; too many different versions to cover." Yeah, RIGHT. So how come somebody else can go to all that trouble.....and you lazy buggers CAN'T?

I tracked this down at woolyss.com.....the semi-official "home" of ready-to-go Chromium builds. Don't know why I never thought of this before. A guy by the handle of "Marmaduke" is providing ready-to-go, self-contained portable Linux builds of UnGoogled Chromium (even has WideVine built-in by default, so no need to "borrow" it from Chrome); this, of course, means there's even less work involved in 'converting' them to the Puppy-portable format. A good find, I think..!

Anyways; the new 'portable' is now available from the usual location in post #1. Posting from it now.

Enjoy..!

Mike.

Hi Mike,

So I downloaded and unpacked your portable. But I'm running Bionicpup64 which, according to pupsys-info, is using " Glibc: 2.27". I figure "What the hell. Right-Clicking 'LAUNCH' and selecting 'Run in Terminal' will only take a moment".

The terminal response was:
"[239100319/191931.895802:ERROR:message_box_dialog.cc(143)] Unable to show a dialog outside the UI thread message loop: Failed To Create Data Directory - Chromium cannot read and write to its data directory:

/initrd/mnt/dev_save/Pup-Apps/Ungoogled_Chromium-portable/chromium/PROFILE
[239850319/191933.468295:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[239100319/192000.783942:ERROR:ev_root_ca_metadata.cc(841)] Failed to register OID: 0"

But the UG-C opened and I'm posting from it now.
What all the above complaints means in practical terms and how much older the glibc can be are yet to be determined.

But, thanks, Mike. And pass my appreciation on to Marmaduke if you can.

p.s. Just noticed the curious 'boxes' in the quoted terminal output which, AFAICT, were added by the Forum's software.

p.p.s. I closed UG-C via Menu>Exit as I wanted to see what the terminal had to say about closing. I didn't have anything unusual to say. Looked in UG-C's "chromium" folder. There's a big red=broken symbolic link to /opt/Ungoogled_Chromium-portable/chromium/PROFILE which makes sense as the portable isn't in /opt. But it shouldn't be there at all.

p.p.p.s. Simple fix. Deleted the link. Restarted UG-C and a proper PROFILE folder was created.

@mikeslr :-

Damn. Done it again..! (Good catch, BTW.)

Repacked/re-uploaded to the Drive.

(Marmaduke must have compiled this against an older glibc. Just curious; will it run under Xenialpup64 7.5?)

EDIT:- Ooh, nice one. This will run under Fossapup64 9.5 (glibc 2.31), Bionicpup64 8.0 (2.27), Xenialpup64 7.5 (2.23).....and even jrb's Quirky64 "April" 7.0.1 (2.20) - Tahrpup-era! Posting from it now in the latter......and I haven't needed to use the 64-bit Xenial chroot, 'cos it's running natively! How's about that..?

Mike.

Also running in LxPupSc64 (slackware deriv) with, as expected, the following libs added to the chromium directory:

libatk-bridge-2.0.so -> libatk-bridge-2.0.so.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
libgdk-3.so -> libgdk-3.so.0.2404.7
libgdk-3.so.0 -> libgdk-3.so.0.2404.7
libgdk-3.so.0.2404.7
libgtk-3.so -> libgtk-3.so.0.2404.7
libgtk-3.so.0 -> libgtk-3.so.0.2404.7
libgtk-3.so.0.2404.7
libxkbcommon.so.0 -> libxkbcommon.so.0.0.0
libxkbcommon.so.0.0.0

and this line added to the LAUNCH script (wasn't needed in the 87 version):

export LD_LIBRARY_PATH=$HERE/chromium:$LD_LIBRARY_PATH

As with the previous ungoogled, I'm running it as spot with a common profile for all pups. The only nag run from terminal in that mode pertains to 'multiple sandboxes' . Pretty darn clean for chromium & spot. Posting from it in an LxPupSc64 20.06 +2 install with the 5.11.6 kernel now.
Also running fine in my very minimal 'Fossapup64 sans adrv with ydrv' built from the main Fossapup64 SFS only to run with no save file or folder.

Thanks,

There is a 32bit version of Un-Googled Chromium that works on upuphh+d (aka HirsutePup32).

The package can be downloaded at:
chromium-ungoogled-89.0.4389.114-i586-1alien.txz (Click on it to install)

The SlackBuild used to create it can be found at:
https://slackware.nl/people/alien/slack ... led/build/

I discovered this from the following post by @peebee:

How to ‘un-google’ your Chromium browser experience by alienbob ... Aka the future of Chromium based (embedded) brows

s243a wrote: ↑Tue Apr 06, 2021 3:21 am

There is a 32bit version of Un-Googled Chromium that works on upuphh+d (aka HirsutePup32).

The package can be downloaded at:
chromium-ungoogled-89.0.4389.114-i586-1alien.txz (Click on it to install)

The SlackBuild used to create it can be found at:
https://slackware.nl/people/alien/slack ... led/build/

I discovered this from the following post by @peebee:

How to ‘un-google’ your Chromium browser experience by alienbob ... Aka the future of Chromium based (embedded) brows

Em... My 'understanding' is that you are not allowed to use this package:

quote from alienbob per page: https://alien.slackbook.org/blog/how-to ... xperience/

I want to state here that from now on, I also explicitly forbid others / distros to re-use and re-package my binaries in order to make them part of their own Linux Distribution: thinking of Slacko Puppy, Porteus, Slint and others. If needed I will use “cease & desist” messages if people refuse to comply. I am not going to pay Google for the use of my binaries in distros that I do not control. The use of my API key is automatic if you run my Chromium binaries, and it involves a monthly cost if Google’s Could APIs get called too much. I already had to negotiate several times with the Chromium people to avoid getting billed when their policies changed. So get your own API key and compile your own version of the browser please.