mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4711] telegram-desktop: screen sharing doesn't work #2763
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#2763
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 @reagentoo on GitHub (Nov 24, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4711
Description
Can't force telegram-desktop to share the screen in firejail.
Steps to Reproduce
Steps to reproduce the behavior
Expected behavior
Screen sharing
Actual behavior
Don't see captured screen preview, caller doesn't see my screen.
Behavior without a profile
Additional context
Environment
firejail --version):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/programOutput of
LC_ALL=C firejail --debug /path/to/program@rusty-snake commented on GitHub (Nov 24, 2021):
Try
dbus-user.talk org.freedesktop.portal.*and if this does not workignore norootin addition. edit: andwhitelist /usr/share/pipewirebecause of firejail <= 0.9.67.@reagentoo commented on GitHub (Nov 24, 2021):
Still doesn't work. 😩
Also tried
dbus-user.own org.telegram.desktop.*,whitelist /usr/share/pipewire/client.conf,dbus-user.talk org.freedesktop.portal.Desktop(/home/user/.config/firejail/telegram.local)
@rusty-snake commented on GitHub (Nov 24, 2021):
Did you tried with
ignore noroottoo?If it still does not work, you need to comment stuff until it works to near it down (dbus? private-etc?, ...).
@reagentoo commented on GitHub (Nov 24, 2021):
Exactly.
Also tried. 😩😩
@rusty-snake commented on GitHub (Nov 24, 2021):
But with
--noprofileit works, right? Then comment everything and uncomment it line for line.@reagentoo commented on GitHub (Nov 24, 2021):
I've done the next steps:
#include whitelist-runuser-common.incOnly with these conditions was it possible to make it work.
@reagentoo commented on GitHub (Nov 24, 2021):
It seems this part was fixed in f-jail upstream:
5d3e0e812b/etc/inc/whitelist-runuser-common.inc (L13-L14)I've added this lines to .config/firejail/whitelist-runuser-common.local:
And got good result.
P.S.: why firejail releases take so long ????
@rusty-snake commented on GitHub (Nov 25, 2021):
I always ask myself that too. At least for profiles some kind of weekly snapshots would make sense IMHO. It would be still an issues if a newer firejail versions introduces new commands (e.g.
noinputor dbus filtering) which are used by profiles and you "import" them into an older firejail version. That's something to solve, but it is not impossible. Also it would allow some kind a testing set installed and tested by much more users. You could then for example do things like "We think it is ok to add foo to bar.profile but let's test this". ATM this is risky, given that a if you release a broken profile into the firejail version used by debian stable, it could take years until users get a working profile.