@Dingo / @TerryH :-
DAMN!!!! I've 'cocked-up'.....again!
I'm really sorry about this, guys. My trouble is that I will build and pack these things late at night, when if I had any sense I'd already be in dreamland. Consequently, I'm often yawning fit to crack a jaw, and so tired I can't think straight...
And it's ALL self-inflicted. I can't blame anybody else..!
(It still needed checking in any case, Terry... I couldn't remember if I made this mistake with both re-builds, or just one; so I 'fixed', double-checked, re-packed and re-uploaded BOTH of 'em again, just to make sure. Glad it's working for you now, anyways!)
----------------------------------------
Thanks for the screenshot, Dingo. That was the 'clue' I needed, rather than having to embark on a spell of detective work.
What's happened is that you guys have downloaded the tarball, which still contains MY profile inside it! And it's no 'ordinary' profile, either; large parts of it are shared from a common profile, which I use with both arches of Vivaldi. Hence all those missing sym-links, y'see...
I have a large, external directory on a remote-mounted partition, where I keep all my portable browsers'n'stuff, with sub-directories for both arches. Custom Menu entries then start them from this location.
When I build upgrades, I copy 'em across to a working directory, make the alterations, check that they run OK, then pack them, and transfer them across for upload. BUT; I don't always remember to delete the profiles..! I link all my browser profiles from a third, "common" directory - absolute links, with full $PATHs, so I can move them anywhere and the sym-links still hold; makes it quicker and easier for testing purposes.
I'm afraid you're both victims of my sheer "cussedness"! But it's an easy 'fix'.
Just go one level further into the 'vivaldi' main directory, and delete the 'PROFILE' directory you'll find there. Now try launching it again..... (*prays...*) Should work now!
I've 'fixed' and re-packed 'em. The tarballs at the Drive are all "kosher" now.... What a "prat", eh?
--------------------------------------------------------
That small window Dingo spotted that said the profile had been 'locked' to prevent corruption, you get this when sharing a single 'portable' between Puppies. One thing the Chromium-based browsers check for upon startup is the 'unique identifier' for your OS, which can be found at /etc/machine-id. It's a 32-digit alphanumeric number, unique to each and every Linux OS install. Every time you shut your browser down, then fire it up in a different Puppy, up pops this window. It's just one of the multitude of redundant safety-checks the Chromium code-base appears to be littered with.... (*shrug*)
Let me know if that fixes it for you both, please..!
Mike.