mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3842] Cannot launch Teams on POP!_OS 20.10 #2420
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#2420
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 @etnx on GitHub (Dec 21, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3842
Problem occurs in : Pop!_OS 20.10 (linux kernel is 5.8.0-7630-generic)
No profile and disabling firejail
What changed calling
firejail --noprofile /path/to/programin a terminal?==> Everything OK
What changed calling the program by path (check
which <program>orfirejail --listwhile the sandbox is running)?Output :
12511:me::firejail --noprofile /usr/bin/teamsEnvironment
Firejail version : 0.9.62.4
Additional context
Date :
The problem occured on november 18.
Before this date, I had no problem using teams with firejail.
In /var/log/syslog :
debug.txt
@rusty-snake commented on GitHub (Dec 21, 2020):
Very likely fixed on master by
a37c7d4e7e (diff-535ce7031241d60504a4a23009358ed4ab07957e52cb45d9b8ac4bef9ff8c8b7)3e7c483044 (diff-535ce7031241d60504a4a23009358ed4ab07957e52cb45d9b8ac4bef9ff8c8b7)f4f6767458 (diff-535ce7031241d60504a4a23009358ed4ab07957e52cb45d9b8ac4bef9ff8c8b7)Read #3795 for better understanding of these changes.
If POP!_OS has AppArmor, also
9738b20511 (diff-535ce7031241d60504a4a23009358ed4ab07957e52cb45d9b8ac4bef9ff8c8b7).@etnx commented on GitHub (Dec 22, 2020):
I already ignored apparmor. I have updated (from Master branch) electron, firejail and firejail-for-linux profiles on my system (because of refactoring).
Now :
Warning: networking feature is disabled in Firejail configuration filedebug.txt
@rusty-snake commented on GitHub (Dec 22, 2020):
You need to update firejail as well, if you copy the profiles from master.
Which one do you use? teams or teams-for-linux?
@szemy commented on GitHub (Jan 14, 2021):
I have a similar issue on Arch:
In firejail Log: https://pastebin.com/wKPHB7v6
dmesg: https://pastebin.com/p97DdYDD
Version: 0.9.64
The teams.profile : https://pastebin.com/67xCJxqx
@rusty-snake commented on GitHub (Jan 15, 2021):
Fixed by:
a37c7d4e7e (diff-535ce7031241d60504a4a23009358ed4ab07957e52cb45d9b8ac4bef9ff8c8b7)3e7c483044 (diff-535ce7031241d60504a4a23009358ed4ab07957e52cb45d9b8ac4bef9ff8c8b7)f4f6767458 (diff-535ce7031241d60504a4a23009358ed4ab07957e52cb45d9b8ac4bef9ff8c8b7)f4f6767458 (diff-046ffcfd2a399dd76a2a4d5220f83814a89dc2bd059b2e2c0fd089e1db06dec9)@kris7t commented on GitHub (Jan 15, 2021):
@rusty-snake Doesn't this defeat the point of using AppArmor along with Firejail? Instead of
ignore apparmor, I think something likein an appropriate AppArmor profile would be more secure (although it does raise the question how to add and maintain such profile modifications, since it goes a bit against using a single AppArmor profile for all of firejail).
@ghost commented on GitHub (Jan 15, 2021):
Perhaps we could add a note in teams.profile that AppArmor users better add the above rule to their
/etc/apparmor.d/local/firejail-default,which is the recommended AA override location.@rusty-snake commented on GitHub (Apr 6, 2021):
I'm closing here due to inactivity, please fell free to request to reopen if you still have this issue.