mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2840] memory-deny-write-execute breaks several applications #1776
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#1776
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 @setpill on GitHub (Jul 8, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2840
At least mumble, galculator and pavucontrol are affected.
@rusty-snake commented on GitHub (Jul 8, 2019):
Fixed in
704fc8b, Thanks for reporting.@setpill commented on GitHub (Jul 9, 2019):
Thanks for the quick response :)
@Fred-Barclay commented on GitHub (Jul 9, 2019):
It would be great if we could test graphical programs in our CI to catch errors like this... any ideas if this is possible?
CC: @reinerh since you've been working on our CI recently 😄
@reinerh commented on GitHub (Jul 9, 2019):
@Fred-Barclay Yes, it would be possible. I think the tests (in test/ directory) already run some graphical programs.
It would be easy to run all tests also in our CI, but for now I didn't enable it, as it's a bit unrealiable.
See e.g. in Debian CI and Ubuntu CI.
@Vincent43 commented on GitHub (Jul 10, 2019):
We obviously can't test all graphical apps in CI, especially across various distros. The truth is that
mdweis unreliable in gtk/qt apps and perhaps in all gui apps and shouldn't be used there.@Fred-Barclay commented on GitHub (Jul 10, 2019):
@Vincent43 I'm inclined to agree but I'd really like using
mdweas much as possible 😄 . Isn't Arch the distro that usually has issues with it?@rusty-snake commented on GitHub (Jul 10, 2019):
We need
?IS_ARCH: mdwe?NOT_ARCH: mdwe😺Yes if an app works fine with
mdweexcept on some distors, it is normaly Arch, Manjaro, ...@Vincent43 commented on GitHub (Jul 10, 2019):
It would be interesting to find out what's causing the difference there.
@rusty-snake commented on GitHub (Jul 10, 2019):
ytdl not only GUI.
BTW: Should we reopen?
@setpill commented on GitHub (Jul 11, 2019):
If a bug is reopened, it would make more sense to reopen #1803 than this one.
@topimiettinen commented on GitHub (Jul 11, 2019):
Regarding Arch specific breakage: recently mdwe was enhanced to block also
memfd_create()system call. Maybe a library in Arch has started using it?@setpill commented on GitHub (Jul 13, 2019):
How recent is that enhancement? #1803 was opened in March 2018 so if it's after that it is not the (only) cause.
@topimiettinen commented on GitHub (Jul 13, 2019):
OK, that was added in March 2019,
59e3061.