librewolf/issues
25
145

Symlinking librewolf.overrides.cfg does not work #2840

Closed
opened 2026年01月30日 16:48:20 +01:00 by jdw · 4 comments

LibreWolf Version

147.0.2-1

Operating System

Fedora / RHEL

Installation Source / Package

Flatpak

Description

I am symlinking (using stow) my librewolf.overrides.cfg configuration file to the place where librewolf should be looking for it, but it does not have any effect. Below you can see its precies location as well as its contents.

If instead I copy the file to the exact same location, everything works fine. It would be great if I could symlink the configuration so I can have all my configuration files in one place.

Logs / Screenshots

Output of ls -al ~/.var/app/io.gitlab.librewolf-community/.librewolf/:

total 16
drwxr-xr-x. 1 jdw jdw 202 Jan 30 16:23 .
drwxr-xr-x. 1 jdw jdw 74 Jan 29 18:09 ..
drwx------. 1 jdw jdw 20 Jan 29 18:09 ckzpdpp1.default
-rw-r--r--. 1 jdw jdw 62 Jan 29 18:09 installs.ini
lrwxrwxrwx. 1 jdw jdw 118 Jan 30 16:23 librewolf.overrides.cfg -> ../../../../Configuration/dotfiles/librewolf/.var/app/io.gitlab.librewolf-community/.librewolf/librewolf.overrides.cfg
drwxr-xr-x. 1 jdw jdw 106 Jan 29 18:09 Profile Groups
-rw-r--r--. 1 jdw jdw 259 Jan 29 18:09 profiles.ini
drwx------. 1 jdw jdw 1702 Jan 30 16:29 vv47xb5z.default-default

Output of cat ~/.var/app/io.gitlab.librewolf-community/.librewolf/librewolf.overrides.cfg

pref("places.history.enabled", false);
pref("browser.newtabpage.activity-stream.feeds.topsites", false);
pref("browser.newtabpage.activity-stream.feeds.section.highlights", false);
pref("browser.urlbar.suggest.openpage", false);
pref("browser.urlbar.suggest.topsites", false);
pref("browser.urlbar.suggest.history", false);
pref("browser.tabs.warnOnClose", false);
pref("browser.tabs.closeWindowWithLastTab", false);
pref("privacy.resistFingerprinting.letterboxing", false);
pref("pdfjs.previousHandler.alwaysAskBeforeHandling", true);
pref("signon.rememberSignons", false);
pref("full-screen-api.warning.timeout", 0);
pref("browser.translations.automaticallyPopup", false);
### LibreWolf Version 147.0.2-1 ### Operating System Fedora / RHEL ### Installation Source / Package Flatpak ### Description I am symlinking (using [`stow`](https://www.gnu.org/software/stow/manual/stow.html)) my `librewolf.overrides.cfg` configuration file to the place where librewolf should be looking for it, but it does not have any effect. Below you can see its precies location as well as its contents. If instead I copy the file to the exact same location, everything works fine. It would be great if I could symlink the configuration so I can have all my configuration files in one place. ### Logs / Screenshots Output of `ls -al ~/.var/app/io.gitlab.librewolf-community/.librewolf/`: ``` total 16 drwxr-xr-x. 1 jdw jdw 202 Jan 30 16:23 . drwxr-xr-x. 1 jdw jdw 74 Jan 29 18:09 .. drwx------. 1 jdw jdw 20 Jan 29 18:09 ckzpdpp1.default -rw-r--r--. 1 jdw jdw 62 Jan 29 18:09 installs.ini lrwxrwxrwx. 1 jdw jdw 118 Jan 30 16:23 librewolf.overrides.cfg -> ../../../../Configuration/dotfiles/librewolf/.var/app/io.gitlab.librewolf-community/.librewolf/librewolf.overrides.cfg drwxr-xr-x. 1 jdw jdw 106 Jan 29 18:09 Profile Groups -rw-r--r--. 1 jdw jdw 259 Jan 29 18:09 profiles.ini drwx------. 1 jdw jdw 1702 Jan 30 16:29 vv47xb5z.default-default ``` Output of `cat ~/.var/app/io.gitlab.librewolf-community/.librewolf/librewolf.overrides.cfg` ``` pref("places.history.enabled", false); pref("browser.newtabpage.activity-stream.feeds.topsites", false); pref("browser.newtabpage.activity-stream.feeds.section.highlights", false); pref("browser.urlbar.suggest.openpage", false); pref("browser.urlbar.suggest.topsites", false); pref("browser.urlbar.suggest.history", false); pref("browser.tabs.warnOnClose", false); pref("browser.tabs.closeWindowWithLastTab", false); pref("privacy.resistFingerprinting.letterboxing", false); pref("pdfjs.previousHandler.alwaysAskBeforeHandling", true); pref("signon.rememberSignons", false); pref("full-screen-api.warning.timeout", 0); pref("browser.translations.automaticallyPopup", false); ```

Maybe because the flatpak does not have permissions to follow the symlink?

Maybe because the flatpak does not have permissions to follow the symlink?
Author
Copy link

That is a good point. I now granted access to that location using

flatpak --user override --filesystem=~/Configuration/dotfiles/librewolf io.gitlab.librewolf-community

