LibreWolf-portable 64-bit (remake)

[fredx181]

Here is a LibreWolf-portable remake of what @mikewalsh shared here: viewtopic.php?p=34456#p34456
(btw, got permission to do so from Mike himself )

The setup includes the latest Librewolf appimage (v131.0.3-1), and,
- different method to point to the (portable) profile (see Readme).
- choice to run as spot or as root
- checking if plain Alsa is used by the system for sound, if so, then run with included apulse (needed then to make sound work)

Tested on: FossaPup, BookwormPup and F96-CE .

EDIT: Note that it's required to run it on a Linux filesystem, not from e.g. FAT32 or NTFS .

Info: (content of included Readme)

*** Launching LibreWolf portable ***
To run LibreWolf 'as spot', run the "LAUNCH" script.
To run LibreWolf 'as root', run the "LAUNCH-as-root" script.

The Librewolf profile (portable) will be in: LibreWolf.x86_64.AppImage.home/.librewolf .
(for when running as spot and as root)
It makes use of the appimage feature to set $HOME inside directory <APPIMAGENAME>.home at the same level as the appimage.

*** How to Update ***
To update the appimage, go here: https://gitlab.com/librewolf-community/ ... -/releases
And download newest appimage, LibreWolf-<VERSION>.x86_64.AppImage (currently it's LibreWolf-131.0.3-1.x86_64.AppImage)

It will download as: LibreWolf.x86_64.AppImage .
Make executable e.g. chmod +x ./LibreWolf.x86_64.AppImage .
And replace the existing LibreWolf.x86_64.AppImage with the new one here.

*** fusermount error ***
If you run as spot (LAUNCH) and librewolf won't start, run ./LAUNCH from terminal.
If it shows an error e.g. fusermount: ....
Then fusermount needs to have the "sticky bit" set for to run as spot, to fix:
chmod u+s `which fusermount`

*** apulse ***
On systems with plain Alsa (no pipewire or pulseaudio running),
then the LD_LIBRARY_PATH env. will be set to make use of the libraries in folder "apulse".

Download LibreWolf-portable64.tar.xz :
https://drive.google.com/uc?export=down ... NLpwBys2BR

[fredx181]

Here's attached the same LibreWolf-portable64 setup but without the appimage included.

LibreWolf-portable64-no-appimg.tar.gz

LibreWolf-portable64 without appimage

(173.62 KiB) Downloaded 12 times

FYI, the appimage can be downloaded here: https://gitlab.com/librewolf-community/ ... -/releases

Btw, for the scripts to work, do not rename the appimage (keep it LibreWolf.x86_64.AppImage ) .
And I've found that on e.g. BookwormPup, when running as spot, the extension .AppImage is required.

[TerryH]

Downloaded and extracted the appimage to /mnt/home. On the first attempt I ran the LAUNCH script to run LibreWolf as user spot, it failed giving the 'Your Firefox profile cannot be loaded. It may be missing or inaccessible.' message. I then used the LAUNCH-as-root, to successfully run LibreWolf. No idea why it won't run as spot.

Edit: I checked this LibreWolf-portable in KLV-Airedale SR15, using the basic LAUNCH script it runs successfully. Posting from it now.

[MochiMoppel]

@fredx181 Would it be possible to provide your scripts without the included LibreWolf.x86_64.AppImage?
In case of LibreWolf the versions change frequently, which means that your package will fast become obsolete. It also means that users who care about security will have to download the file from the official site anyway, and weird users like me who have no issues with the officially provided LibreWolf.x86_64.AppImage may get new ideas from your script without downloading stuff they already have.

P.S.: Where can I find LibreWolf's change history?

[greengeek]

and weird users like me who have no issues with the officially provided LibreWolf.x86_64.AppImage may get new ideas from your script without downloading stuff they already have.

Can I ask which link you use to access the Librewolf appimage?
(Is it this one: https://gitlab.com/api/v4/projects/2438 ... 4.AppImage) ?
(Found here: https://librewolf.net/installation/linux)

And any tips on how you choose to run it?
Cheers!
(Still working out which method works best for me on a cutdown Fossa64 9.5)

[fredx181]

@fredx181 Would it be possible to provide your scripts without the included LibreWolf.x86_64.AppImage?

Ok, see: viewtopic.php?p=133775#p133775

P.S.: Where can I find LibreWolf's change history?

Here ? : https://codeberg.org/librewolf/source/c ... 2-1...main

[fredx181]

Downloaded and extracted the appimage to /mnt/home. On the first attempt I ran the LAUNCH script to run LibreWolf as user spot, it failed giving the 'Your Firefox profile cannot be loaded. It may be missing or inaccessible.' message. I then used the LAUNCH-as-root, to successfully run LibreWolf. No idea why it won't run as spot.
...

On which OS ?

Downloaded and extracted the appimage to /mnt/home

No need to extract the appimage (but perhaps you mean: extracted the tar.xz archive ?)

[TerryH]

Sorry Fred, I thought I put the OS, it was Bookwormpup64 10.0.8.

Yes, I extracted from the tar archive.

[esos]

extracted the LibreWolf-portable64.tar.xz archive in the spot folder on VoidPup64-22.02-240919 and fire up launch as spot. The same problem like TerryH "Your Firefox profile cannot be loaded" message.

[bigpup]

EDIT: Note that it's required to run it on a Linux filesystem, not from e.g. FAT32 or NTFS

So it has to be in the Puppy save, if you have installed Puppy on a fat32 or ntfs formatted location?

[fredx181]

Sorry Fred, I thought I put the OS, it was Bookwornpup64 10.0.8.

Yes, I extracted from the tar archive.

Can you say more about what you did exactly, I cannot reproduce that error in BookwormPup: 'Your Firefox profile cannot be loaded. It may be missing or inaccessible.'
Works ok in BookwormPup for me when running from a Linux partition and from /home/spot too.

What I do get, btw, is when running the portable (LAUNCH) from /root :
ash: exec: line 10: /root/LibreWolf-portable64/LibreWolf.x86_64.AppImage: Permission denied (that comes from run-as-spot AFAIK)
Some security built in Bookworm that a normal user like spot cannot access /root

extracted the LibreWolf-portable64.tar.xz archive in the spot folder on VoidPup64-22.02-240919 and fire up launch as spot. The same problem like TerryH "Your Firefox profile cannot be loaded" message.

Thanks. I'll get back to that later, first find out why that error message on BookwormPup (from TerryH report).

[fredx181]

EDIT: Note that it's required to run it on a Linux filesystem, not from e.g. FAT32 or NTFS

So it has to be in the Puppy save, if you have installed Puppy on a fat32 or ntfs formatted location?

Probably yes, if you only have fat32 or ntfs partition.

[TerryH]

Sorry Fred, I thought I put the OS, it was Bookwornpup64 10.0.8.

Yes, I extracted from the tar archive.

Can you say more about what you did exactly, I cannot reproduce that error in BookwormPup: 'Your Firefox profile cannot be loaded. It may be missing or inaccessible.'
Works ok in BookwormPup for me when running from a Linux partition and from /home/spot too.

What I do get, btw, is when running the portable (LAUNCH) from /root :
ash: exec: line 10: /root/LibreWolf-portable64/LibreWolf.x86_64.AppImage: Permission denied (that comes from run-as-spot AFAIK)
Some security built in Bookworm that a normal user like spot cannot access /root

extracted the LibreWolf-portable64.tar.xz archive in the spot folder on VoidPup64-22.02-240919 and fire up launch as spot. The same problem like TerryH "Your Firefox profile cannot be loaded" message.

Thanks. I'll get back to that later, first find out why that error message on BookwormPup (from TerryH report).

The partition I use is formatted ext4 on an internal nvme ssd. After extracting the tar.xz, to the partition containing all my frugal installs, I opened the directory, checked permissions of script (don't remember if i had to change to allow execution) and then executed the the program on the first attempt by clicking on the LAUNCH script. I received the error message. I then ran it from a terminal using ./LAUNCH, which failed.

I then ran using LAUNCH-as-root which was successful.

[d-pupp]

Sounds like permission to me.
Launching as spot would fail in a root owned folder.

[MochiMoppel]

@fredx181 Would it be possible to provide your scripts without the included LibreWolf.x86_64.AppImage?

Ok, see: viewtopic.php?p=133775#p133775

Thanks

P.S.: Where can I find LibreWolf's change history?

Here ? : https://codeberg.org/librewolf/source/c ... 2-1...main

Well,no. I was hoping for a human readable history, one that gives me the highlights and new features of each release.

[TerryH]

Sounds like permission to me.
Launching as spot would fail in a root owned folder.

The launch scripts include chown commands to change the ownership to spot or root depending on which script is being run, so it will run as either.

[TerryH]

Sorry Fred, I thought I put the OS, it was Bookwornpup64 10.0.8.

Yes, I extracted from the tar archive.

Can you say more about what you did exactly, I cannot reproduce that error in BookwormPup: 'Your Firefox profile cannot be loaded. It may be missing or inaccessible.'
Works ok in BookwormPup for me when running from a Linux partition and from /home/spot too.

What I do get, btw, is when running the portable (LAUNCH) from /root :
ash: exec: line 10: /root/LibreWolf-portable64/LibreWolf.x86_64.AppImage: Permission denied (that comes from run-as-spot AFAIK)
Some security built in Bookworm that a normal user like spot cannot access /root

extracted the LibreWolf-portable64.tar.xz archive in the spot folder on VoidPup64-22.02-240919 and fire up launch as spot. The same problem like TerryH "Your Firefox profile cannot be loaded" message.

Thanks. I'll get back to that later, first find out why that error message on BookwormPup (from TerryH report).

The partition I use is formatted ext4 on an internal nvme ssd. After extracting the tar.xz, to the partition containing all my frugal installs, I opened the directory, checked permissions of script (don't remember if i had to change to allow execution) and then executed the the program on the first attempt by clicking on the LAUNCH script. I received the error message. I then ran it from a terminal using ./LAUNCH, which failed.

I then ran using LAUNCH-as-root which was successful.

To test further, I booted my Bookwormpup64 with pfix=ram to check on a pristine boot. LibreWolf-portable ran successfully on this attempt. So unfortunately something in the save folder seems to be interfering with the script execution. At present I have no idea what it may be, I'll check further.

[fredx181]

extracted the LibreWolf-portable64.tar.xz archive in the spot folder on VoidPup64-22.02-240919 and fire up launch as spot. The same problem like TerryH "Your Firefox profile cannot be loaded" message.

I tested now on VoidPup64, extracted in /home/spot, ran LAUNCH and it's working fine for me.
Also no problem when launching from /mnt/home.
Still cannot explain what could possibly cause the "Your Firefox profile cannot be loaded" message.

[bigpup]

Tried it running in BookwormPup64 10.0.8

Working OK for me.

I used pExtract to do the extraction.

Maybe something about what is used to do the extraction process is causing these issues

[Chelsea80]

@TerryH @esos

I have no idea as to the answer to your problem, however, this is an AI answer, correct or incorrect or misleading maybe, but worth a punt at least:

extracted the LibreWolf-portable64.tar.xz archive in the spot folder on VoidPup64-22.02-240919 and fire up launch as spot and got Your Firefox profile cannot be loaded

Sources
support.mozilla.org favicon
github.com favicon

Answer
Since you're using LibreWolf (a Firefox-based browser) on VoidPup64-22.02-240919, the "Your Firefox profile cannot be loaded" error likely stems from profile issues. Here are some steps to resolve this:

Check Permissions
Open a terminal and navigate to the LibreWolf directory
text
cd /path/to/LibreWolf/directory

Ensure proper permissions:
text
chmod -R u+rw

Create a New Profile
In the terminal, run LibreWolf with the profile manager
text
./librewolf -P

In the Profile Manager window, click "Create Profile"
Follow the prompts to create a new profile
Select the new profile and click "Start LibreWolf"

Delete profiles.ini
If creating a new profile doesn't work

Navigate to the LibreWolf configuration directory
text
cd ~/.librewolf

Delete the profiles.ini file
text
rm profiles.ini

Restart LibreWolf

Check for Conflicting Files
Look for leftover Firefox or LibreWolf configuration files
text
ls -la ~ | grep -E '\.mozilla|\.librewolf'

If you find conflicting directories, rename or remove them
Verify LibreWolf Installation
Ensure LibreWolf was extracted correctly

Check the contents of the LibreWolf directory:
text
ls -l /path/to/LibreWolf/directory

Verify the presence of essential files like librewolf and librewolf.cfg
If files are missing, re-extract the archive
text
tar -xvf LibreWolf-portable64.tar.xz -C /path/to/destination

Run as Root (Temporary Test)
As a diagnostic step, try running LibreWolf as root to rule out permission issues
text
sudo ./librewolf

If it works as root but not as spot, focus on fixing permissions

If these steps don't resolve the issue, check LibreWolf logs (usually in the installation directory or ~/.librewolf/) for specific error messages that might provide more insight into the problem.

Good luck

[fredx181]

@TerryH @esos

I have no idea as to the answer to your problem, however, this is an AI answer, correct or incorrect or misleading maybe, but worth a punt at least:
...

Thanks. Unfortunately AI doesn't know about the details of this uncommon portable setup, but perhaps some things it says are useful to try finding out what causes "Your Firefox profile cannot be loaded".

[esos]

Thanks fredx181,
I tested last night booting VoidPup64/S15pup in frugalinstall and /home/spot/Librewolfportable Launch as spot is working fine.
Just wondering why /home/spot/Librewolfportable will not run LAUNCH as spot on VoidPup64/S15pup(direct iso booting).
Any other iso(s)booting, Librewolfportable as spot works fine.