I agree! I had to disable it. Its not important to me. I did a bug report!
https://bugs.kde.org/

1 members found this post helpful.

Personally, I'm fine with KDE being removed, though I do like the idea of replacing it something Qt-based that is more lightweight and simple, like LXQt or Lumina. I would still probably use KDE apps as long as they were still available from ktown.

The baloo indexer is known to spike from time to time (consuming 100% of a CPU core) but that is not all the time as far as I am aware.
Disabling Baloo is not required. This issue can be mitigated by disabling file content indexing in the System Settings. That way, Baloo remains functional but file content is no longer searchable.
On my machine, I do see the occasional CPU spikes caused by the Baloo file indexer if I add new file content, but that is always temporary.

3 members found this post helpful.

Personally, IF the KDE4 will be removed, I believe then we should chop every bit and bolt of KDE and Qt and related things.

Compared with GTK, which was still used by things like GIMP or Firefox after GNOME was removed, the Qt is not used anymore by Slackware if you remove KDE4.

So, I for one I believe on a pure XFCE/GTK Slackware, and to forget at all about this bunch of crazy hippies who believe that they are kings of the World.

Seriously? Including the freaking Chromium as a subsystem in Qt? Why not include also the Linux Kernel and call a day?

Who needs Qt things can find them already in SBo and Eric's smithy...

Good advice as could be expected from Eric.

I might add that I don't really need baloo's file content indexing capabilities. If I need some serious search I invoke kfind and that's it.

Off topic, locate grep and find work pretty well here

1 members found this post helpful.

QT is a big enough library that without it, I think it would hurt Slackware. Enough people don't like qt5 things now due to the incredible compile time needed to build it (and not everyone is aware of Eric's package for it). What does it hurt to include it except for some extra harddrive space?

If KDE is removed, it makes sense to keep qt5 and possibly provide a simpler qt5 WM/DE.

3 members found this post helpful.

Not that my vote counts for much... I 100% agree. If it is time to drop KDE, then add something, BUT it has to be simpler to maintain than KDE.

I've seen Qt5 crash my systems by overheating and then eating all the ram during compile over the years. Not to mention they require an internal version of ninja for their build process or that SBo and Alien Bob still provide an EOL Qt version with known security issues...

That said enough programs are using it now that even if I very much wish it would go away entirely I am forced to deal with it.

Excuse me, but there is a rule that the Slackware should use Qt apps?

Like the past demonstrated, the Slackers learned very quickly how NOT to use GNOME apps, thought...

I am not PRO for removing KDE4 unless it does not compile anymore, BUT if it is removed, again: I believe everything associated should be gone. Those interested on Qt apps will find them for sure.

All hail for a pure XFCE/GTK Slackware! I am glad that the Plasma5 usage opened my eyes about this beautiful gem given by Slackware already.

Where did I say there was a rule? But gnome and qt5 are quite different. What you're suggesting is the equivalent of removing KDE but still wanting KDE apps. That's not what I was suggesting. qt5 is a library, not a WM/DE. Many, many programs rely on qt just as many rely on gtk. Just because Pat removed Gnome didn't mean he removed gtk from the distro.

I'm just saying that such a major library shouldn't be removed from Slackware even if KDE is removed, and if KDE is removed, it'd be nice to have a lightweight qt5-based WM/DE take its place.

Thank you for the recommendation, I'll try that!

That is all fine as your opinnion but you have to look at the bigger picture. A lot of software that isn't apart of Slackware (FOSS or proprietary) requires QT in some capacity. So we are going to leave those projects out in the cold?

Another thing you fail to realize is that we need to have options when it comes to window managers and desktop environments. Something like LXQT or LXDE fits well with Slackware and for the most part checks all the boxes that were checked by KDE.

A bit off topic for this thread. If this route is taken then Xfce needs to be filled out more with "one task each" type of applications. Pat will be ading some kind of software no matter what route he takes.

2 members found this post helpful.

You either have no idea what you are talking about or you are being willingly ignorant...

I have installed 0 KDE programs and dislike Qt enough to use it as little as I can, yet I still have 15 programs built against Qt5 and 7 Qt4 programs (Not counting those included in the main tree). Using Qt4 or Qt5 does not mean you use KDE just as much as using gtk+3 does not mean you use gnome and it would be great if you can stop spreading misinformation.

5 members found this post helpful.

I'd like to have qt5 libraries at least but not the 5.9 branch at the moment. I am having issues with the 5.9 branch of qt. 5.9.6 introduced a dock widget bug that affected QMPlay2 (Jun 27 comment).https://codereview.qt-project.org/#/c/209128/

The bug is not found in the qt5 5.11 branch. I'm tempted to switch to the testing branch of ktown but for now I am waiting to see what happens. I built myself a qt5 5.9.5 library last month.