github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #4891] librewolf: cannot open new URLs into running instance #2804

New issue
Closed
opened 2026-05-05 09:27:41 -06:00 by gitea-mirror · 8 comments
gitea-mirror commented 2026-05-05 09:27:41 -06:00
Owner
Copy link

Originally created by @Lonniebiz on GitHub (Feb 2, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4891

firejail version 0.9.64.4
Debian 11
LibreWolf v96.0.3-2

This issue is similar to one reported for Firefox.

A list of LibreWolf AppImages can be found here. Here's the command I'm using to run LibreWolf:
firejail --appimage --profile=/etc/firejail/librewolf.profile ~/AppImages/LibreWolf.x86_64.AppImage

The problem occurs after first launch, when I'm trying to open additional web pages. For example, let's say LibreWolf is already running, and I want to open Ebay from the command line:
firejail --appimage --profile=/etc/firejail/librewolf.profile ~/AppImages/LibreWolf.x86_64.AppImage https://www.ebay.com

Instead of opening Ebay into a new tab, I get this error:
LW

In a prior AppImage of LibreWolf, version 96.0.2-1, I was able to get past this issue using a custom profile:

~/.config/firejail/librewolf.profile

# Firejail profile for Librewolf
# Description: Firefox fork based on privacy
# This file is overwritten after every install/update
# Persistent local customizations
include librewolf.local
# Persistent global definitions
include globals.local

noblacklist ${HOME}/.cache/librewolf
noblacklist ${HOME}/.librewolf

mkdir ${HOME}/.cache/librewolf
mkdir ${HOME}/.librewolf
whitelist ${HOME}/.cache/librewolf
whitelist ${HOME}/.librewolf

whitelist /usr/share/doc
whitelist /usr/share/gtk-doc/html
whitelist /usr/share/mozilla
whitelist /usr/share/webext
include whitelist-usr-share-common.inc

dbus-user filter
dbus-user.own org.mozilla.librewolf.*
ignore dbus-user none

# Redirect
include firefox-common.profile

Then, I'd launch v96.0.2-1 using the custom profile above:
firejail --appimage --profile=~/.config/firejail/librewolf.profile ~/AppImages/LibreWolf.x86_64.AppImage

Later, when I'd launch a URL (with LibreWolf already running), it would open that URL in a new tab with the following command:
firejail --appimage --profile=~/.config/firejail/librewolf.profile ~/AppImages/LibreWolf.x86_64.AppImage https://www.ebay.com

However, in LibreWolf version v96.0.3-2, the custom profile above doesn't succeed in launching URLs into new tabs.

Hopefully, the default LibreWolf profile can be modified to prevent this issue. In the meantime, I'd appreciate any suggestions of how I might modify the custom profile above to prevent the issue. Again, the custom profile above worked in v96.0.2-1, but doesn't prevent the issue in v96.0.3-2 .

Originally created by @Lonniebiz on GitHub (Feb 2, 2022). Original GitHub issue: https://github.com/netblue30/firejail/issues/4891 firejail version 0.9.64.4 Debian 11 LibreWolf [v96.0.3-2](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v96.0.3-2) This issue is similar to [one reported for Firefox](https://github.com/netblue30/firejail/issues/4670). A list of LibreWolf AppImages can be found [here](https://gitlab.com/librewolf-community/browser/appimage/-/releases). Here's the command I'm using to run LibreWolf: `firejail --appimage --profile=/etc/firejail/librewolf.profile ~/AppImages/LibreWolf.x86_64.AppImage` The problem occurs after first launch, when I'm trying to open additional web pages. For example, let's say LibreWolf is already running, and I want to open [Ebay](https://www.ebay.com) from the command line: `firejail --appimage --profile=/etc/firejail/librewolf.profile ~/AppImages/LibreWolf.x86_64.AppImage https://www.ebay.com` Instead of opening Ebay into a new tab, I get this error: ![LW](https://user-images.githubusercontent.com/151919/152204433-8623598b-5dc9-42ed-9967-75af612cc128.png) In a prior AppImage of LibreWolf, [version 96.0.2-1](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v96.0.2-1), I was able to get past this issue using a custom profile: **~/.config/firejail/librewolf.profile** ``` # Firejail profile for Librewolf # Description: Firefox fork based on privacy # This file is overwritten after every install/update # Persistent local customizations include librewolf.local # Persistent global definitions include globals.local noblacklist ${HOME}/.cache/librewolf noblacklist ${HOME}/.librewolf mkdir ${HOME}/.cache/librewolf mkdir ${HOME}/.librewolf whitelist ${HOME}/.cache/librewolf whitelist ${HOME}/.librewolf whitelist /usr/share/doc whitelist /usr/share/gtk-doc/html whitelist /usr/share/mozilla whitelist /usr/share/webext include whitelist-usr-share-common.inc dbus-user filter dbus-user.own org.mozilla.librewolf.* ignore dbus-user none # Redirect include firefox-common.profile ``` Then, I'd launch [v96.0.2-1](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v96.0.2-1) using the custom profile above: `firejail --appimage --profile=~/.config/firejail/librewolf.profile ~/AppImages/LibreWolf.x86_64.AppImage` Later, when I'd launch a URL (with LibreWolf already running), it would open that URL in a new tab with the following command: `firejail --appimage --profile=~/.config/firejail/librewolf.profile ~/AppImages/LibreWolf.x86_64.AppImage https://www.ebay.com` However, in [LibreWolf version v96.0.3-2](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v96.0.3-2), the custom profile above doesn't succeed in launching URLs into new tabs. Hopefully, the default LibreWolf profile can be modified to prevent this issue. In the meantime, I'd appreciate any suggestions of how I might modify the custom profile above to prevent the issue. Again, the custom profile above worked in [v96.0.2-1](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v96.0.2-1), but doesn't prevent the issue in [v96.0.3-2](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v96.0.3-2) .
gitea-mirror commented 2026-05-05 09:27:44 -06:00
Author
Owner
Copy link

@Lonniebiz commented on GitHub (Feb 2, 2022):

I've also brought this issue to the attention of the LibreWolf AppImage maintainers:
https://gitlab.com/librewolf-community/browser/appimage/-/issues/32

I don't think they're at fault for this issue, but I was hoping that they may be able to offer insight that leads to us making a fully functioning profile for LibreWolf v96.0.3-2.

<!-- gh-comment-id:1028197553 --> @Lonniebiz commented on GitHub (Feb 2, 2022): I've also brought this issue to the attention of the LibreWolf AppImage maintainers: https://gitlab.com/librewolf-community/browser/appimage/-/issues/32 I don't think they're at fault for this issue, but I was hoping that they may be able to offer insight that leads to us making a fully functioning profile for LibreWolf [v96.0.3-2](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v96.0.3-2).
gitea-mirror commented 2026-05-05 09:27:45 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Feb 2, 2022):

