librewolf: cannot open new URLs into running instance 3 #6413
Comments
|
FYI, Librewolf offers .deb files: https://librewolf.net/installation/debian/. Can you test if your issue changes when you don't use an AppImage? |
kmk3
changed the title
|
Basic debugging information is missing; please follow the bug report template: |
|
Does it still happen with firejail-git? What is the output in trace.txt in the following command? firejail --trace=trace.txt --appimage \
--profile=/etc/firejail/librewolf.profile \
~/AppImages/LibreWolf.x86_64.AppImage https://www.ebay.com |
|
@kmk3 : After initially launching LibreWolf successfully, here's the output of the command you provided (that fails to open Ebay into a new tab):
This wasn't an issue in the previous version of LibreWolf (v127.0-2), it only started happening again (#4891, #5227) in the latest v128.0-2. I think significant changes were made to LibreWolf starting in version 128.0-2. I say this because after downgrading back to v127.0.2-2, I got a message upon launch saying that I could no longer load my browser-profile touched by v128.0-2. 128.0-2 apparently modified my browser-profile in a manner where v127.0.2-2 could no longer read it. I had to restore my LibreWolf browser-profile from a backup before I could load it again in v127.0.2-2. For applications not in the debian repository, I only run AppImages (with FireJail), and I avoid installing .deb files from websites. However, I did attempt to grant your request of testing a .deb install of LibreWolf in a VM; Launching without firejail worked, but I couldn't get firejail to launch the deb installed version. Hopefully, this is a separate issue that can just be avoided due to the other info I've provided. |
|
Try using Please note that the use of This works in firefox and I even wrote a python script wrapper for firejail to handle all this. I have a handler/wrapper sitting at /usr/bin/firefox to make all the commands and my options and translates then runs all commands for firejail and firefox. HA, if that makes sense. So whenever a program or a GUI wants to open a webpage, it is always sandbox'd and working, creating new windows or tabs. |
|
@stormtheory : I tried using |
|
@Lonniebiz I just tried this and it worked in Firefox. In your librewolf.profile make sure of the following is set in order for it to talk on the dbus or the instances won't be able to talk: Run commands like this but with your profile and LibreWolf command. I'm able to open many tabs from different terminals to one sandbox. https://github.com/stormtheory/firefox-firejail-wrapper |
|
@stormtheory : My custom profile does indeed contain: dbus-user filter The difference is that I'm specifically trying to accomplish this using the latest AppImage of LibreWolf (version 129.0.2-1) which is located here: So, when I try the arguments you're suggesting, with this exact AppImage, they look like this: Yet, upon running the 2nd command, I'm getting the error I screen captured in a prior post. I simply can't launch new tabs from the command line. Previously, in LibreWolf v127.0-2 AppImage, I was able to launch new tabs from the command line without getting that error (even without |
kmk3
changed the title
|
#4897 added Does it work if you remove all dbus-related entries from all the relevant I'd try using something like busctl or d-feet to inspect what dbus commands |
|
What is the dbus name returned in the following? It appears as Does it work with the following in librewolf.local? |
It appears that LibreWolf 129 uses `io.gitlab.firefox.*` as the dbus
name.
Commands used to check the dbus name:
$ busctl --user --no-legend | grep -v '^:' | grep librewolf |
sed -E 's/(^[^ ]+\.)[^. ]+ .*/\1/'
io.gitlab.firefox.
Commands used to test dbus communication:
# Open a new browser instance:
$ firejail --name=lwtest --ignore=name --ignore='dbus-user none' \
--dbus-user=filter --dbus-user.own='io.gitlab.firefox.*' \
--private --net=none --ignore=net /usr/bin/librewolf
# In another shell, try to open a new tab:
$ firejail --join=lwtest /usr/bin/librewolf --new-tab about:blank
# Check that the new tab was opened
Related commits:
* c3f2996 ("Let programs outside librewolf sandbox open new tabs in
librewolf (netblue30#4546)", 2021-09-19)
* a8ad9ca ("Update librewolf.profile: use new message bus",
2022-02-03) / PR netblue30#4897
* 4211ee3 ("merges", 2022-02-04)
Fixes netblue30#6413.
Misc: This was noticed on netblue30#6444.
Reported-by: @Lonniebiz
|
@kmk3 Thank you so much for taking the time to reproduce my issue and fix it. I confirm that after adding How long do you expect it will take before your changes land in Debian 12? Once there, I'll likely switch back to using the default profile. |
All good, thanks for confirming.
Personally I'm working on a few fixes for new features before they ship. Then the idea is to work on the release itself. No ETA though. |
It appears that LibreWolf 129 uses `io.gitlab.firefox.*` as the dbus
name.
Commands used to check the dbus name:
$ busctl --user --no-legend | grep -v '^:' | grep librewolf |
sed -E 's/(^[^ ]+\.)[^. ]+ .*/\1/'
io.gitlab.firefox.
Commands used to test dbus communication:
# Open a new browser instance:
$ firejail --name=lwtest --ignore=name --ignore='dbus-user none' \
--dbus-user=filter --dbus-user.own='io.gitlab.firefox.*' \
--private --net=none --ignore=net /usr/bin/librewolf
# In another shell, try to open a new tab:
$ firejail --join=lwtest /usr/bin/librewolf --new-tab about:blank
# Check that the new tab was opened
Related commits:
* c3f2996 ("Let programs outside librewolf sandbox open new tabs in
librewolf (netblue30#4546)", 2021-09-19)
* a8ad9ca ("Update librewolf.profile: use new message bus",
2022-02-03) / PR netblue30#4897
* 4211ee3 ("merges", 2022-02-04)
Fixes netblue30#6413.
Misc: This was noticed on netblue30#6444.
Reported-by: @Lonniebiz
Firejail Version: 0.9.72
Debian 12
LibreWolf AppImage 128.0-2:
This issue was previously fixed in #4891 and #5227. Yet after upgrading to LibreWolf AppImage 128.0-2 the problem has returned.
Here's the command I'm using to run LibreWolf:
firejail --appimage --profile=/etc/firejail/librewolf.profile ~/AppImages/LibreWolf.x86_64.AppImageThe 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.comInstead of opening Ebay into a new tab, I get this error:
"Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile."The text was updated successfully, but these errors were encountered: