Bug#1141812: zathura: starts with about 30 seconds of delay over SSH X11 forwarding with Gdk Vulkan warnings
Sebastian Ramacher
sramacher at debian.org
Fri Jul 10 12:55:43 BST 2026
Control: reassign -1 libgtk-4-1 4.22.2+ds-2
On 2026-07-10 13:05:29 +0200, Francesco Poli (wintermute) wrote:
> Package: zathura
> Version: 2026.07.02-3
> Severity: important
> X-Debbugs-Cc: invernomuto at paranoici.org
>
> Hello!
>
> Since at least zathura/2026.07.02-3, I have been seeing a new misbehavior,
> which looks like a regression.
> I have also tried to upgrade to zathura/2026.07.08-1, but I see the same
> issue.
>
> Running zathura locally in X does not seem to have any issue.
> But, if I run it over SSH X11 forwarding:
>
> local-box $ ssh -X remote-box
> remote-box $ zathura document.pdf
> libEGL warning: DRI3 error: Could not get DRI3 device
> libEGL warning: Ensure your X server supports DRI3 to get accelerated rendering
>
> (zathura:691837): Gdk-WARNING **: 12:49:42.368: Cannot get portal org.freedesktop.portal.Inhibit version: Timeout was reached
>
> (org.pwmt.zathura:691837): Gdk-WARNING **: 12:49:42.445: Vulkan: ../src/amd/vulkan/radv_physical_device.c:2382: Could not open device /dev/dri/renderD128: Permission denied (VK_ERROR_INCOMPATIBLE_DRIVER)
>
> (org.pwmt.zathura:691837): Gdk-WARNING **: 12:49:42.446: Vulkan: ../src/intel/vulkan/anv_physical_device.c:2650: Unable to open device /dev/dri/renderD128: Permission denied (VK_ERROR_INCOMPATIBLE_DRIVER)
>
>
> This warnings are produced very slowly, thus delaying the startup of zathura
> by about 30 s, while in the past I hadn't noticed any significant delay
> (beyond the small one expected because of the remote rendering).
>
> I don't know if this is related to bug [#1049423], but I am seeing GDK Vulkan
> warnings, which are not mentioned in that bug report...
>
> [#1049423]: <https://bugs.debian.org/1049423>
You have correctly identified this is a Gtk 4 issue and even found the
bug. Reassigning accordingly.
Cheers
>
> Please note that the remote-box has AMD CPU-integrated graphics, while the
> local-box has Intel CPU-integrated graphics. Maybe this explains why I am
> seeing an AMD-related Vulkan warning and an Intel-related one...
>
> Please investigate this issue, and re-assign or forward upstream, as
> appropriate.
>
> Thanks for your time and dedication!
>
>
> -- System Information:
> Debian Release: forky/sid
> APT prefers testing
> APT policy: (800, 'testing'), (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 7.0.13+deb14-amd64 (SMP w/4 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages zathura depends on:
> ii libc6 2.42-17
> ii libcairo2 1.18.4-3+b1
> ii libgirara5 2026.07.07-1
> ii libglib2.0-0t64 2.88.2-1
> ii libgraphene-1.0-0 1.10.8-5+b2
> ii libgtk-4-1 4.22.2+ds-2
> ii libjson-glib-1.0-0 1.10.8+ds-2+b1
> ii libmagic1t64 1:5.47-4
> ii libpango-1.0-0 1.58.0-1
> ii libpangocairo-1.0-0 1.58.0-1
> ii libseccomp2 2.6.0-2+b1
> ii libsqlite3-0 3.46.1-9+b1
> ii libsynctex2 2026.20260303.78225+ds-4
> ii libxxhash0 0.8.3-2+b2
> ii zathura-pdf-poppler 2026.05.10-1+b1
>
> zathura recommends no packages.
>
> Versions of packages zathura suggests:
> ii chromium [www-browser] 149.0.7827.196-1
> ii falkon [www-browser] 26.04.2-1
> ii firefox-esr [www-browser] 140.12.0esr-1
> ii w3m [www-browser] 0.5.3+git20230121-2.3
> ii zathura-cb 2026.05.10-1+b1
> ii zathura-djvu 2026.05.10-1+b1
> ii zathura-ps 2026.02.03-1+b1
>
> -- no debconf information
--
Sebastian Ramacher
More information about the pkg-gnome-maintainers
mailing list