dbus-user.own io.gitlab.librewolf.*

Was org.mozilla.librewolf.* ever used? Yes f20e869fa4

<!-- gh-comment-id:1028231449 --> @rusty-snake commented on GitHub (Feb 2, 2022): ``` dbus-user.own io.gitlab.librewolf.* ``` Was `org.mozilla.librewolf.*` ever used? Yes https://gitlab.com/librewolf-community/browser/flatpak/-/commit/f20e869fa4e4fdd9471e53338b4b6dead04509b9
gitea-mirror commented 2026-05-05 09:27:46 -06:00
Author
Owner
Copy link

@Lonniebiz commented on GitHub (Feb 2, 2022):

In the custom profile, shown above. I changed the following line:
dbus-user.own org.mozilla.librewolf.*
to
dbus-user.own io.gitlab.librewolf.*

After closing LibreWolf, and relaunching LibreWolf v96.0.3-2 (with this modified custom profile), I again tried to open Ebay into a new tab with the following command:
firejail --appimage --profile=~/.config/firejail/librewolf.profile ~/AppImages/LibreWolf.x86_64.AppImage https://www.ebay.com

Instead of launching Ebay into a new tab, the same error occurred:
LW
@rusty-snake

<!-- gh-comment-id:1028266180 --> @Lonniebiz commented on GitHub (Feb 2, 2022): In the custom profile, shown above. I changed the following line: `dbus-user.own org.mozilla.librewolf.*` to `dbus-user.own io.gitlab.librewolf.*` After closing LibreWolf, and relaunching LibreWolf [v96.0.3-2](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v96.0.3-2) (with this modified custom profile), I again tried to open Ebay into a new tab with the following command: `firejail --appimage --profile=~/.config/firejail/librewolf.profile ~/AppImages/LibreWolf.x86_64.AppImage https://www.ebay.com` Instead of launching Ebay into a new tab, the same error occurred: ![LW](https://user-images.githubusercontent.com/151919/152219921-42b67568-7d43-46c9-809d-202a4a26450f.png) @rusty-snake
gitea-mirror commented 2026-05-05 09:27:47 -06:00
Author
Owner
Copy link

@Lonniebiz commented on GitHub (Jul 1, 2022):

firejail version: 0.9.64.4
Debian 11
LibreWolf (AppImage): v101.0.1-1

Last night I updated Debian 11 and noticed that the Firejail Profiles package got updated.

Today, this issue 4891 is happening again. It seems that the firejail profile has been updated in a manner that has forgotten about this issue.

Please reopen this issue until it gets fixed again.

<!-- gh-comment-id:1172476798 --> @Lonniebiz commented on GitHub (Jul 1, 2022): firejail version: 0.9.64.4 Debian 11 LibreWolf (AppImage): [v101.0.1-1](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v101.0.1-1) Last night I updated Debian 11 and noticed that the Firejail Profiles package got updated. Today, this issue 4891 is happening again. It seems that the firejail profile has been updated in a manner that has forgotten about this issue. Please reopen this issue until it gets fixed again.
gitea-mirror commented 2026-05-05 09:27:48 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Jul 1, 2022):

