Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Z zathura
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 151
    • Issues 151
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pwmt
  • zathura
  • Issues
  • #274

Closed
Open
Created Apr 02, 2022 by Simon D@Semoar

rseq syscall not allowed in strict sandbox

How to reproduce

$ zathura --version
zathura 0.4.9
girara 0.3.7 (runtime: 0.3.7)
(plugin) pdf-mupdf (0.3.8) (/usr/lib/zathura/libpdf-mupdf.so)
$ cat .config/zathura/zathurarc
set selection-clipboard clipboard
set sandbox strict

Running on Arch Linux, sway/wayland.

Try to open any pdf document or just start zathura

Expected

A window opens.

Observed

Zathura does not open and in journalctl you can find:

... audit[103187]: SECCOMP auid=1000 uid=1000 gid=984 ses=1 pid=103187 comm="zathura" exe="/usr/bin/zathura" sig=31 arch=c000003e syscall=334 compat=0 ip=0x7f81638183c6 code=0x0

334 corresponds to rseq.

Running zathura with --log-level debug shows that it allows some syscalls, but rseq is not in the list.

Wanted to fix it, but already seems to be fixed in develop in 0cfaac07, just not yet released.

Edited Apr 02, 2022 by Simon D
Assignee
Assign to
Time tracking