librewolf/issues
25
145

Librewolf private window isnt running with the portable data and its using appdata instead. #1703

Closed
opened 2023年12月11日 19:39:21 +01:00 by NastyFlytrap · 4 comments

As title says. If i start librewolf portable and then right click on it on the taskbar, it starts a private window thats not using the portable settings and data. This is important because i need my extensions even in a private window and without it accessing that path i wont have access to them.

Either way, my solution would be that when i launch librewolf portable exe, it would do as it does now and launch the real exe thats told to use the portable settings, and then if i launch a private window off of that librewolf, it'd inherit the setting that tells it to look in the portable folder, and not in appdata.

Also, a small minor issue, putting a librewolf portable shortcut on the taskbar and launching it launches a normal librewolf instance, and therefore, doesnt stack with the shortcut because they are technicly speaking two different exe's. Any chance you could somehow fix this?

As title says. If i start librewolf portable and then right click on it on the taskbar, it starts a private window thats not using the portable settings and data. This is important because i need my extensions even in a private window and without it accessing that path i wont have access to them. Either way, my solution would be that when i launch librewolf portable exe, it would do as it does now and launch the real exe thats told to use the portable settings, and then if i launch a private window off of that librewolf, it'd inherit the setting that tells it to look in the portable folder, and not in appdata. Also, a small minor issue, putting a librewolf portable shortcut on the taskbar and launching it launches a normal librewolf instance, and therefore, doesnt stack with the shortcut because they are technicly speaking two different exe's. Any chance you could somehow fix this?

So, nothing?

So, nothing?

You can only open a private window when right-clicking a taskbar button if you've already pinned LibreWolf to the taskbar. Otherwise the option to open a private window isn't available.

Pinning the browser to the taskbar does not automatically add the explicitly specified profile folder (which is what the portable launcher does) to the pinned shortcut.

So the one issue (the fact that you pin the browser to the taskbar, which unfortunately causes the loss of the profile path specified by the portable launcher) causes the other (the private window will use a new profile in your application data). The same goes for the regular window: it will not use the portable profile if you start it directly from the pinned browser on the taskbar, as it will only use the portable profile when starting via LibreWolf-Portable.exe.

What you can do is drag the portable launcher itself (LibreWolf-Portable.exe) onto the taskbar. That way, it will always start with the right profile and clean up afterwards. However, it will also show a separate taskbar button for the LibreWolf window itself.

Another option is to manually add the profile folder at the end of the pinned shortcut: right-click the icon, then right-click LibreWolf, then click Properties and add e.g. -P=D:\Path\To\Profiles\Default to Target. This only works if you don't move the profile anymore and it won't clean up some files and folders anymore (since the portable launcher isn't run anymore).

You can only open a private window when right-clicking a taskbar button if you've already pinned LibreWolf to the taskbar. Otherwise the option to open a private window isn't available. Pinning the browser to the taskbar does not automatically add the explicitly specified profile folder (which is what the portable launcher does) to the pinned shortcut. So the one issue (the fact that you pin the browser to the taskbar, which unfortunately causes the loss of the profile path specified by the portable launcher) causes the other (the private window will use a new profile in your application data). The same goes for the regular window: it will not use the portable profile if you start it directly from the pinned browser on the taskbar, as it will only use the portable profile when starting via `LibreWolf-Portable.exe`. What you _can_ do is drag the portable launcher itself (`LibreWolf-Portable.exe`) onto the taskbar. That way, it will always start with the right profile and clean up afterwards. However, it will also show a separate taskbar button for the LibreWolf window itself. Another option is to manually add the profile folder at the end of the pinned shortcut: right-click the icon, then right-click `LibreWolf`, then click `Properties` and add e.g. ` -P=D:\Path\To\Profiles\Default` to Target. This only works if you don't move the profile anymore and it won't clean up some files and folders anymore (since the portable launcher isn't run anymore).

But if you don't pin it to the taskbar, right-click directly on the taskbar icon to open a new window still not use profile, is there a way?

But if you don't pin it to the taskbar, right-click directly on the taskbar icon to open a new window still not use profile, is there a way?

Correct, if you use the jumplist for this, it will use the default non-portable profile (or create one) in the %AppData%\LibreWolf\Profiles. Sorry, that's just how Firefox is built (and I actually make use of this fact sometimes), can't do anything about this, other than pinning a shortcut that defines the profile path and --private-window.

Correct, if you use the jumplist for this, it will use the default non-portable profile (or create one) in the `%AppData%\LibreWolf\Profiles`. Sorry, that's just how Firefox is built (and I actually _make use_ of this fact sometimes), can't do anything about this, other than pinning a shortcut that defines the profile path _and_ `--private-window`.
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
3 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#1703
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?