I don't test with NVIDIA's driver.
I don't test with AMD's official driver.
I don't test VMWare's kernel stuff.
I don't test those and lots of other stuff because I don't have the (non-free) hardware or software to do so.
That will not change.

I can't speak for Pat, as I don't know what hardware he has exactly, but this expectation you seem to have of him to test a new kernel with NVIDIA's non-free software is unreasonable.

8 members found this post helpful.

I don't test with NVIDIA's driver.
I don't test with AMD's official driver.
I don't test VMWare's kernel stuff.
I don't test those and lots of other stuff because I don't have the (non-free) hardware or software to do so.
That will not change.

I can't speak for Pat, as I don't know what hardware he has exactly, but this expectation you seem to have of him to test a new kernel with NVIDIA's non-free software is unreasonable.

8 members found this post helpful.

I'm surprised that this surprises you.

1 members found this post helpful.

Who was talking about you. This was About Pat pushing a show killer and not noting it. Stop it. It is Pat's changelog.
do not harass me again. This is a slackware forum. And this is Abouts Pat's WORK. not yours. I support his work. I care less If he likes me or not. Makes me think. You Sir Are Out of line. We the slackware supporters ask wtf wtf Pat. Get with it KISS. heads up nvida broke dudes.

It's getting late and I am tired so maybe I am not understanding the problem Drakeo is having. The nvidia driver is not building with 4.4.11? As I stated in another post this was fixed 14 hours ago...

https://www.linuxquestions.org/quest...4/#post5801515

I do not have a problem. I was reporting Pat pushed a show killer with out a note. Slackbuilds is far from slackbooks.
KISS I am disappointed this much work in a kernel and no note the nvidia installer is broken.
None of those links you pushed sir are from this years nvidia blob.
Be so kind to learn what a changelog is for.
Ask your self Why would I care.

Dude now you are pissing me off. The first link was wrong, I said that, READ the other two, this is fixed! It's late and I am trying to finish up my work so I posted one wrong link then immediately corrected it. If you are too lazy to patch 6 lines of code in one file then just sit there and wait for nvidia to release a new version and stop complaining because Pat didn't take the time to inform you something might break on the TESTING branch of Slackware.

nvm push the link to the latest. it is a forum 0 and 1. kiss
current is not testing. learn current can break at any time you want to follow in RWorkmans foots steps. Wtf dude type sh NV the fill out the log. What is a log.? Why do we have them.
Yes Pat let me down. 2 times in 20 years stuff happens . Better than my mom.
She dead

Which driver are you using?
I have 2 different computers with different NVidia drivers (one is legacy 304.xx and the other is 384.xx) and they are working great with Linux Kernel 4.14.x. You just need to find the patches for the version you used and it's already available for some time

4 members found this post helpful.

-current is the ongoing effort of developing, *testing* and stabilizing the next Slackware release. It is *not* a rolling release that's supposed to work all the time. There *will* be breakage of various things all over the place. It's inevitable because nobody can account for everything. That's why we expect people running -current to be experienced and mature enough to test and verify *their* particular use-case(s) and report to us when something is broken, preferably already with a proposed solution.

So, in your case, instead of ranting on and on about how the breakage with the proprietary nvidia driver was not noted in the changelog, you should've just calmly noted that the latest kernel update doesn't yet work with it. Ranting won't fix anything.

11 members found this post helpful.

Current releases of sqlitebrowser are Qt5 based (https://github.com/sqlitebrowser/sql...er/BUILDING.md).
SMtube is now also Qt5 based (https://www.smtube.org/).
I have a Qt5 based Krusader in my own Plasma 5 repository.
Krename development in git is based on Qt5 and KF5 (https://cgit.kde.org/krename.git/tree/CMakeLists.txt).
Firetools supports both Qt4 and Qt5 (https://github.com/netblue30/firetools)
About qtgzmanager, I don't think there was any development for multiple years and the last couple of releases were only done to add new Slackware versions it should support. Time to say bye-bye.

So you're mostly good.

2 members found this post helpful.

If you want a stable system, run Slackware 14.2.
If you decide on slackware-current, then - as I have told countless times - you are considered to be a Slackware BETA-TESTER. We (Slackware team) expect that if you run slackware-current, you accept that things can break suddenly without immediate fix, and we also expect that you are able to fix issues yourself and get your computer back to a workable state.
Read https://docs.slackware.com/slackware...rrent_versions please.

Like Robby said: slackware-current is not a rolling release model. It is where development happens. It is much more stable than development versions of other distro's, but this is NOT a stable release. If proprietary software can not cope with updates in Linux land, then too bad ans we will have to wait for them to fix their shit.
It's not like this is the first time this happened... I have had multiple occasions where I had to revert to a previous kernel temporarily in order to avoid losing my GPU-accelerated desktop.

9 members found this post helpful.

Another tool ported on kf5, kbackup:

https://www.linux-apps.com/p/1127679/

Hi,

Thanks for checking it out.
I guess qtgzmanager maintainer will easily follow the suite.
I'm all set ;-)

There are couple of more stock packages that depend on Qt4, but they are rather active projects, so no doubt they'll adapt or already support Qt5.

--
Best regards,
Andrzej Telszewski

We all been here. Think pat Worked on that Kernel that long and did not have an issue made me look very hard at the two systems I run current. So This is A Learning Curve. About The Lead. My First post asked wtf and is it me or Pat.;
You all seem to think it is my system. OK. Great Thanks for the help. Back to the winter,

No, it is not that we think it's your system. It's the way you seem to be looking at slackware-current, expecting updates to be fully tested against everything that is NOT part of Slackware itself.
That is not how it works. The development cycle between two stable releases (14.2 and 15.0 for instance) is called "slackware-current" and if you use that development version you are a tester. Period.
You can expect that on release of Slackware 15.0, it probably contains a kernel that is supported by the Nvidia drivers, but even that compatibility will not be tested by Pat or the Slackware team.
And if it is tested and it's proven that Nvidia drivers are not compatible, that's still not a reason to delay updates. Slackware-current is always the bleeding edge and sometimes, it bleeds until 3rd parties get their act together.

You, the user/admin, are responsible for keeping a Slackware-current system functional. If you distrust -current updates because of potential incompatibilities (Nvidia for instance) but you want to run slackware-current regardless, then the best advice is to NOT immediately apply updates. Rather, you wait a day, check this LinuxQuestions.org forum for any reported issues, and eventually you update your computer when you are confident that there is no major breakage.

And a final advice. In case of kernel upgrades, ALWAYS keep a working kernel installed. NEVER use "upgradepkg" or "slackpkg upgrade-all" to upgrade from your working kernel to the next one. If you use slackpkg, make sure to blacklist "kernel-generic", "kernel-huge" and "kernel-modules".
My boot menu always contains at least two kernel choices. If the new kernel does not work or creates issues, you can safely go back to your previous kernel.

I do not understand why you were so pissed at Slackware and Pat. It was unwarranted.

6 members found this post helpful.