Hide Forgot
Description of problem: (empathy:14881): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to find suitable fbconfig for the GLX context: Failed to find any compatible fbconfigs (empathy:14881): empathy-CRITICAL **: main: assertion `gtk_clutter_init (&argc, &argv) == CLUTTER_INIT_SUCCESS' failed Version-Release number of selected component (if applicable): 17 How reproducible: Simply launch it. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: The chat window works.
Also seen in Fedora 17. [671:0]>empathy (empathy:7532): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to find suitable fbconfig for the GLX context: Failed to find any compatible fbconfigs (empathy:7532): empathy-CRITICAL **: main: assertion `gtk_clutter_init (&argc, &argv) == CLUTTER_INIT_SUCCESS' failed thaynes@nexus6:~/Desktop [672:1]>rpm -q empathy empathy-3.4.0.2-1.fc17.x86_64 thaynes@nexus6:~/Desktop [673:0]>rpm -qa '*nvidia*' xorg-x11-drv-nvidia-devel-295.33-1.fc17.x86_64 xorg-x11-drv-nvidia-libs-295.33-1.fc17.x86_64 xorg-x11-drv-nvidia-295.33-1.fc17.x86_64 kmod-nvidia-3.3.1-3.fc17.x86_64-295.33-1.fc17.x86_64 nvidia-xconfig-1.0-13.fc17.x86_64 akmod-nvidia-295.33-1.fc17.x86_64 nvidia-settings-1.0-15.fc17.x86_64 kmod-nvidia-3.3.0-8.fc17.x86_64-295.33-1.fc17.x86_64 kmod-nvidia-3.3.0-1.fc17.x86_64-295.33-1.fc17.x86_64
I have the same bug under Fedora 17, at least for 2-3 weeks. I also have the nvidia driver.
Identical error on a fresh install of Fedora 17 with the nvidia driver. [user@macbook-pro ~]$ rpm -qa '*nvidia*' akmod-nvidia-295.40-1.fc17.1.x86_64 nvidia-xconfig-1.0-14.fc17.x86_64 xorg-x11-drv-nvidia-295.40-1.fc17.x86_64 xorg-x11-drv-nvidia-libs-295.40-1.fc17.x86_64 nvidia-settings-1.0-16.fc17.x86_64 kmod-nvidia-3.3.2-1.fc17.x86_64-295.40-1.fc17.2.x86_64
Confirm!
Our problem is probably closely related, if not identical, to a previous gnome-shell bug: https://bugzilla.redhat.com/show_bug.cgi?id=716572
resolved for me in Empathy 3.4.1 With nvidia-settings-1.0-16.fc17.x86_64 xorg-x11-drv-nvidia-libs-295.40-1.fc17.x86_64 kmod-nvidia-3.3.4-1.fc17.x86_64-295.40-1.fc17.1.x86_64 xorg-x11-drv-nvidia-295.40-1.fc17.x86_64 akmod-nvidia-295.40-1.fc17.1.x86_64 kmod-nvidia-3.3.2-8.fc17.x86_64-295.40-1.fc17.3.x86_64 kmod-nvidia-3.3.2-1.fc17.x86_64-295.40-1.fc17.2.x86_64 nvidia-xconfig-1.0-14.fc17.x86_64
Is this bug still present, or has the gnome-shell fixed it?
I get this error as well when initializing clutter from python: > python Python 2.7.3 (default, Apr 30 2012, 21:18:11) [GCC 4.7.0 20120416 (Red Hat 4.7.0-2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from gi.repository import Clutter >>> Clutter.init("") (python:4829): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to find suitable fbconfig for the GLX context: Failed to find any compatible fbconfigs (<enum CLUTTER_INIT_ERROR_INTERNAL of type ClutterInitError>, []) >>> I get this today with an updated Fedora 17 on a Mac mini (Early 2009) MB464xx/A started with grub2-efi. The nvidia driver version is 295.53 > uname -a Linux box.anet 3.4.2-4.fc17.x86_64 #1 SMP Thu Jun 14 22:22:05 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux If you need more details, please let me know.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.