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

[mikewalsh]

@xenial :-

Mm. Well, I guess part of the reason I don't seem to have problems with these things is because most of the time, I'm in Barry's old Quirky64 April 7.0.1. Barry used these things as experimental test-beds, and included a number of things you never used to get in the Puppies, OOTB. I'm pleasantly surprised so much modern stuff still works in it, given its vintage...!

On top of which, I've added so much other stuff myself, I couldn't even begin to catalogue what's 'extra' and what isn't.

What Puppy are you getting this issue in? If I can, I'll try a 'vanilla' boot into it and see if the problem is there for me. If I can duplicate it, I'll see if it's 'fixable'. If not, I'll just switch back to the tarball download instead. It's no skin off my nose...

A thought. What happens if you try to run the 'LAUNCH' script in the terminal? Any clues?

What's your readout look like?

Mike.

[xenial]

Hello mike,
I am using fossapup64.
Just to add your other portables have updated perfectly it's just ugc giving upset..i have ran the librewolf appimage on here just fine with no problems.

It is nothing to worry about as i have at least half a dozen of your portables on here lol.

[Marv]

Pristine boots of both fossapup64 9.5 and LxPupSc64 22.02 +4 both fail on fusermount for me. Portable extracted and run with no changes made at all. VoidPup64 is fine. The terminal message on failure is:

Code: Select all

root# ./LAUNCH
fusermount: mount failed: Operation not permitted

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information

All 3 are fine with the 'older' packaging ie. the works in a chromium directory...

Thanks,

[xenial]

I am getting exactly the same terminal error message as marv has reported above.

[mikewalsh]

@Marv / @xenial :-

'Kay, guys, that's what I wanted; feedback. All right; we'll revert to the tarballed 'chromium' directory.

I should have expected this, because in the last couple of weeks "Marmaduke" has upgraded his build system to OpenSuse 'Tumbleweed'.....a rolling release that is always bang-up-to-date with the very newest of everything (including a far newer version of fusemount than any Puppy yet supports, no doubt).

I'll re-pack & re-upload. Bear with me!

Mike.

[mikewalsh]

Right. Back to normal again, gang.

This shouldn't give problems now....sorry to make y'all re-download.

Mike.

[Marv]

No problem at all, I already reconfigured it & it's working perfectly I will do a quick check on the reuploaded version anyway.

Thanks,

[mikewalsh]

@Marv :-

No problem at all, I already reconfigured it & it's working perfectly I will do a quick check on the reuploaded version anyway.

Thanks,

The principle I outlined above still holds in essence - except instead of swapping AppImages, you're swapping 'chromium' directories instead. Still just as easy....

Mike.

[xenial]

Thank you very much mike.
Updated perfectly with no issues.

[soniabu]

hey Mike ciao,
maybe there is also a 32-bit version: right?
sonia

[mikewalsh]

Afternoon, gang.

After something of a hiatus, here's the Puppy-portable build of Marmaduke's latest offering - v105.0.5195.54.

Silky-smooth as always. The link can be found at the usual location in post #1.....follow the standard usage instructions.

Have fun.

Mike.

[Marv]

Thanks Mike! As usual, slick'n'quick. Extracted, in my 'portables' directory and so far tested in VoidPup64 +9 with no issues. When I reboot I'll check fossapup64 and LxPupSc64.

[mikewalsh]

You're very welcome, Marv. Enjoy.

Mike.

[mikewalsh]

...and it's upgrade time again. Here's the Puppy-portable build of v106.0.5249.103.

'Marmaduke's work is as silky-smooth as always.....and reliable as ever.

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

Download available from the link in post #1. As always:-

• Download

• Unzip

• Move the portable directory wherever you like.....though outside the 'save' is best

• Click to enter

• Click 'LAUNCH' to fire it up

Scripts permit adding a menu entry from the portable's location, if one is required. (Read the 'MenuReadMe..!) Otherwise, run from the 'LAUNCH' script every time, to keep it 'portable'.