As I said in #5227 this is fixed!

If you run an old firejail version without the fix, cherry-pick it by hand into a .profile (in /etc/firejail) and update the packages, this is expect and not your bug.

If nobody can show that this is still an issue with firejail 0.9.68 I'm going to close this again (tomorrow).

<!-- gh-comment-id:1172669137 --> @rusty-snake commented on GitHub (Jul 1, 2022): As I said in #5227 this is fixed! If you run an old firejail version without the fix, cherry-pick it by hand into a .profile (in /etc/firejail) and update the packages, this is expect and not your bug. If nobody can show that this is still an issue with firejail 0.9.68 I'm going to close this again (tomorrow).
gitea-mirror commented 2026-05-05 09:27:48 -06:00
Author
Owner
Copy link

@kmk3 commented on GitHub (Jul 1, 2022):

@Lonniebiz commented on Jul 1:

firejail version: 0.9.64.4 Debian 11 LibreWolf (AppImage):
v101.0.1-1

Last night I updated Debian 11 and noticed that the Firejail Profiles package
got updated.

Today, this issue 4891 is happening again. It seems that the firejail profile
has been updated in a manner that has forgotten about this issue.

Please reopen this issue until it gets fixed again.

Again, please follow the bug report template. The information in the
template might be needed for debugging, so if that is missing, your issue is
more likely to be ignored.

Also, checking the latest profile version is part of the checklist:

  • The profile (and redirect profile if exists) hasn't already been fixed upstream.

If the latest version indeed solves the issue (as @rusty-snake mentioned), just
going through the checklist could have led you directly to the fix and avoided
reopening this issue.

Lastly, aside from the template, is LibreWolf running under wayland or Xorg?

