Stock 4.1.13.

For future reference, you can just run:

Every so often, I rollback Slackware to a fresh install by clearing out everything from the SBo install listing, minus OpenRC stuff, then rebuild it all in one fell swoop over a day.

This refreshes dependencies and restores a lot of functionality at times. The only thing is, usually a lot of stuff on SBo can get broken, so I end up having to use ponce's bleeding edge repository at times.

An update.

I put a second Slackware on another partition. We'll call this Slack 2. It is current, the same version as my main Slackware, which we'll call Slack 1. Once Slack 2 got settled in and working, I used it to test the functionality of the crazybee.sh Bumblebee installer. To my surprise, it installed right the first time. Oh. I mean, that's good, but it was unexpected.

Note: Slack 1 and Slack 2 are the exact same version, with the same kernel.

I copied out the Slack 2 copy of all of the slack-packages made during the BumbleBee install process. As root, I installed them in Slack 1. This put in everything that was needed, neatly bypassing the problem, whatever it was, that prevents things like the bbswitch module from compiling.

Reboot. Slack 1 is no longer running hot, because bbswitch and the other bits are running. Whew. Problem solved. Not understood, but worked around.

Later, poking around the directories of the two Slacks, I noticed something odd: Slack 2's kernel directory had several subdirectories that were not in Slack 1. What the hell?

New theory: somehow in the recent upgrade of current (from the version of a few months ago to the new eudev version) the upgrade of the kernel headers and/or source was ... well, failed? corrupted? only partially upgraded?

So I reinstalled kernel source (/k directory), kernel headers (/d directory) kernel firmware (/a directory) generic kernel (/a directory)and kernel modules (/a directory). Regenerated initrd, ran lilo, rebooted. All still fine and the directory tree of the /usr/src area has all those missing bits.

edit: so I guess I'll never know the actual specific cause of the problem. Something took out part of the kernel area!

How I did the most recent upgrade: http://www.linuxquestions.org/questi...ml#post5453753 Near as I can tell, I did that correctly?

Great you solved it! And thanks for sharing your solution, it could help others. Unfortunately so rare nowadays...

You're welcome. I don't know as much as many of the regulars here but I can at least help them learn from my mistakes.

Also if I have the same problem in the future and forget, googling can lead me back to this thread.

The virtual box in slackbuilds even current is very old . I uninstalled it. then installed VirtualBox Version 5.0.10 r104061
with the developers install script. Then booted it then used there guest add-on's cdrom.
wonderful thing about slackware is you can use the developers build and it works. There is a little bit of work stripping things apart
and making slackbuilds with it. And I am sure one day the maintainer may get around to it.

At this point, I theorize that my missing kernel related files caused the Virtualbox installer to fail to compile a kernel driver. So perhaps I could install Virtualbox now.

An added datum: when I originally installed Virtualbox, I used their installer, not a slackbuild.

I was using Libreoffice 5.0.1 on Slackware64-current, but, then it became nonfunctional. That is, LO would not launch when I clicked on the icon in my application program list in XFCE4. Many thanks to Eric for providing a newer version of LO at his site.
Libreoffice 5.0.3 functions as expected on Slackware64-current.

I believe I have a full install of the latest -current. I tried to run gwenview and got the following error:
$ gwenview
gwenview: error while loading shared libraries: libraw_r.so.15: cannot open shared object file: No such file or directory

$ grep libraw_r /var/log/packages/*
/var/log/packages/LibRaw-0.16.0-x86_64-1:usr/lib64/pkgconfig/libraw_r.pc
/var/log/packages/LibRaw-0.16.0-x86_64-1:usr/lib64/libraw_r.la
/var/log/packages/LibRaw-0.16.0-x86_64-1:usr/lib64/libraw_r.so.10.0.0

ldd /usr/bin/gwen* shows both /usr/bin/gwenview and /usr/bin/gwenview_importer as having the following:
libraw_r.so.15 => not found

Might need a rebuild? Or did I miss an added somewhere?
gwenview-4.14.3-x86_64-2 from Thu Oct 29 20:12:14 UTC 2015

The package.txt file shows,

as the correct version for -current and was updated on 14 November.

You might want to take a look at the change log,

http://www.slackware.com/changelog/c...php?cpu=x86_64

1 members found this post helpful.

Thanks. I had that LibRaw-0.17.0-x86_64-1.txz in my mirror. I somehow missed all the packages that stared with a capital letter. I didn't want to accidentally mess up multilib and tried doing things like upgradepkg [a-f]*.txz [h-z]*.txz and then manually do the g*.txz packages.

gwenview opened fine after upgradepkg.