[GH-ISSUE #2767] qTox: hangs after launch in Arch Linux due to memory-deny-write-execute #1740

New issue

Closed

opened 2026-05-05 08:24:37 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 08:24:37 -06:00

Owner

Originally created by @grizzlyuser on GitHub (Jun 13, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2767

$ firejail --version
firejail version 0.9.60

Compile time support:
	- AppArmor support is enabled
	- AppImage support is enabled
	- chroot support is enabled
	- file and directory whitelisting support is enabled
	- file transfer support is enabled
	- networking support is enabled
	- overlayfs support is enabled
	- private-home support is enabled
	- seccomp-bpf support is enabled
	- user namespace support is enabled
	- X11 sandboxing support is enabled

Linux Distributions: Arch Linux, Parabola GNU/Linux-libre

firejail qtox starts the process, but the main application window doesn't show up.

Works fine if memory-deny-write-execute is commented in /etc/firejail/qtox.profile. Seems to be related to issue #1803.

The problem didn't exist in the previous release of firejail. As I understood, that was due to addition of memory-deny-write-execute after it.

Tested in Gnome@Wayland and KDE Plasma@Xorg

Originally created by @grizzlyuser on GitHub (Jun 13, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2767 ``` $ firejail --version firejail version 0.9.60 Compile time support: - AppArmor support is enabled - AppImage support is enabled - chroot support is enabled - file and directory whitelisting support is enabled - file transfer support is enabled - networking support is enabled - overlayfs support is enabled - private-home support is enabled - seccomp-bpf support is enabled - user namespace support is enabled - X11 sandboxing support is enabled ``` Linux Distributions: Arch Linux, Parabola GNU/Linux-libre `firejail qtox` starts the process, but the main application window doesn't show up. Works fine if `memory-deny-write-execute` is commented in `/etc/firejail/qtox.profile`. Seems to be related to issue #1803. The problem didn't exist in the previous release of firejail. As I understood, that was due to addition of `memory-deny-write-execute` after it. Tested in Gnome@Wayland and KDE Plasma@Xorg

gitea-mirror closed this issue

2026-05-05 08:24:38 -06:00

gitea-mirror commented

2026-05-05 08:24:39 -06:00

Author

Owner

@ghost commented on GitHub (Jun 13, 2019):

@grizzlyuser Should be fixed now. Thanks for reporting it!

@ghost commented on GitHub (Jun 13, 2019): @grizzlyuser Should be fixed now. Thanks for reporting it!

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#1740

No description provided.

Rows
Columns