Blacklist Plasma (temporarily at least)
by Scribtor from LinuxQuestions.org on (#5C59X)
How to exclude everything related to the new plasma DE:WM using slackpkg blacklist?
I have an USB with issue of "current" from August 2019 with a 4.19.69 kernel and software that was "current" at the time.
After installing the old and upgrading, I found that the new kernel is having problems with VirtualBox, which is a must currently!
Vice-versa, mixing old kernel with new packages doesn't resolve the issue either, because apparently the old kernel is too old again to work with some of the new packages that come with plasma.
What, +almost+, works? Old kernel, old software but then I lose other important things like Thunderbird which is not the goal. (GMail wouldn't let me set up an account simply because my thunderbird of last year is too "insecure" for their IMAP)
From my point of view, the only reasonable solution for immediate resolution is old kernel, old packages which I will allow to be upgraded (mainly the gcc and glibc) so that other programs work with it but I need to forbid KDE from upgrading to plasma, at least until these migration pains are sorted. (Both related to VirtualBox-Kernel and VirtualBox-Plasma)
Immediate ask is instructions to exclude anything&everything related to KDE5, and stick to kde4, while the permanent solution would be to configure the new-and-new system in such a way that I can run a Code:#slackpkg update&install-new&upgrade-all&clean-system periodically with properly adjusted blacklist, without fear.
Whether the latter part just requires time or some configuration, I don't know.
I have an USB with issue of "current" from August 2019 with a 4.19.69 kernel and software that was "current" at the time.
After installing the old and upgrading, I found that the new kernel is having problems with VirtualBox, which is a must currently!
Vice-versa, mixing old kernel with new packages doesn't resolve the issue either, because apparently the old kernel is too old again to work with some of the new packages that come with plasma.
What, +almost+, works? Old kernel, old software but then I lose other important things like Thunderbird which is not the goal. (GMail wouldn't let me set up an account simply because my thunderbird of last year is too "insecure" for their IMAP)
From my point of view, the only reasonable solution for immediate resolution is old kernel, old packages which I will allow to be upgraded (mainly the gcc and glibc) so that other programs work with it but I need to forbid KDE from upgrading to plasma, at least until these migration pains are sorted. (Both related to VirtualBox-Kernel and VirtualBox-Plasma)
Immediate ask is instructions to exclude anything&everything related to KDE5, and stick to kde4, while the permanent solution would be to configure the new-and-new system in such a way that I can run a Code:#slackpkg update&install-new&upgrade-all&clean-system periodically with properly adjusted blacklist, without fear.
Whether the latter part just requires time or some configuration, I don't know.