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.
The new nvidia prop driver have a new thing and nvidia-settings now uses gkt3 by default, or something like that. But its not working on Slack. I have the bumblebee setup, and it gives me this message now:
bash-4.3# nvidia-settings
ERROR: libnvidia-gtk3.so.346.35: cannot open shared object file: No such file or directory
libnvidia-gtk3.so: cannot open shared object file: No such file or directory
libnvidia-gtk2.so.346.35: cannot open shared object file: No such file or directory
libnvidia-gtk2.so: cannot open shared object file: No such file or directory
ERROR: A problem occured when loading the GUI library. Please check your installation and library path. You may need to specify this library when calling nvidia-settings. Please run
`nvidia-settings --help` for usage information.
Not sure if its the way the installation is made in the bumblebee script or something else. I'll try to poke around the bumblebee-nvidia slackbuild later.
slackbuild nvidi-driver: 340.65 has broken my amd and nvidia mixed system, 340.76 was released today and fixed this problem.
Edit: there are still problem with 340.76, all screen number is messed up, can't have 2 different screen 0 from different video chip vendors. back to 340.58 works.
As i said ( or tried to) in the initial post, the nvidia-settings cant find the gtk3 nor the gtk2 libs, as it says in the error.
bash-4.3# nvidia-settings --use-gtk2
ERROR: libnvidia-gtk2.so.346.35: cannot open shared object file: No such file or directory
libnvidia-gtk2.so: cannot open shared object file: No such file or directory
ERROR: A problem occured when loading the GUI library. Please check your installation and
library path. You may need to specify this library when calling nvidia-settings.
Please run `nvidia-settings --help` for usage information.
ERROR: libnvidia-gtk2.so.346.35: cannot open shared object file: No such file or directory
libnvidia-gtk2.so: cannot open shared object file: No such file or directory
ERROR: A problem occured when loading the GUI library. Please check your installation and
library path. You may need to specify this library when calling nvidia-settings.
Please run `nvidia-settings --help` for usage information.
I don't have this problem with 346.35 on 14.1 multilib.
There's no output at all when I run nvidia-settings from terminal.
It still exits with segmentation fault whenever I close the window, but I think it's a completely different issue.
Have you tried nvidia.run --uninstall before upgrading the driver?
Maybe some leftover from old driver did this, I have seen it happen before.
I believe the script you use to install the NVIDIA driver just doesn't include the libnvidia-gtk2.so.346.35 and libnvidia-gtk3.so.346.35 files.
EDIT: If it's similar to the nvidia-driver SlackBuild you'll probably need to add something like (untested BTW, I just use the binary installer, which has stopped removing libEGL.la ... for now):
I am also running this nvidia driver with the bumblebee setup... without issues. The package creates a menu item under settings that should run it properly. To do it from the command line you need to run
Code:
optirun nvidia-settings -c :8
Not sure what is causing the issues tho you describe above. Have you removed stock slackware packages from your system? What version of slackware are you running?
I believe the script you use to install the NVIDIA driver just doesn't include the libnvidia-gtk2.so.346.35 and libnvidia-gtk3.so.346.35 files.
EDIT: If it's similar to the nvidia-driver SlackBuild you'll probably need to add something like (untested BTW, I just use the binary installer, which has stopped removing libEGL.la ... for now):
No, i havent removed anything from the default full install. Just checked and the 340.76 packages (nvidia-bumblebee and nvidia-kernel) opens the nvidia-settings normally.
Well, i kept digging around in this. Looks like now i only get those errors if im starting from the terminal, in my need fresh slackware install ( when i created this post, it was not). When i start the nvidia-settings shortcut on the KDE or XFCE menus, it goes on normally.
After making sure those 2 libraries was being compiled, from the terminal, the nvidia-settings opens with:
A few observations:
1. I think it leaks files. Starting with v346.35, the nvidia-settings package now creates the libnvidia-gtk{2,3}.so.${VERSION} libraries, so LIBDIR=/package/library/location needs to be added to the respective make install line. Otherwise it installs to the default location of /usr/local/lib while the package is being made.
2. The nvidia-settings and nvidia-xconfig packages don't actually need to be downloaded or used. Except for NV-CONTROL-API.txt and FRAMELOCK.txt(which aren't important), all the files that are installed from those packages are actually present in the NVIDIA binary installer. So the SlackBuild could be simplified slightly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.