Enjoy.

Mike.

[mikewalsh]

Upgrade time again. Here's the Puppy-portable build of v107.0.5304.87.

Silky-smooth as always. No issues to report.....at all.

Download link as in post #1.

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

D/l
Unzip
Move the portable directory anywhere you like, though preferably outside the 'save'
Click to enter
Click 'LAUNCH' to fire it up

Scripts permit the addition/removal of a Menu entry, should one be required. Otherwise, keep completely 'portable' & fire-up via the 'LAUNCH' script.

Enjoy!

Mike.

[Marv]

In like Flynn! Thanks Mike. Used my slightly tweaked LAUNCH script, otherwise OOTB. Posting from my fossapup64 9.5 install with no savefile and all basic configuration carried on the ydrive.

Cheers,

[mikewalsh]

'Kay, guys. Update time again...

Here's the Puppy-portable version of Ungoogled Chromium v108.0.5359.98.....full of Marmaduke's usual silky-smooth goodness.

Everything functioning A-OK, like always.

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

Download available from the usual link in post #1. Usual caveats apply:-

• Download

• Unzip

• Move the 'portable' anywhere you like, though outside the 'save' IS preferable

• Click to enter

• Click 'LAUNCH' to fire it up and use the self-contained profile

Scripts permit the addition of a Menu entry, should one be required. Enjoy!

Mike.

[Marv]

Good to go here Mike.

Quick round robin test in FossaPup64_9.6_CE_radky4, VoidPup64 22.02 +14, S15pup64 22.12 +1, and even LxPupSc64 22.02 +2 with a little extra library fiddling. I'm retiring that pup soon so I unfiddled

Thanks,

[mikewalsh]

Right, gang. Update time (again....)

Here's the current 'Puppy-portable' of Ungoogled Chromium v110.0.5481.100. As usual, utilising 'Marmaduke's' excellent builds.....silky-smooth, as always.

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

Nothing to add. How do you 'improve' upon perfection..?

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

Usual 'rules' apply:-

• D/load

• Unzip

• Move anywhere you like.....preferably outside the 'save'

• Click to enter

• Click 'LAUNCH' to, well.....launch!

A Menu-entry CAN be added (if required) using the supplied MenuAdd/Remove scripts. The 'MenuReadMe' explains how to use 'em.

Have fun! Enjoy.

Mike.

[Marv]

As advertised Mike, Posting in it OOTB in LxPupSc64 23.01 +1d.
Thanks, Jim

[mikewalsh]

As advertised Mike, Posting in it OOTB in LxPupSc64 23.01 +1d.
Thanks, Jim

Good, good. Enjoy...

Mike.

[CatPup]

Hey, I can't launch the program at all, with the "LAUNCH" file, under Fosspup96 RC1.

[Marv]

Hey, I can't launch the program at all, with the "LAUNCH" file, under Fosspup96 RC1.

Two quick things to try.

First: Check the permissions of /home/spot. They have to be spot:spot and if not can be set that way recursively from rightclick>properties.

Second: Try adding >/dev/null 2>&1 to the end of the 'run-as-spot' lines in LAUNCH, should be lines 16,20, and 22.

I don't know about RC1 but the second patch is not needed in either F96-CE_2 or in jammypup64, upup C!. A few of my pup installs have balked starting some of the portables from .desktops with 'Terminal=false' without that.

[mikewalsh]

Okay, guys'n'gals. Update time again....

Here's the new Puppy-portable build of Marmaduke's silky-smooth Ungoogled Chromium. We're now at v112.0.5615.67. Pure "gold".....as always.

Download link can be found at the bottom of post #1.

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

As usual:-

• Download

• Unzip

• Move the portable anywhere you like - preferably, outside the 'save'

• Click to enter

• Click 'LAUNCH' to fire it up

A Menu-entry can be added from wherever the portable has ben located, if one is desired, using the resident MenuAdd/MenuRemove scripts.

Any probs, y'all know where to find me. Have fun..!

