[GH-ISSUE #2840] memory-deny-write-execute breaks several applications #1776

Closed
opened 2026-05-05 08:26:42 -06:00 by gitea-mirror · 13 comments
Owner

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.

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.
Author
Owner

@rusty-snake commented on GitHub (Jul 8, 2019):

Fixed in 704fc8b, Thanks for reporting.

<!-- gh-comment-id:509229017 --> @rusty-snake commented on GitHub (Jul 8, 2019): Fixed in 704fc8b, Thanks for reporting.
Author
Owner

@setpill commented on GitHub (Jul 9, 2019):

Thanks for the quick response :)

<!-- gh-comment-id:509542695 --> @setpill commented on GitHub (Jul 9, 2019): Thanks for the quick response :)
Author
Owner

@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 😄

<!-- gh-comment-id:509836579 --> @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 :smile:
Author
Owner

@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.

<!-- gh-comment-id:509838651 --> @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](https://ci.debian.net/packages/f/firejail/unstable/amd64/) and [Ubuntu CI](http://autopkgtest.ubuntu.com/packages/f/firejail).
Author
Owner

@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 mdwe is unreliable in gtk/qt apps and perhaps in all gui apps and shouldn't be used there.

<!-- gh-comment-id:510096466 --> @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 `mdwe` is unreliable in gtk/qt apps and perhaps in all gui apps and shouldn't be used there.
Author
Owner

@Fred-Barclay commented on GitHub (Jul 10, 2019):

@Vincent43 I'm inclined to agree but I'd really like using mdwe as much as possible 😄 . Isn't Arch the distro that usually has issues with it?

<!-- gh-comment-id:510108875 --> @Fred-Barclay commented on GitHub (Jul 10, 2019): @Vincent43 I'm inclined to agree but I'd really like using `mdwe` as much as possible :smile: . Isn't Arch the distro that usually has issues with it?
Author
Owner

@rusty-snake commented on GitHub (Jul 10, 2019):

Isn't Arch the distro that usually has issues with it?

We need ?IS_ARCH: mdwe ?NOT_ARCH: mdwe 😺

Yes if an app works fine with mdwe except on some distors, it is normaly Arch, Manjaro, ...

<!-- gh-comment-id:510113048 --> @rusty-snake commented on GitHub (Jul 10, 2019): > Isn't Arch the distro that usually has issues with it? _We need ~`?IS_ARCH: mdwe`~ `?NOT_ARCH: mdwe` :smiley_cat:_ Yes if an app works fine with `mdwe` except on some distors, it is normaly Arch, Manjaro, ...
Author
Owner

@Vincent43 commented on GitHub (Jul 10, 2019):

It would be interesting to find out what's causing the difference there.

<!-- gh-comment-id:510148194 --> @Vincent43 commented on GitHub (Jul 10, 2019): It would be interesting to find out what's causing the difference there.
Author
Owner

@rusty-snake commented on GitHub (Jul 10, 2019):

$ grep -l "#1803" *
authenticator.profile
autokey-common.profile
baobab.profile
bitwarden.profile
clawsker.profile
d-feet.profile
enpass.profile
eo-common.profile
exfalso.profile
font-manager.profile
galculator.profile
geekbench.profile
mpDris2.profile
mumble.profile
ocenaudio.profile
pavucontrol.profile
QMediathekView.profile
qtox.profile
subdownloader.profile
viewnior.profile
youtube-dl.profile

ytdl not only GUI.

BTW: Should we reopen?

<!-- gh-comment-id:510152501 --> @rusty-snake commented on GitHub (Jul 10, 2019): ``` $ grep -l "#1803" * authenticator.profile autokey-common.profile baobab.profile bitwarden.profile clawsker.profile d-feet.profile enpass.profile eo-common.profile exfalso.profile font-manager.profile galculator.profile geekbench.profile mpDris2.profile mumble.profile ocenaudio.profile pavucontrol.profile QMediathekView.profile qtox.profile subdownloader.profile viewnior.profile youtube-dl.profile ``` **ytdl** not only GUI. BTW: Should we reopen?
Author
Owner

@setpill commented on GitHub (Jul 11, 2019):

If a bug is reopened, it would make more sense to reopen #1803 than this one.

<!-- gh-comment-id:510377298 --> @setpill commented on GitHub (Jul 11, 2019): If a bug is reopened, it would make more sense to reopen #1803 than this one.
Author
Owner

@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?

<!-- gh-comment-id:510418580 --> @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?
Author
Owner

@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.

<!-- gh-comment-id:511124583 --> @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.
Author
Owner

@topimiettinen commented on GitHub (Jul 13, 2019):

OK, that was added in March 2019, 59e3061.

<!-- gh-comment-id:511144845 --> @topimiettinen commented on GitHub (Jul 13, 2019): OK, that was added in March 2019, 59e3061.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1776
No description provided.