mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1541] seccomp: kmail started to freeze with seccomp and tracelog #1029
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#1029
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 @msva on GitHub (Sep 8, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1541
I've just faced the problem that KMail freezing on start with it's current profile (with enabled
seccompandtracelog).Disabling
seccomp, but keepingtracelogmakes it segfault (or whateverReceived signal 11 SEGV_MAPERR 000000000338means, and still be freezed),Disabling
tracelogkeepingseccomp- change nothing (it still freezes on start)Commenting both lines makes it start normally again.
Although, I'm not sure why do this started to happen only now, while both seccomp and tracelog exists in the kmail profile for more that year already...
@netblue30 commented on GitHub (Sep 13, 2017):
I'll take a look, thanks.
@curiosity-seeker commented on GitHub (Sep 19, 2017):
Same problem here. Kmail 17.04 on Fedora 26 runs well with
and
tracelogdisabled. Once I enable it I got the same segfault as @msva :EDIT: After adding tgkill and alarm to seccomp.keep I get the following complete output:
@smitsohu commented on GitHub (Dec 9, 2017):
@msva and @curiosity-seeker, can one of you confirm it is working with latest commit on git?
@smitsohu commented on GitHub (Dec 10, 2017):
Reason for chroot is that KMail now has a sandboxed renderer process.
tracelogis also not working with the Chromium sandbox, see #197.@curiosity-seeker commented on GitHub (Dec 18, 2017):
@smitsohu : I'm sorry that I'm not able to test it right now. You have to wait until January - sorry :-(
@smitsohu commented on GitHub (Dec 21, 2017):
@curiosity-seeker no worries! I just see that anyways your
seccomp.keepalready accounts for it (should have checked that earlier).@chiraag-nataraj commented on GitHub (Aug 20, 2018):
These fixes made it into master, so I'm going to close this for now. If there are any issues, please feel free to re-open.