Zenity does not pull `libglvnd-gles`, which makes it abort when it can't find `libGLESv2.so.2`. My system is a Xen virtual machine without hardware acceleration. ``` $ dnf list installed zenity Installed Packages zenity.x86_64 4.0.1-2.fc40 @fedora $ dnf list --installed lib* | grep -e egl -e lges libglvnd-egl.x86_64 1:1.7.0-4.fc40 @fedora libwayland-egl.x86_64 1.22.0-3.fc40 $ zenity --question --title title --text text libEGL warning: DRI2: failed to authenticate MESA: error: ZINK: failed to choose pdev libEGL warning: egl: failed to create dri2 screen Couldn't open libGLESv2.so.2: libGLESv2.so.2: cannot open shared object file: No such file or directory Aborted (core dumped) $ rpm -q --whatrequires libglvnd-gles no package requires libglvnd-gles $ rpm -q --whatprovides libglvnd-gles libglvnd-gles-1.7.0-4.fc40.x86_64 $ rpm -q --whatrecommends libglvnd-gles no package recommends libglvnd-gles $ rpm -q --whatsuggests libglvnd-gles no package suggests libglvnd-gles ``` If I choose the cairo renderer, it works: ```sh env GSK_RENDERER=cairo LIBGL_ALWAYS_SOFTWARE=1 zenity --question --title title --text text --timeout 1 ``` But on Fedora 39, this was not required. Zenity should not fail on missing graphics support if it is not required. Else it should install `libglvnd-gles` so the program doesn't abort. Reproducible: Always Steps to Reproduce: 1. Install a minimal Fedora system, libglvnd-gles is not going to be installed. 2. Install zenity. 3. Try to run zenity: zenity --question --title title --text text Actual Results: Zenity aborted. Expected Results: Zenity works. Zenity must depend on `libglvnd-gles` or continue continue without graphic acceleration. I am on a Qubes OS Fedora 40 Minimal qube. Hardware acceleration is not present, zenity worked on previous versions available on Fedora 39.
I think this is a gtk4 issue. To reproduce: toolbox create -r f41 toolbox enter fedora-toolbox-41 sudo dnf install gtk4-devel # compile the example from https://docs.gtk.org/gtk4/getting_started.html ./example-0 Output: MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FINISHME: support YUV colorspace with DRM format modifiers MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:794: FINISHME: support more multi-planar formats with DRM modifiers Couldn't open libGLESv2.so.2: libGLESv2.so.2: cannot open shared object file: No such file or directory fish: Job 1, './example-0' terminated by signal SIGABRT (Abort)
This is also breaking builds on koji (which are minimal) when run in xvfb: https://koschei.fedoraproject.org/build/18775164
This may have been fixed in Rawhide with GTK 4.17, though I don't know how or why.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.