After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 673136 - sushi doesn't start in nautilus.
sushi doesn't start in nautilus.
Status: RESOLVED NOTGNOME
Product: sushi
Classification: Core
Component: general
0.4.x
Other Linux
: Normal major
: ---
Assigned To: Sushi maintainer(s)
Sushi maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-03-30 05:33 UTC by sangu
Modified: 2012-05-01 01:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sangu 2012-03-30 05:33:50 UTC 
https://bugzilla.redhat.com/show_bug.cgi?id=806180
Click space key in nautilus -> No response

Steps to Reproduce:
1. launch nautilus
2. move a media file (like a jpg file)
3. click space key

sushi-0.4.0-1.fc17.x86_64
nautilus-3.4.0-1.fc17.x86_64
gvfs-1.12.0-1.fc17.x86_64
gtk3-3.4.0-1.fc17.x86_64
glib2-2.32.0-1.fc17.x86_64
clutter-1.10.0-2.fc17.x86_64
clutter-gtk-1.2.0-1.fc17.x86_64
cogl-1.10.0-1.fc17.x86_64
gjs-1.32.0-1.fc17.x86_64
dbus-1.4.10-4.fc17.x86_64
Comment 1 sangu 2012-04-19 00:48:05 UTC 
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