Mike.

[Marv]

Thanks Mike! No muss no fuss. Running Version 112.0.5615.67 (Official Build, ungoogled-chromium) (64-bit) in 'another jammypup64' version E1 now. Posting from that combo.
v112 gracefully accepted my profile from v110 so a very easy upgrade.

[MochiMoppel]

Here's the new Puppy-portable build of Marmaduke's silky-smooth Ungoogled Chromium. We're now at v112.0.5615.67. Pure "gold".....as always.

Let's call it "silver" Unpacked to /opt but it does not work as portable.
You'll have to remove the dead link PROFILE. Seems to be a leftover of your tests and points to /mnt/sda3/SYSTEMS/BROWSERS...
Also prevents cache clearing despite the final bogus " ~~~ CACHE CLEARED! ~~~" message. Here a check would be helpful to test if the rm -rf $HERE/PROFILE/Default/Cache/* was actually successful.

Next problem: When I copy the stuff to /mnt/home, which in my case is a FAT32 USB stick, the dead PROFILE link can't be created, which of course is good, but when I start LAUNCH I'm imediately greeted by the "Do you wish to clear the Chromium cache?" dialog. No, I don't want to clear the cache, I want to run Chromium first. How can I do that? Starting LAUNCH from a terminal tells me /mnt/sdb1/x/test/Ungoogled_Chromium-portable64/PROFILE/SingletonLock: Permission denied. AFAIK it's not possible to use chown on a FAT32 FS, thus preventing me to become spot.

Next experiment: Adding --no-sandbox option.
Result:

Code: Select all

[30146:30146:0413/155720.046907:ERROR:process_singleton_posix.cc(334)] Failed to create /mnt/sdb1/x/test/Ungoogled_Chromium-portable64/PROFILE/SingletonLock: Operation not permitted (1)
[30146:30146:0413/155720.047157:ERROR:chrome_browser_main.cc(1424)] Failed to create a ProcessSingleton for your profile directory. This means that running multiple instances would start multiple browser processes rather than opening a new window in the existing process. Aborting now to avoid profile corruption.

"Profile corruption"? Sounds scary. So I removed the --user-data-dir=$HERE/PROFILE argument which finally causes Chromium to start with the funny caveat "You are using an unsupported command-line flag: --no-sandbox. Stabiility and security will suffer". But this removes the portabiliy feature.

There must be a better way to run this browser "silky-smooth" as root from a FAT32 device. Any idea?

[Grey]

@mikewalsh Mike, can you please check if this online simulation of the old Octopus game from the Game & Watch series works for you in the Marmaduke version?
It works in Firefox for me, but nothing happens in Chromium after pressing Play.

[williwaw]

Starting LAUNCH from a terminal tells me /mnt/sdb1/x/test/Ungoogled_Chromium-portable64/PROFILE/SingletonLock: Permission denied. AFAIK it's not possible to use chown on a FAT32 FS, thus preventing me to become spot.
There must be a better way to run this browser "silky-smooth" as root from a FAT32 device. Any idea?

I ran into similar issues running a startup script as root, that is, having to change owners of profiles created by root.

where chown is not available, could the script be run by spot and still be "portable" enough?
at least portable for use by spot with any distro that supports the user spot?

[pp4mnklinux]

Same problem here.- I can't start it .

When I clicked on LAUNCH... it tells me if I wanna clear or not CACHE.. but I can click on whatever of them.... the program doesn't start.

You can read the answer when trying to start from terminal.

Thanks

Hey, I can't launch the program at all, with the "LAUNCH" file, under Fosspup96 RC1.

[mikewalsh]

@mikewalsh Mike, can you please check if this online simulation of the old Octopus game from the Game & Watch series works for you in the Marmaduke version?
It works in Firefox for me, but nothing happens in Chromium after pressing Play.

@Grey :-

Doesn't work in Marmaduke's build either. I press 'Play'.....the button disappears, and nothing happens.

No idea, I'm afraid.

Mike.