<!-- gh-comment-id:1172701961 --> @kmk3 commented on GitHub (Jul 1, 2022): @Lonniebiz commented [on Jul 1](https://github.com/netblue30/firejail/issues/4891#issuecomment-1172476798): > firejail version: 0.9.64.4 Debian 11 LibreWolf (AppImage): > [v101.0.1-1](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v101.0.1-1) > > Last night I updated Debian 11 and noticed that the Firejail Profiles package > got updated. > > Today, this issue 4891 is happening again. It seems that the firejail profile > has been updated in a manner that has forgotten about this issue. > > Please reopen this issue until it gets fixed again. [Again][1], please follow the [bug report template][2]. The information in the template might be needed for debugging, so if that is missing, your issue is more likely to be ignored. Also, checking the latest profile version is part of the checklist: > - [ ] The profile (and redirect profile if exists) hasn't already been fixed [upstream](https://github.com/netblue30/firejail/tree/master/etc). If the latest version indeed solves the issue (as @rusty-snake mentioned), just going through the checklist could have led you directly to the fix and avoided reopening this issue. Lastly, aside from the template, is LibreWolf running under wayland or Xorg? [1]: https://github.com/netblue30/firejail/issues/4670#issuecomment-962522511 [2]: https://github.com/netblue30/firejail/issues/new?assignees=&labels=&template=bug_report.md&title=
gitea-mirror commented 2026-05-05 09:27:49 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Jul 1, 2022):

https://github.com/netblue30/firejail/issues/5227#issuecomment-1172703949

<!-- gh-comment-id:1172716880 --> @rusty-snake commented on GitHub (Jul 1, 2022): https://github.com/netblue30/firejail/issues/5227#issuecomment-1172703949
gitea-mirror commented 2026-05-05 09:27:49 -06:00
Author
Owner
Copy link

@kmk3 commented on GitHub (Jul 1, 2022):

@rusty-snake commented on Jul 1:

#5227 (comment)

For reference:

@Lonniebiz commented on Jul 1:

In Debian 11, I opened this file: /etc/apt/sources.list

And added this line to it: deb http://deb.debian.org/debian
bullseye-backports main

Then, I upgraded filejail to version 0.9.70 : sudo apt update ; sudo apt
install firejail/bullseye-backports firejail-profiles/bullseye-backports

After, this I relaunched the LibreWolf AppImage
using firejail and now the issue is resolved; I can launch additional pages
in new tabs.

<!-- gh-comment-id:1172717978 --> @kmk3 commented on GitHub (Jul 1, 2022): @rusty-snake commented [on Jul 1](https://github.com/netblue30/firejail/issues/4891#issuecomment-1172716880): > [#5227 (comment)](https://github.com/netblue30/firejail/issues/5227#issuecomment-1172703949) For reference: @Lonniebiz commented [on Jul 1](https://github.com/netblue30/firejail/issues/5227#issuecomment-1172703949): > **In Debian 11, I opened this file:** /etc/apt/sources.list > > **And added this line to it:** deb http://deb.debian.org/debian > bullseye-backports main > > **Then, I upgraded filejail to version 0.9.70 :** sudo apt update ; sudo apt > install firejail/bullseye-backports firejail-profiles/bullseye-backports > > After, this I relaunched the LibreWolf [AppImage](https://gitlab.com/librewolf-community/browser/appimage/-/releases/v101.0.1-1) > using firejail and now the issue is resolved; I can launch additional pages > in new tabs.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear labels   
LTS merge

   
LTS merge

   
bug

   
bug

   
converted-to-discussion

   
doc-todo

   
documentation

   
duplicate

   
enhancement

   
file-transfer

   
firecfg

   
firejail-in-firejail

   
firetools

   
graphics

   
help wanted

   
information_old

   
installation

   
invalid

   
modif

   
moved

   
needinfo

   
networking

   
notabug

   
notourbug

   
old-version

   
overlayfs

   
packaging

   
profile-request

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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: github-starred/firejail#2804
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?