If I now enter the flatpak container using

flatpak run --command=bash io.gitlab.librewolf-community 

and I run

cat ~/Configuration/dotfiles/librewolf/.var/app/io.gitlab.librewolf-community/.librewolf/librewolf.overrides.cfg 

inside the flatpak container, it correctly outputs the contents of the file, but the configuration still has no effect.

That is a good point. I now granted access to that location using ``` flatpak --user override --filesystem=~/Configuration/dotfiles/librewolf io.gitlab.librewolf-community ``` If I now enter the flatpak container using ``` flatpak run --command=bash io.gitlab.librewolf-community ``` and I run ``` cat ~/Configuration/dotfiles/librewolf/.var/app/io.gitlab.librewolf-community/.librewolf/librewolf.overrides.cfg ``` inside the flatpak container, it correctly outputs the contents of the file, but the configuration still has no effect.

you could try manually setting autoadmin.global_config_url in about:config to the path you want to use

you could try manually setting `autoadmin.global_config_url` in `about:config` to the path you want to use
Author
Copy link

Sorry for not reporting back in such a long time. I now set autoadmin.global_config_url to the absolute path of the file in my dotfiles folder, so I can manage my librewolf config together with my other configuration. Setting it to the symlinked file inside ~/.var/app/io.gitlab.librewolf-community did not work.

What's also curious to me is that the default value of autoadmin.global_config_url was file:///var/home/<user>/.librewolf/librewolf.overrides.cfg, i.e. the absolute path to where the file would be for a non-flatpak install but that a non-symlink file at ~/.var/app/io.gitlab.librewolf-community/.librewolf/librewolf.overrides.cfg is read correctly nonetheless.

Anyway, thanks for your help!

Sorry for not reporting back in such a long time. I now set `autoadmin.global_config_url` to the absolute path of the file in my dotfiles folder, so I can manage my librewolf config together with my other configuration. Setting it to the symlinked file inside `~/.var/app/io.gitlab.librewolf-community` did not work. What's also curious to me is that the default value of `autoadmin.global_config_url` was `file:///var/home/<user>/.librewolf/librewolf.overrides.cfg`, i.e. the absolute path to where the file would be for a non-flatpak install but that a non-symlink file at `~/.var/app/io.gitlab.librewolf-community/.librewolf/librewolf.overrides.cfg` is read correctly nonetheless. Anyway, thanks for your help!
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
Branding
Issues that relate to our logo or the branding of our browser and website.
Broken Upstream
Issue is also present in Firefox
Build
Alpine
Issues specific to the Alpine Linux build of LibreWolf.
Build
AppImage
Issues specific to the AppImage release of LibreWolf.
Build
AUR
Issues specific to the AUR build of LibreWolf.
Build
Debian
Issues specific to our official release for Debian based distros.
Build
DebianOBS
Issues specific to the non-official OBS build of LibreWolf.
Build
Fedora
Issues specific to our official release for Fedora.
Build
FedoraCOPR
Issues specific to the non-official COPR build of LibreWolf.
Build
Flatpak
Issues specific to the Flatpak release of LibreWolf.
Build
Gentoo
Issues specific to the Gentoo build of LibreWolf.
Component: Infrastructure
Issues related to infrastructure provided by LibreWolf
Component
Builds
Issues related to how we build LibreWolf
Component
Patches
Issue with one of the patches in our source code.
Component
Settings
Issues related to the settings of LibreWolf.
Component
UI
A purely cosmetic issue in our browser.
Component
Website
Issues with our website.
Docs
Change required
A needed change in our documentation.
Docs
FYI
Issues that document a change, or how stuff gets patched, built or configured.
Flag
Caution
Change that might be tricky or that needs to be carefully evaluated. Best suited for core members.
Flag
Good first issue
Suited for a first contribution as it is a straightfoward task!
FreeBSD
Issues related to the FreeBSD release of LibreWolf.
Linux
Issues realted to one or all our Linux releases.
macOS
Issues realated to the MacOS release of LibreWolf.
Needed
Help
We are stuck :-(
Needed
Info
Closing in ten days if no details are provided.
Needed
Testing
We are almost there!
Prio
High
Issues with a high priority
Prio
Low
Prio
Normal
Prio/Urgent
Issues needing immediate attention
Repositories
An issue with our repositories.
Research
Collecting informations to document something or to evaluate a change.
Source
Issues related to the source code of LibreWolf.
Status
Blocked
An issue blocked by another one.
Status
Duplicate
Look for existing issues.
Status
Icebox
Change that is not happening soon or issue that cannot be tested.
Status
Known issue
An issue that we are aware of but that we cannot fix at the moment.
Status
Not Planned
The requested feature is currently not planned
Status
Upstream
Either we upstreamed the issue or a fix is coming directly from Mozilla!
Status
Won't fix
Does not require a fix.
Type
?
What?
Type
Bug
Ouch...
Type
Discussion
Let's have a talk...
Type
Feature
A feature request.
Type
Question
Not a issue but just a user question
Type
Task
This needs to be done
Windows
Issues related to the Windows release of Librewolf.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
librewolf/issues#2840
Reference in a new issue
librewolf/issues
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?