Description of problem: Upgrading llvm-libs causes gnome-shell to display "Oops! Something has gone wrong" screen. The logs contain these messages: Dec 26 00:30:02 f21test.internal /usr/bin/dbus-launch[1238]: gnome-session-is-accelerated: llvmpipe detected. Dec 26 00:30:03 f21test.internal gnome-session[1238]: Entering running state Dec 26 00:30:12 f21test.internal gnome-session[1238]: LLVM ERROR: Cannot select: intrinsic %llvm.x86.sse41.pblendvb Dec 26 00:30:13 f21test.internal gnome-session[1238]: current session already has an ibus-daemon. Dec 26 00:30:14 f21test.internal gnome-session[1238]: LLVM ERROR: Cannot select: intrinsic %llvm.x86.sse41.pblendvb Dec 26 00:30:14 f21test.internal gnome-session[1238]: gnome-session[1238]: WARNING: App 'gnome-shell.desktop' respawning too quickly Dec 26 00:30:14 f21test.internal gnome-session[1238]: WARNING: App 'gnome-shell.desktop' respawning too quickly Dec 26 00:30:14 f21test.internal gnome-session[1238]: Unrecoverable failure in required component gnome-shell.desktop This is on an x86-64 qemu-kvm host with QXL video device Version-Release number of selected component (if applicable): llvm-libs-3.5.0-4.fc21.x86_64 mesa-dri-drivers-10.4.0-1.20141214.fc21.x86_64 mesa-libxatracker-10.4.0-1.20141214.fc21.x86_64 How reproducible: Always Steps to Reproduce: 1. Boot to graphical login (gdm) 2. "Oops!" screen is displayed Actual results: Login screen not displayed Expected results: Should boot to graphical login Additional info: Downgrading to these versions allows gnome-shell to work again: llvm-libs-3.4-15.fc21.x86_64 mesa-dri-drivers-10.3.3-1.20141110.fc21.x86_64 mesa-libxatracker-10.3.3-1.20141110.fc21.x86_64 The failure still occurs with these versions: llvm-libs-3.5.0-5.fc21.x86_64 mesa-dri-drivers-10.4.0-4.20141214.fc21.x86_64 mesa-libxatracker-10.4.0-4.20141214.fc21.x86_64
I'm seeing this as well, the downgrade to 3.4.15 fixes the issue.
The problem does not happen any more after updating to these versions: llvm-libs-3.5.0-6.fc21.x86_64 mesa-dri-drivers-10.4.7-1.20150323.fc21.x86_64 mesa-libxatracker-10.4.7-1.20150323.fc21.x86_64
I'm still seeing this on the stock Fedora 22 live CD, with updated mesa and llvm-libs.
This works fine in F23 beta for me now.
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.