Created attachment 596771 [details] output from ~$ strace paraview 2> paraStrace.txt Description of problem: Trying to start paraview from the command line only yields the following message: $ paraview /usr/lib64/paraview/paraview: symbol lookup error: /lib64/libOSMesa.so.8: undefined symbol: _glapi_Dispatch Version-Release number of selected component (if applicable): paraview-3.14.1-3.fc17.x86_64 How reproducible: Every time Additional info: Nvidia driver installed and loaded (akmod from rpmfusion). Paraview worked fine in Fedora 16.
Also, the paraview binary (3.14.1 / tar.gz / 64-bit) from the kitware website seems to work.
I think this a problem with the linking of libOSMesa: mesa-libOSMesa.i686: W: undefined-non-weak-symbol /usr/lib/libOSMesa.so.8.0.3 _glapi_Dispatch mesa-libOSMesa.i686: W: undefined-non-weak-symbol /usr/lib/libOSMesa.so.8.0.3 _glapi_Context mesa-libOSMesa.i686: W: undefined-non-weak-symbol /usr/lib/libOSMesa.so.8.0.3 _glapi_get_proc_address mesa-libOSMesa.i686: W: undefined-non-weak-symbol /usr/lib/libOSMesa.so.8.0.3 _glapi_get_dispatch_table_size mesa-libOSMesa.i686: W: undefined-non-weak-symbol /usr/lib/libOSMesa.so.8.0.3 _glapi_get_dispatch mesa-libOSMesa.i686: W: undefined-non-weak-symbol /usr/lib/libOSMesa.so.8.0.3 _glapi_get_context mesa-libOSMesa.i686: W: undefined-non-weak-symbol /usr/lib/libOSMesa.so.8.0.3 _glapi_add_dispatch mesa-libOSMesa.i686: W: undefined-non-weak-symbol /usr/lib/libOSMesa.so.8.0.3 _glapi_check_multithread mesa-libOSMesa.i686: W: undefined-non-weak-symbol /usr/lib/libOSMesa.so.8.0.3 _glapi_set_context mesa-libOSMesa.i686: W: undefined-non-weak-symbol /usr/lib/libOSMesa.so.8.0.3 _glapi_set_dispatch libOSMesa.so.8 is not linked to libglapi.
Just updated to mesa from 8.0.3-1 to 8.0.3-3, nothing changed.
Same problem here on F17, 64bit.
mesa-8.1-0.19.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mesa-8.1-0.19.fc18
Package mesa-8.1-0.19.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mesa-8.1-0.19.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-12852/mesa-8.1-0.19.fc18 then log in and leave karma (feedback).
Any chance this will be fixed in F17 also? F18 is, after all, not even alpha yet.
mesa-8.1-0.19.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Since F18 is still alpha, please backport the fix to F17. thanks!
There is another deeper issue here as well. As discussed in this bug report and the mesa mailing list threads it links to https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=744434 it isn't actually correct to use both libGL and libOSMesa at the same time. This was fixed in VTK awhile back (you have to compile VTK without -DVTK_OPENGL_HAS_OSMESA:BOOL=ON), but paraview was missed as it has it's own copy. Currently we are getting away with it, but it is a sitting time bomb. Whether or not it bites you depends on linking order, functions used, and such. Cheers! -Tyson
(In reply to comment #10) ... > This was fixed in VTK awhile back (you have to compile VTK without > -DVTK_OPENGL_HAS_OSMESA:BOOL=ON), but paraview was missed as it has it's own > copy. There is a related bug 697842 on the private VTK copy of Paraview.