Description: After installing gnome-desktop group ( dnf group install gnome-desktop ), the mesa-dri-drivers package is not installed and gdm/graphical UI won't work because of that. Packages to be added: mesa-dri-drivers Comps group: gnome-desktop Testing was done on Fedora-Server-netinst-x86_64-28-20180322.n.0.iso .
CCing some of the GNOME folks to get their opinion here.
Here are some error messages from journal that occur when mesa is not installed, and gdm tries to start: org.gnome.Shell.desktop[7456]: gbm: failed to open any driver (search paths /usr/lib64/dri) org.gnome.Shell.desktop[7456]: gbm: Last dlopen error: /usr/lib64/dri/radeonsi_dri.so: cannot open shared object file: No such file or directory org.gnome.Shell.desktop[7456]: failed to load driver: radeonsi org.gnome.Shell.desktop[7456]: gbm: failed to open any driver (search paths /usr/lib64/dri) org.gnome.Shell.desktop[7456]: gbm: Last dlopen error: /usr/lib64/dri/kms_swrast_dri.so: cannot open shared object file: No such file or directory org.gnome.Shell.desktop[7456]: failed to load driver: kms_swrast org.gnome.Shell.desktop[7456]: gbm: failed to open any driver (search paths /usr/lib64/dri) org.gnome.Shell.desktop[7456]: gbm: Last dlopen error: /usr/lib64/dri/swrast_dri.so: cannot open shared object file: No such file or directory org.gnome.Shell.desktop[7456]: failed to load swrast driver gnome-shell[7456]: Failed to create backend: Failed to initialize renderer: Failed to create gbm device: No such file or directory
If gdm is dlopening these, shouldn't there just be a Requires: mesa-dri-drivers on gdm?
(In reply to Kevin Fenzi from comment #3) > If gdm is dlopening these, shouldn't there just be a Requires: > mesa-dri-drivers on gdm? Adding needinfo for Ray Strode, the GDM maintainer.
Any word on this?
no, gdm doesn't dlopen those. g*b*m dlopen's those. didn't three letter acronym. but i think comps is the right fix, not a spec file dependency.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I created a PR here: https://pagure.io/fedora-comps/pull-request/546
The PR was merged.