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.
Oh...Eric aka AlienBob
I'm not 100% certain with as much different work as I've been doing with several systems on the same box and at the same time converting to EFI boot (another new learning curve not nearly as specific in feedback as LILO), but I'm pretty sure I had converted my Main, this system I'm focusing on right now, to Vtown shortly after it was released. I am 100% that I had removed ConsoleKit. It actually was running really great which is what inspired me to do more rapid upgrades via slackpkg. It is however possible that I did miss removing something that created a trigger to slackpkg "thinking" it had an older system to deal with, especially with the initial mess I created not understanding slackpkg at all well.
One of my test installs was from scratch with Vtown and it runs great so I'm thinking of reinstalling almost every subdirectory on my Main. If my Main wasn't fleshed out with a lot off addon packages and the only system presently on an NVME drive, I'd just switch to the clean fresh install but it lacks a lot of important stuff and is on a mechanical drive. It is an ace up the sleeve though since it wouldn't be difficult to clone it to NVME and as I keep all my built packages in /tmp, adding on wouldn't be too traumatic or time consuming.
I should mention that I also did a clean install from 12/7 iirc on an ancient IBM Thinkpad T61P (pre Lenovo). I am impressed and surprised that it runs substantially better with Current than it did with 14.2. Some of that is probably new kernel but a lot is just from the great work you have accomplished implementing a solid Plasma. Certainly those Plasma boys have demonstrated they've grown really tired of all the KDE4 hangover "bloat" talk and have refined Plasma 5 to a very sweet footprint, but it has been mostly you, if I understand the process much like 64bit was, that brought it to Slackware. You're one potent coder, Bro.
OK this is weird. Thankfully I have a clean install version of the same as I'm trying to upgrade to. So once I found I could login to Xfce, I began looking for what is different between the two. Dolphin wouldn't yet run but good ol' Krusader did. Combining that and narrowing down by launching kde apps from terminal and watching for what is missing, then seeing if it exists on the working test install system, I found that baloo, 2 packages in the kde subdirectory were not installed on my Main. I reinstalled "kde" twice so I don't understand how baloo got overlooked/missed.
In any case, I downloaded the two baloo packages via mirror-by-browser, installed them and while I haven't 100% confirmed that is all that was missing, Plasma 5 now logs in and looks fine. I know baloo gets a lot of hate mail but geeeez!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.