SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've just done some testing on it as I use the nvidia proprietary drivers which do not supply a libglapi.so at all and I can report that a symlink pointing to libGL.so.$VERSION for libglapi.so.0 works.
If the same can be done in the mesa package when it is not compiled with a separate libglapi.so then a possible conflict can be avoided, assuming that nvidia doesn't modify their blob installer to deal with it.
No problems here.
I'm running all the latest packages posted last night, my time, and the Nvidia 310.19 drivers, in Slackware64-current with Xfce, and everything is working flawlessly... so far.
:-)
Well, most of things are working for me too. It's only some of KDE's effects that complain for something wrong in OpenGL. Composition is started per se, the fading logo works, etc. But wobbly windows, the cube, and some other effects complain saying that OpenGL is missing.
I would happily ldd the involved executables to see what they're missing, but I can't find which ones they are =D
Probably you don't notice this with Xfce... ?
Or maybe something in KDE needs to be recompiled after Mesa upgrade... sorry for just throwing random ideas :/
Last edited by lonestar_italy; 02-23-2013 at 05:17 AM.
I'm trying to build mesa9.0.3 using the slackware slackbuild from current.
I'm using slackware64 current and multilib both updated just now.
If i add "--enable-shared-glapi" to the slackbuild, the package is compiled without errors, but when i use:
Code:
. /etc/profile.d/32dev.sh
To build the multilib package stops in this error:
Code:
gmake[4]: *** [xform4.lo] Error 1
In the slackbuild the LIBDIRSUFFIX is set to "" in the x86_64 elfi part.
What i missed?
I've just done some testing on it as I use the nvidia proprietary drivers which do not supply a libglapi.so at all and I can report that a symlink pointing to libGL.so.$VERSION for libglapi.so.0 works.
If the same can be done in the mesa package when it is not compiled with a separate libglapi.so then a possible conflict can be avoided, assuming that nvidia doesn't modify their blob installer to deal with it.
Wouldn't that approach cause a problem for pre-compiled binaries built against a libglapi which will be looking for a soname of 'libglapi.so.0' and won't find it?
Wouldn't that approach cause a problem for pre-compiled binaries built against a libglapi which will be looking for a soname of 'libglapi.so.0' and won't find it?
They shouldn't even be compiled against it, it is implementation specific (only mesa has it).
OpenGL also has it's own versioning system with it's own API calls so you shouldn't even use a SONAME or anything else other than the OpenGL API to check.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,041
Rep:
Quote:
Originally Posted by lonestar_italy
Well, most of things are working for me too. It's only some of KDE's effects that complain for something wrong in OpenGL. Composition is started per se, the fading logo works, etc. But wobbly windows, the cube, and some other effects complain saying that OpenGL is missing.
I would happily ldd the involved executables to see what they're missing, but I can't find which ones they are =D
Probably you don't notice this with Xfce... ?
Or maybe something in KDE needs to be recompiled after Mesa upgrade... sorry for just throwing random ideas :/
Running KDE 4.10, at the moment and the "cube" and "wobby windows" work just fine.
The only problem I've had with KDE 4.10, is the desktop icons cannot be moved. This started before all the recent latest X updates, and, yes, I've checked all the setting. Another problem with the desktop icons, and this goes back over the last few KDE versions, is the size of the desktop icons cannot be changed. Oh, you can go through the motions, but the changes do not take effect.
I don't think my issue is related to the video driver at all, but we'll see...it seems I've developed the "klauncher can't find dbus" problem somehow in the last 24 hrs...from the kdm.log the warning is that dbus isn't running or installed, but $ps aux | grep dbus shows that it is in fact installed and running...doing #slackpkg reinstall kde at present..it is possible something got corrupt when I was doing the upgrade at work yesterday...and now for more caffeine
Curiosity got the better of me and I've looked even more closely at trine2 and libglapi.so and the link is actually an error on their part as it doesn't call any functions from the library at all you can symlink it to any library on the system and it will still work.
I'll be reporting this as a bug to the Trine 2 folks.
Well, seems like I had "Compositing type" set to XRender.
I changed it to OpenGL, and now all effects are working.
But I had not changed this toggle from it's usual value before or after latest -current updates. I guess some default changed from what it used to be....
Thanks everybody for spending time on reading this =)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.