|
If you get a chance you might want to edit the sigil launch script and have it run ptrace on Sigil during launch. That way you can see the exact location it attempts to load libGL and its components from.
Also your qtdiag out put showed both qt4 and qt5 and even a qt3/include path in the environment.. That is very strange.
You can compare a ptrace output log from launching Sigil with a ptrace output from launching qtdiag to see if they differ in some way.
This may be worth a shot.
|