@orbitz @m4 You don't need to be running the desktop environment to run the app, you only have to have it installed. Like, KDE apps require (some parts of) KDE to be installed, but typically work fine even if you're running Gnome instead of KDE, and vice-versa.
Apps do tend to look and feel a little smoother if you use them in their "native" desktop environment though.
@Moshpirit ๐
If you have any experience with computer programming, I would definitely recommend looking up a tutorial on threads for your favorite programming language and writing a little program that uses them. The best way to understand what threads are is through practical experience.
If not, hopefully you can find some good resources anyway! The gist is that threads are kind of like little mini-programs that run within a main program and can be used to do specific tasks that would otherwise "distract" the main program from its work. (That's not exactly accurate, but it's the best way I can think of to explain the basic idea in one sentence.)
@mvirts @Moshpirit Yep, htop shows threads in green, so all of those shown in the image (except the first one probably) are threads. You can turn off display of threads in the settings.
Or, if you enable tree display, the threads will display as children of their process.
@mfraz74 @Bro666 @rriemann @kde@floss.social @kde@lemmy.kde.social Gotcha. Well, I use Gentoo so I would be compiling it anyway. Sounds like I should take a look at it again ๐
@mfraz74 @Bro666 @rriemann @kde@floss.social @kde@lemmy.kde.social Is Amarok still maintained? I thought it was dead. I used to love it but I had to give it up when I couldn't run it anymore.
@Fleppensteijn @Max_P The change in the first component of the version number from 5 to 6 is what could have tipped you off. I mean, admittedly there's no universal standard for software versioning that everyone follows, but the closest thing there is to a commonly adopted standard (https://semver.org/) says that when the first component of the version number changes, it's a big deal and things might break. (Or, a relatively big deal, but just how big that is in practice depends on the package.) If you didn't know to look out for that, now you do. ๐
Unless by "average user" you mean someone who relies on automatic updates and doesn't look at what's getting installed. Which is fine, but if you're allowing automatic updates, you have to understand you're giving up the ability to catch stuff like this before it happens. (This situation could certainly be improved, but generally that's the state of things right now.)