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>

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!

Control: reassign -1 libgtk-4-1 4.22.2+ds-2

You have correctly identified this is a Gtk 4 issue and even found the
bug. Reassigning accordingly.

Cheers