mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #5601] qutebrowser: links do not open in the existing instance #3037
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#3037
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @aleprovencio on GitHub (Jan 18, 2023).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5601
Description
Until upgrading
firejailto this last release, I used to open links on external apps and they would open on a newqutebrowsertab.Steps to Reproduce
Steps to reproduce the behavior
qutebrowserkitty'sopen_url_with_hintsExpected behavior
The link would open a new tab of the already running
qutebrowserinstanceActual behavior
A new
qutebrowserinstance is opened with the linkBehavior without a profile
The same happens
Additional context
I've had to make other adjustments on my
qutebrowser.localas well after this upgrade, but couldn't figure this one out. I've tried things likeignore dbus-system noneanddbus-user.own org.qutebrowser.*without success.Environment
Checklist
/usr/bin/vlc) "fixes" it).https://github.com/netblue30/firejail/issues/1139)browser-allow-drm yes/browser-disable-u2f noinfirejail.configto allow DRM/U2F in browsers.--profile=PROFILENAMEto set the right profile. (Only relevant for AppImages)Log
Output of
LC_ALL=C firejail /path/to/program@ghost commented on GitHub (Jan 18, 2023):
It would be helpful if you could post your
qutebrowser.localhere. I'm asuming you've addedinclude allow-lua.incto that for some reason, as that isn't in /etc/firejail/qutebrowser.profile. You also have awhitelist-common.localaccording to the above output. Please post that as well.I'm not normally using qutebrowser on my Arch Linux box, but I do have it installed to work on its profile on occasion. IMO it's unlikely this is D-Bus related. Very few applications need access to the system bus, and AFAICT qutebrowser doesn't expose any D-Bus addresses of its own (checked with d-feet). Without additional info my only advice at the moment is to disable the newly added options (one by one) from the 0.9.72 qutebrowser.profile so you can get as close as possible to the former 0.9.70 version that used to work for you.
Potential culprits:
@aleprovencio commented on GitHub (Jan 19, 2023):
Thank you for your help. Below are my local files, I hope comments are self-explanatory of my doings.
whitelist-common.local
qutebrowser.local
@rusty-snake commented on GitHub (Jan 19, 2023):
IIRC qutebrowser now has
apparmor.Also, if you only need
${HOME}executable you can be more specific. So try to replace this line with@The-Compiler commented on GitHub (Jan 24, 2023):
qutebrowser upstream here - this is related to qutebrowser not being able to access its unix socket in
/run/user/$UID/qutebrowser/ipc-<hash>. An user reported that they get:when starting qutebrowser, which means qutebrowser then opens in a new process.
2 seems to be
QLocalSocket::ServerNotFoundError, i.e. I suppose it got anENOENTfor that file.@Dieterbe commented on GitHub (Jan 24, 2023):
could be due to #5389 ?
@ghost commented on GitHub (Jan 24, 2023):
@The-Compiler @Dieterbe Thanks for the info! It looks like we need an additional
in qutebrowser.profile.
@aleprovencio Can you confirm your issue is fixed when adding that to your
qutebrowser.local? I'll fix it in master when you confirm it solves it. Or you can open a PR yourself.@rusty-snake commented on GitHub (Jan 24, 2023):
Remember to
mkdirit too.@aleprovencio commented on GitHub (Jan 25, 2023):
It does work, thank you all for your time
@Dieterbe commented on GitHub (Jan 26, 2023):
Thank you! open source power !! 👯