[GH-ISSUE #3775] zathura does not work with ipc-namespace #2377

New issue

Closed

opened 2026-05-05 09:03:37 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 09:03:37 -06:00

Owner

Originally created by @ScoreUnder on GitHub (Nov 26, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3775

Bug and expected behavior
ipc-namespace does not allow zathura to run.

No profile and disabling firejail
ignore ipc-namespace is sufficient to fix the issue, but more minimal profiles work for the same reason.

Reproduce

Run zathura under firejail
Observe the failure to launch, and the error:

(org.pwmt.zathura:12): Gdk-ERROR **: 16:50:29.070: The program 'org.pwmt.zathura' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
  (Details: serial 294 error_code 10 request_code 130 (MIT-SHM) minor_code 1)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

This also occurs with --x11=xpra, --x11=xvfb, and --x11=xephyr. --x11=none will not work because it requires X11, and --x11=xorg has never worked on my machine.

Environment

zathura 0.4.7-1
nvidia-dkms 455.38-1
linux 5.9.3.arch1-1
firejail 0.9.64-2

Debug output available if necessary but it doesn't describe the actual issue (the difference between ignore ipc-namespace and not amounts to order of profile loading, whether ipc namespaces are reported as enabled, mountpoint IDs, and the error output seen above).

Originally created by @ScoreUnder on GitHub (Nov 26, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3775 **Bug and expected behavior** `ipc-namespace` does not allow zathura to run. **No profile and disabling firejail** `ignore ipc-namespace` is sufficient to fix the issue, but more minimal profiles work for the same reason. **Reproduce** 1. Run zathura under firejail 2. Observe the failure to launch, and the error: ``` (org.pwmt.zathura:12): Gdk-ERROR **: 16:50:29.070: The program 'org.pwmt.zathura' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAccess (attempt to access private resource denied)'. (Details: serial 294 error_code 10 request_code 130 (MIT-SHM) minor_code 1) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ``` This also occurs with `--x11=xpra`, `--x11=xvfb`, and `--x11=xephyr`. `--x11=none` will not work because it requires X11, and `--x11=xorg` has never worked on my machine. **Environment** - zathura 0.4.7-1 - nvidia-dkms 455.38-1 - linux 5.9.3.arch1-1 - firejail 0.9.64-2 Debug output available if necessary but it doesn't describe the actual issue (the difference between `ignore ipc-namespace` and not amounts to order of profile loading, whether ipc namespaces are reported as enabled, mountpoint IDs, and the error output seen above).

gitea-mirror closed this issue

2026-05-05 09:03:38 -06:00

gitea-mirror commented

2026-05-05 09:03:40 -06:00

Author

Owner

@rusty-snake commented on GitHub (Nov 26, 2020):

Thanks for reporting. ipc-namespace breaks some X-extensions and causes frequently issues with gui programs. That's why it should not be used in graphical profiles at all. (Under Wayland it works fine)

@rusty-snake commented on GitHub (Nov 26, 2020): Thanks for reporting. `ipc-namespace` breaks some X-extensions and causes frequently issues with gui programs. That's why it should not be used in graphical profiles at all. (Under Wayland it works fine)

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

No description provided.

Rows
Columns