Description: This plasmoid is an enhanced QML/C++ implementation of my BusyTasks program. It displays the most active process for each of the four computer components: processor, memory, harddisk and network. Similarly to the Java app, it uses iotop and nethogs as data sources. It is intended and optimised for use in a horizontal control bar! There are thousands of downloads, but not a single comment/rating - please give some feedback! Please note that this version is optimized for X11. (Wayland may not work)
REQUIREMENTS: –IOTOP or IOTOP-c –NETHOGS Both programs are usually easy to install with the help of your package manager.
You need to set the superuser password in the configuration in order to start iotop and nethogs. For more documentation, please see the manual.
starting having plasmashell crashes and used gdb to isolate the problem to this plugin on plasma 6. BusyTasksPlugin.cpp:299: https://pastebin.com/qMQnnpAQ
Hi, thanks for the report.
Just for the record: please note that this is the plasma 5 section of the plasmoid. You should not use a plasma 5 plasmoid on plasma 6. If you indeed use the plasma 6 version from https://www.pling.com/p/2153869 then you just reported on the wrong site.
At first glance I can tell that this is a problem with data processing from iotop. More precisely, you are obviously using a java app called CLion with a long command name, which I suspect to crash BusyTasksPlugin. Of course, this should not happen, it's an annoying bug.
To resolve it, I need a bit more info. How long do you use this plasmoid? Did it already work in the past? Does it just randomly crash, or only when CLion is running? Could you start "sudo iotop -Pkqqbo" in a terminal, then open CLion and afterwards post the output?
Thanks in advance.
yes I think I was using plasma 6 version but this version just showed first on google. and I used CLion to debug plasmashell, I didn't have CLion installed before and it was crashing multiple times a day. I used it for months without issue
Good to know that it worked for months, sad to know there is a problem. As far as I can tell from the bug report, there is a high probability CLion actually crashed BusyTasksPlugin, at least for the reported incident. As a consequence the crashes before may have got another source within BusyTasksPlasmoid or may not even be related to this plasmoid after all.
New line characters in a program name screwed up data retrieval from iotop. Although they are supported by some OS, it's really not a wise choice to integrate such reserved symbols in the name of an executable. After some severe tossing and turning I found a way to allow this unusual situation. Please upgrade ( from https://www.pling.com/p/2153869 ) and give some feedback. You may have to restart the whole computer in the process. Plasma caching is a pain in the ass sometimes.
sorry I don't care to test your plasmoid. I need my OS to be reliable and it is very difficult to troubleshoot plasmoid crashes. But it is good you have fixed it as many others may have run into this issue
First of all, thanks for the report and your replies. Let's at least hope it is fixed. Many people just use a software and if it doesn't work, they just get rid of it without giving the developers any chance to fix it. I have been using this plasmoid for years on several OSs and even though I am quite an exemplary tester, I can't deal with all of the use cases and environments people may use. This is why feedback is still important!
Ratings & Comments
11 Comments
starting having plasmashell crashes and used gdb to isolate the problem to this plugin on plasma 6. BusyTasksPlugin.cpp:299: https://pastebin.com/qMQnnpAQ
Hi, thanks for the report. Just for the record: please note that this is the plasma 5 section of the plasmoid. You should not use a plasma 5 plasmoid on plasma 6. If you indeed use the plasma 6 version from https://www.pling.com/p/2153869 then you just reported on the wrong site. At first glance I can tell that this is a problem with data processing from iotop. More precisely, you are obviously using a java app called CLion with a long command name, which I suspect to crash BusyTasksPlugin. Of course, this should not happen, it's an annoying bug. To resolve it, I need a bit more info. How long do you use this plasmoid? Did it already work in the past? Does it just randomly crash, or only when CLion is running? Could you start "sudo iotop -Pkqqbo" in a terminal, then open CLion and afterwards post the output? Thanks in advance.
yes I think I was using plasma 6 version but this version just showed first on google. and I used CLion to debug plasmashell, I didn't have CLion installed before and it was crashing multiple times a day. I used it for months without issue
Good to know that it worked for months, sad to know there is a problem. As far as I can tell from the bug report, there is a high probability CLion actually crashed BusyTasksPlugin, at least for the reported incident. As a consequence the crashes before may have got another source within BusyTasksPlasmoid or may not even be related to this plasmoid after all.
New line characters in a program name screwed up data retrieval from iotop. Although they are supported by some OS, it's really not a wise choice to integrate such reserved symbols in the name of an executable. After some severe tossing and turning I found a way to allow this unusual situation. Please upgrade ( from https://www.pling.com/p/2153869 ) and give some feedback. You may have to restart the whole computer in the process. Plasma caching is a pain in the ass sometimes.
sorry I don't care to test your plasmoid. I need my OS to be reliable and it is very difficult to troubleshoot plasmoid crashes. But it is good you have fixed it as many others may have run into this issue
First of all, thanks for the report and your replies. Let's at least hope it is fixed. Many people just use a software and if it doesn't work, they just get rid of it without giving the developers any chance to fix it. I have been using this plasmoid for years on several OSs and even though I am quite an exemplary tester, I can't deal with all of the use cases and environments people may use. This is why feedback is still important!