Package Details: zathura-git 2026.07.08.r6.gedc0ca7e-1

Git Clone URL: https://aur.archlinux.org/zathura-git.git (read-only, click to copy)
Package Base: zathura-git
Description: Minimalistic document viewer
Upstream URL: https://pwmt.org/projects/zathura
Licenses: zlib
Conflicts: zathura
Provides: zathura
Submitter: None
Maintainer: a821
Last Packager: a821
Votes: 95
Popularity: 0.166163
First Submitted: 2009-09-19 13:00 (UTC)
Last Updated: 2026-07-11 06:35 (UTC)

Dependencies (19)

Required by (23)

Sources (1)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

balmar commented on 2026-07-12 22:23 (UTC)

Yes, could very well be, but I then installed this zathura-git package from yay... so I'm not sure what happened. Anyway it works fine now with the symlink so unless you'd like me to investigate more I'm happy as is.

a821 commented on 2026-07-11 18:26 (UTC)

Perhaps you forgot to pass the --prefix option to meson when you compiled zathura from sources, which I guess it defaults to /usr/local. This option is set automatically to /usr by arch-meson in the PKGBUILD. You can see here the arch-meson source: https://gitlab.archlinux.org/archlinux/packaging/packages/meson/-/blob/main/arch-meson

balmar commented on 2026-07-11 16:49 (UTC)

Thanks! I confirm the tests issue is now gone.

Before trying the Arch git package I tried to compile directly from github and for some reason the build/build.ninja file has -DZATHURA_PLUGINDIR="/usr/local/lib/zathura so maybe that's why I had that problem. That install failed me with core dumped I think so that's when I turned to your package via yay. I've no idea where but I suspect some config somewhere still has /usr/local/lib/zathura.

(I had the non-git version installed until yesterday and now I was trying to see if the freshest versions got rid of a weird bug where opening multiple zathura windows then moving them around above-below other windows and/or other workspaces in i3wm lose my ability to scroll the pdf left or right. The answer is no. :-( But the error is so random that I'm not prepared to file a bug report upstream. Maybe I should...?)

a821 commented on 2026-07-11 06:40 (UTC)

@balmar: Thanks for the report! I fixed the tests issue (Upstream recent commits removed such option).

I cannot reproduce the plugins issue. The zathura-git plugins are installed under /usr/lib as always. I tried viewing some PDF and PS files with zathura-git and found no problem at all.

balmar commented on 2026-07-10 17:09 (UTC)

Oh and I also got meson.build:1:0: ERROR: Unknown option: "tests".

so I removed -Dtests=disabled from the build file to compile.

balmar commented on 2026-07-10 17:05 (UTC)

It looks like zathura now expects the plugin files at /usr/local/lib/zathura/

whereas the yay install puts them in /usr/lib/zathura/ .

I couldn't get the plugins to work before I created a symlink between the above two.

a821 commented on 2026-02-03 17:16 (UTC) (edited on 2026-02-04 08:04 (UTC) by a821)

Edit2: Fixed upstream. The missing headers were added back in girara (see commit e73ddcd). I rebuilt girara-git, zathura-git and the other -git plugins successfully just know. (The PKGBUILD doesn't require changes so I won't push).

--

This is an upstream issue. The file "types.h" was removed from installation recently (see girara commit 0e6a327). It seems there's is a big refactoring going on, so breakage is expected; after all, this is a git package.

Edit: FWIW, I built this successfully last weekend, and that commit is dated Sunday night.

raphix commented on 2026-02-03 15:22 (UTC) (edited on 2026-02-03 15:23 (UTC) by raphix)

[3/122] Compiling C object zathura-sandbox.p/zathura_main-sandbox.c.o
FAILED: [code=1] zathura-sandbox.p/zathura_main-sandbox.c.o 
cc -Izathura-sandbox.p -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/sysprof-6 -I/usr/include/gio-unix-2.0 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/cloudproviders -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glycin-2 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/atk-1.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/fribidi -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/json-glib-1.0 -I/usr/include/synctex -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=c17 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -g -ffile-prefix-map=/home/raph/.cache/paru/clone/zathura-git/src=/usr/src/debug/zathura-git -flto=auto -fPIE -pthread '-DGETTEXT_PACKAGE="org.pwmt.zathura"' '-DLOCALEDIR="/usr/share/locale"' '-DZATHURA_PLUGINDIR="/usr/lib/zathura"' '-DSYSCONFDIR="/etc"' -D_DEFAULT_SOURCE -DWITH_SYNCTEX -DWITH_SANDBOX -DWITH_SECCOMP -DWITH_LANDLOCK -Werror=implicit-function-declaration -Werror=vla -Werror=int-conversion -Werror=maybe-uninitialized -MD -MQ zathura-sandbox.p/zathura_main-sandbox.c.o -MF zathura-sandbox.p/zathura_main-sandbox.c.o.d -o zathura-sandbox.p/zathura_main-sandbox.c.o -c ../zathura/main-sandbox.c
Dans le fichier inclus depuis ../girara-gtk/settings.h:6,
                 depuis ../zathura/main-sandbox.c:3:
../girara-gtk/types.h:6:10: erreur fatale: girara/types.h : Aucun fichier ou dossier de ce nom
    6 | #include <girara/types.h>
      |          ^~~~~~~~~~~~~~~~

Just after recompiling girara-git with makepkg -si, I launch the compilation of zathura-git and get this error.

$ pacman -Q girara-git
girara-git 2026.01.30.r14.ga3763f7-1

what did I miss?

a821 commented on 2025-10-28 18:06 (UTC)

I'm the maintainer of girara-git :)

You need to recompile girara-git yourself. Since it's a VCS package, it does not need to be bumped.

pvk commented on 2025-10-28 17:51 (UTC)

@a821:

girara-git 0.4.4.r10.g7368f9d-1

But I also notice that the version of girara-git in the AUR is also 0.4.4, specifically 0.4.4.r1.g23b4ed7-1. Should I ask the maintainer of that to bump the version?