mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4784] telegram: cannot open links in browser #2776
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#2776
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 @YorkZ on GitHub (Dec 19, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4784
Description
Unable to open hyperlinks in Telegram
Steps to Reproduce
telegram-desktopExpected behavior
The link should be opened in the web browser.
Actual behavior
The link isn't opened
Behavior without a profile
The link gets opened in the web browser when clicking it in Telegram.
Additional context
The issue went away after
noblacklistbashandsh:And I've open PR #4783 as a proposal to address the issue.
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 telegram-desktop@ghost commented on GitHub (Dec 19, 2021):
Aha, I think I see where the confusion discussed in PR #4783 stems from. As you state, your using firejail 0.9.66 on Arch Linux. That version indeed does not have
private-binenabled. That's brought in recently via this commit, so my earlier assumptions were off here. There have been other changes to telegram.profile since 0.9.66-3 from the official Arch Linux repo, regarding D-Bus. Here's my suggestion. Until we cut a new release you can add your needed fixes to a telegram.local override. For the PR you'll need to additionally addbash,shandxdg-opento the now enabledprivate-bin. I'll add a comment about this to the PR too.Hope this clears up the confusion. And thanks for reporting!
@YorkZ commented on GitHub (Dec 19, 2021):
@glitsj16 Yep, I figured this out and have updated in the PR #4783 discussion. Could you check my comments there?
@ghost commented on GitHub (Dec 19, 2021):
@YorkZ I just merged your PR and added credits to the README. Thanks again for your efforts and reporting. I'll close this but feel free to re-open if the issue returns.
Regards
@YorkZ commented on GitHub (Dec 19, 2021):
Thanks a lot for your help.