Perhaps you should read a bit on the LTS roadmap. You'll see that there is a plan, with updates spread further apart than the one-month cycle for the bleeding edge, and there's the dedication to keep releasing updates for at least 2 years. Only bugfix releases, no backports. It's not just a label.

https://jriddell.org/2017/06/07/plas...er-kicked-off/
https://www.kde.org/announcements/plasma-5.12.0.php
https://community.kde.org/Schedules/Plasma_5

5 members found this post helpful.

Balls.

Vader has crystalline balls.

1 members found this post helpful.

He also has an IT-O Interrogator! http://starwars.wikia.com/wiki/IT-O_Interrogator

He also has the shittiest graphics card of mankind.

2 members found this post helpful.

He has several graphics cards from a certain AMD family. Aparently, he's oriented to low power "desktop" cards, because no one of these enumerated by him consumes more than 20W.

And yes, he's right. Even a complex desktop environment like KDE4 or Plasma5 must and should work with these graphics cards, as demonstrated by KDE4 and Plasma 5.13.1

I will agree, someone needs a pair of balls to say that the King wears nothing when this is so obviously.

And I can confirm this prime time, because myself I have an AMD Radeon HD 4350 GPU, which works with Slackware with both KDE4 and Plasma5 - since 5.13.1. And Windows 10.

What I find interesting is that the single computer where any Plasma5 works is an Intel.

Also I have a third computer, having an NVidia GeForce 210, an AMD Athlon 7850 CPU and 4GB RAM, where I am stuck on Nouveau and the lower clocks that card can, which apparently works with Plasma5 - but trying to install the propietary drivers from SlackBuilds.Org ended with an uterly failure, and a unusable Plasma5 desktop. Maybe my knowledge is limited, but NVidia looks being very dificult to setup, compared with AMD Radeon and Intel.

Maybe the AMD Radeon cards are "dog fooding, so to speak" as Patrick Volkerding said, and like @stoffepojken said, they are shittiest in the world, but today they are the single discrete alternative which have actively maintained open-source drivers given by producer. If not Radeon, then what? On-board Intel which force you to go for an Intel CPU? Nouveau is still at the level of a hack.

And Eric Hameleers biasing toward the NVidia cards does not help us too much to get a fully functional Plasma5 on AMD Radeon cards, either LTS or not.

1 members found this post helpful.

I think you misunderstood what he meant by that.

Please see this link for a description of the terminology used: https://en.wikipedia.org/wiki/Eating_your_own_dog_food
Again, I think you misunderstood. That was the textbook definition of sarcasm.

1 members found this post helpful.

Let's give credit where's the credit. Eric's also the Vader[1] of Plasma 5.13.1

However, I hope that's not his illegitimate (brain-)child about he's embarrassed...

[1] believe or not, that's literally "Father" in Dutch language.

Yeah, man! BUT 5.12 LTS is buggy and does not work, plain and simple. And it will never work, because they will never backport half of 5.13.

I do not blame you, I do not blame someone from Slackware, it is just the last one series compromised by the poisoned breath of Martin Gräßlin, before the Three Letters Companies[1] of KDE hit his sorry ass.

Let's step along. I believe that the KDE future is bright, after they discovering this (corporate?) mole.

[1] VDG anyone? and a "non-existent" K Usability Group

1 members found this post helpful.

OK. So what KDE Bug reports are yours? Can you give me the numbers or URLs? If a bug report gets more people on cc that are following it, or if more people than you alone comment on the bug, that's the first step to getting more attention on solving it.
And I am not talking about backporting new functionality from 5.13.x... that is never going to happen. But actual bugs, those should be in scope of the LTS support.

1 members found this post helpful.

Mr. Hameleers, permit me to doubt that they aren't aware about certain issues, considering that they fixed them in 5.13.x

And you aren't the one who said from your own experience that they ignore as being irrelevant the bug reports from Slackware, because it lacks certain features present in other 99% of Linux distributions?

Well, probably that's real reason why he send us to put bug reports instead.

I heard that last time he made that, the endeavor ended with a nervous breakdown first class, with middle fingers everywhere and carpet bombing of FU words...

OK, it was something about SDDM or similar, and SystemD hard dependencies.

Always an excuse to not report bugs. How much time have you spent on here ranting about it, when you could have put in 10% of that time towards something useful? Your act is getting really old, and really annoying. Frankly, I'm surprised people actually entertain your complaints about this anymore.

1 members found this post helpful.

And what the heck you believe I made here, even in this thread, even showing screenshots? Ranting or reporting bugs?

I tell you what I made here if isn't obviously: bug-reporting as Slackware user to Slackware maintainers and packagers.

AND, as a former distro maintainer, I know well that next the ball is on distro maintainers side. Firstly, they would decide if the issues are mainstream or distro sided. If is worth keeping a particular version or rolling back.

Then they should talk with mainstream, who will ask about build flags, the features which are enabled and/or disabled at build-time, conditions when the bugs appear or not, and other shiny things.

These information aren't usually accessible for an user, but for maintainers; who compiles and sums the gathered data about usage and bug-reports, and knows well how the heck they built the software.

This how the things are done.

2 members found this post helpful.

No, that's not how things are done. You know well that the bug is on the software side, not the packaging side; otherwise you would have been complaining that Eric is a bad maintainer instead of spreading FUD that the KDE devs don't know what they are doing or that they are beholden to corporate interests or whatever. You are the one with the hardware that produces the error, not Eric. Moreover, Eric has asked you multiple times to report the bug, so obviously he does not agree with your take. Yet here you are, ranting, complaining, spreading FUD, with precious little of what you post actually representing useful information, and always coming up with an excuse for why someone else should put in the actual work.

3 members found this post helpful.

Aye. Or done his homework before he bought a shitty card and blame everybody else for what everybody in the Linux and Windows worlds know: Darth Vader bought a lemon video card.

1 members found this post helpful.