Description of problem: Starting gnome-shell with the rpmfusion proprietary nvidia drivers results in gnome-shell exiting with the message: (gnome-shell:4555): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to find suitable fbconfig for the GLX context: Failed to find any compatible fbconfigs Version-Release number of selected component (if applicable): gnome-shell-3.4.1-5.fc17.x86_64 kmod-nvidia-304.37-1.fc17.4.x86_64 xorg-x11-drv-nvidia-304.37-1.fc17.x86_64 xorg-x11-drv-nvidia-libs-304.37-1.fc17.x86_64 nvidia-settings-1.0-20.fc17.x86_64 kmod-nvidia-3.5.3-1.fc17.x86_64-304.37-1.fc17.3.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Log in Actual results: A screen with just backdrop and no menus Expected results: Gnome3 UI Additional info: There are various similar issues on bugzilla and other sites, but they are a year or so old and have been fixed. This issue showed up in the last few days and cannot be fixed with the workarounds given. The workaround I have found is as follows. 1 - Remove the rpath from the gnome-shell binary using: # chrpath -d /usr/bin/gnome-shell 2 - Add ld.so.conf paths /usr/lib64/gnome-bluetooth & /usr/lib64/gnome-shell .. I did this by creating two files: /etc/ld.so.conf.d/gnome-shell.conf (containing /usr/lib64/gnome-shell) /etc/ld.so.conf.d/gnome-bluetooth.conf (containing /usr/lib64/gnome-bluetooth) 3 - Run as root "ldconfig" This allows the glx shared objects specific for nVidia to be loaded, rather than the generic glx stuff from /usr/lib64
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.