How many KDE sessions are you running? Maybe post systemctl status run as root?
this post was submitted on 27 Jan 2024
31 points (97.0% liked)
KDE
5305 readers
56 users here now
KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
Plasma 6 Bugs
If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
founded 1 year ago
MODERATORS
Thanks for replying! Only one session. Running systemctl status as root gave me this result. I could only find one /usr/bin/kwin_x11 --replace (ID: 4426) entry, though when I can see many others: 4426, 4427, 4429, 4430, 4433, 4434, 4436, 4442, 4443, 4444, 4445, 5871 10277, 10278, 10279, 12222, 12223, 12224, 12225, 12226, 12227 and 12228.
You know I bet those are just the threads kwin is using, since memory usage is all the same. Linux threads are just processes that share everything. You may be able to look at your top (htop?) Options to show threads separately or together?
@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.
@[email protected] @[email protected] thanks for the info! I had no idea of the existence of threads! TBF I don't even know the reason of their existence, but I'll check it out :)
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.)