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.
Probably the blob was not cleanly uninstalled or your xorg.conf still mentions the nvidia driver as the Xserver still looks for a file shipped in the blob.
I think its the former! Do you or anyone have a suggestions on how to get rid of the rest of blob and fix the glx symbolic links?
Thanks that helped! I deleted the libraries manually in those locations. I searched for nvidia and the first part of the driver number to find the rest. Then I removed and installed the relevant files back since I deleted the opengl files. I still had nouveau disabled in modprobe. Everything works as it should now
Today's update includes added and updated man pages in:
Japanese, thanks to Keiichi Shiga,
Serbian, thanks Bojan Popovic and Miloš Topličić. The man pages in Serbian should have been provided long ago, sorry for the delay.
Swedish, thanks to Ingemar Karlsson,
Please note that man-1.6 shipped in Slackware does not handle very well ideographs (failing to properly cut or justify lines, for instance). For this reason I suggest to replace it in Slackware by man-db, as we did in Slint for a better display of man pages in Japanese[1].
You can see an example of display in an xfce4-terminal of "man installpkg" in Japanese using the man binary shipped in man-db. The result is way better.
A SlackBuild for man-db is available @ http://slackbuilds.org, thanks to B. Watson. It installs by default man-db binaries and man pages in /opt/man-db to allow a coexistence with man-1.6. I chose to replace the latter by the former in Slint, thus installing in /usr instead.
Also, a Linux console is unable to display CJK languages as it can handle at most 512 glyphs per font, but one can install fbterm (also available from http://slackbuilds.org) to overcome this limitation.
[1]This is also the case for most of the man pages in Japanese already shipped in Slackware.
Last edited by Didier Spaier; 12-06-2016 at 02:13 PM.
Reason: footnote added.
I can't see any mention of this fix in the upcoming stable releases currently in review (expected later this week). So sadly, it looks like 'stable' kernel users will remain vulnerable until 4.8.14/4.4.38 at the earliest (unless Greg adds it in at the last minute).
FWIW, the commit Cwiz' linked to does appear to be fairly self-contained and applies cleanly to 4.8.12, so manual patching looks like a possibility if Greg doesn't include this fix, though I'd much prefer not to have to do that sort of thing as you never know whether it's going to break something.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.