-
Notifications
You must be signed in to change notification settings - Fork 595
qutebrowser: links do not open in the existing instance #5601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It would be helpful if you could post your 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:
|
Thank you for your help. Below are my local files, I hope comments are self-explanatory of my doings. whitelist-common.local
qutebrowser.local
|
IIRC qutebrowser now has
|
qutebrowser upstream here - this is related to qutebrowser not being able to access its unix socket in
when starting qutebrowser, which means qutebrowser then opens in a new process. 2 seems to be |
could be due to #5389 ? |
@The-Compiler @Dieterbe Thanks for the info! It looks like we need an additional
@aleprovencio Can you confirm your issue is fixed when adding that to your |
Remember to |
Addresses issue netblue30#5601
It does work, thank you all for your time |
Thank you! open source power !! 👯 |
Description
Until upgrading
firejail
to this last release, I used to open links on external apps and they would open on a newqutebrowser
tab.Steps to Reproduce
Steps to reproduce the behavior
qutebrowser
kitty
'sopen_url_with_hints
Expected behavior
The link would open a new tab of the already running
qutebrowser
instanceActual behavior
A new
qutebrowser
instance is opened with the linkBehavior without a profile
The same happens
Additional context
I've had to make other adjustments on my
qutebrowser.local
as well after this upgrade, but couldn't figure this one out. I've tried things likeignore dbus-system none
anddbus-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 no
infirejail.config
to allow DRM/U2F in browsers.--profile=PROFILENAME
to set the right profile. (Only relevant for AppImages)Log
Output of
LC_ALL=C firejail /path/to/program
The text was updated successfully, but these errors were encountered: