Description of problem: Started a VM with QXL and gnome-shell fails to start Version-Release number of selected component (if applicable): mesa-dri-drivers-10.4.3-1.20150124.fc21.x86_64 How reproducible: Always Steps to Reproduce: 1. Start gnome-shell on a VM Actual results: Fails to start: Mar 20 15:58:20 vrutkovs-f21u-43 gdm-Xorg-:0[1068]: (II) SELinux: Disabled by boolean Mar 20 15:58:20 vrutkovs-f21u-43 gdm-Xorg-:0[1068]: (II) AIGLX: Screen 0 is not DRI2 capable Mar 20 15:58:20 vrutkovs-f21u-43 gdm-Xorg-:0[1068]: (EE) AIGLX: reverting to software rendering Mar 20 15:58:20 vrutkovs-f21u-43 gdm-Xorg-:0[1068]: (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (libLLVM-3.5.so: cannot open shared object file: No such file or directory) Mar 20 15:58:20 vrutkovs-f21u-43 gdm-Xorg-:0[1068]: (EE) GLX: could not load software renderer Mar 20 15:58:20 vrutkovs-f21u-43 gdm-Xorg-:0[1068]: (II) GLX: no usable GL providers found for screen 0 -bash-4.3# ldd /usr/lib64/dri/swrast_dri.so linux-vdso.so.1 => (0x00007ffd29d1a000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f55c7358000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f55c7138000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f55c6f30000) libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f55c6d00000) libdrm_nouveau.so.2 => /lib64/libdrm_nouveau.so.2 (0x00007f55c6af8000) libdrm_intel.so.1 => /lib64/libdrm_intel.so.1 (0x00007f55c68d0000) libdrm_radeon.so.1 => /lib64/libdrm_radeon.so.1 (0x00007f55c66c0000) libdrm.so.2 => /lib64/libdrm.so.2 (0x00007f55c64b0000) libelf.so.1 => /lib64/libelf.so.1 (0x00007f55c6298000) libLLVM-3.5.so => not found libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f55c5f88000) libm.so.6 => /lib64/libm.so.6 (0x00007f55c5c80000) libc.so.6 => /lib64/libc.so.6 (0x00007f55c58c0000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f55c56a8000) libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f55c5438000) liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f55c5210000) /lib64/ld-linux-x86-64.so.2 (0x00007f55c8140000) libpciaccess.so.0 => /usr/lib64/libpciaccess.so.0 (0x00007f55c5000000) -bash-4.3# rpm -qa mesa-dri-drivers mesa-dri-drivers-10.4.3-1.20150124.fc21.x86_64 -bash-4.3# yum provides '*libLLVM-3.5.so' llvm-libs-3.5.0-6.fc21.i686 : LLVM shared libraries Repo : updates Matched from: Filename : /usr/lib/llvm/libLLVM-3.5.so Provides : libLLVM-3.5.so llvm-libs-3.5.0-6.fc21.x86_64 : LLVM shared libraries Repo : updates Matched from: Filename : /usr/lib64/llvm/libLLVM-3.5.so llvm-libs-3.5.0-6.fc21.x86_64 : LLVM shared libraries Repo : installed Matched from: Filename : /usr/lib64/llvm/libLLVM-3.5.so Expected results: gnome-shell starts up Additional info:
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.