Description of problem: sushi doesn't start in nautilus. or $ sushi (sushi-start:4664): 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): 0.3.92-2.fc17.x86_64 How reproducible: always Steps to Reproduce: 1. launch nautilus 2. move a media file (like a jpg file) 3. click space key Actual results: Expected results: Additional info: nautilus-3.3.92-1.fc17.x86_64 clutter-1.9.16-1.fc17.x86_64 cogl-1.10.0-1.fc17.x86_64
This issue still happens in sushi 0.4.0
This bug still happens in sushi-0.4.1-1.fc17.x86_64. Maybe, sushi seem to find wrong GL lib. $ ldd /usr/libexec/sushi-start |grep GL libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007f4664b62000) <-- wrorng Because this linux system is using nvidia closed source driver. # ldconfig -v /usr/lib64/nvidia: [...] libGL.so.1 -> libGL.so.290.10 In another gl program. $ ldd /usr/bin/glxgears | grep GL libGLEW.so.1.6 => /lib64/libGLEW.so.1.6 (0x00007fa98451a000) libGLU.so.1 => /lib64/libGLU.so.1 (0x00007fa9842ac000) libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x00007fa983f95000) <--- Rright
After recent updating packages in test repo, this issue is fixed. $ ldd /usr/libexec/sushi-start |grep GL libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x00007f0689006000)