https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #55 from Riccardo Robecchi ---
Yes, this appears to do it! CPU usage is now down to about 10% when idle. Still
a bit high, but definitely a huge improvement compared to the previous state.
Thanks Arjen for your work!
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
|
https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |
|ug.cgi?id=493902|
https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=434877
Alexander Wilms changed:
What|Removed |Added
CC||f.alexander.wi...@gmail.com
--
You are recei
https://bugs.kde.org/show_bug.cgi?id=434877
prettyvani...@posteo.at changed:
What|Removed |Added
CC||prettyvani...@posteo.at
--
You are re
https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
CC||peter.eszl...@gmail.com
--- Comment #52 from Nate
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #51 from Mark ---
(In reply to neobrain from comment #50)
> (In reply to Nate Graham from comment #44)
> > We know this is an issue; that's
> > why it's open and in the CONFIRMED state. Further criticisms don't help
> > anything. if you want
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #50 from bugs.7n...@aleeas.com ---
(In reply to Nate Graham from comment #44)
> We know this is an issue; that's
> why it's open and in the CONFIRMED state. Further criticisms don't help
> anything. if you want to help, try to fix it.
Thanks
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #46 from David Redondo ---
I marked a comment as spam not because of mentioning of alternatives but the
clear violation of the code-of-conduct.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #47 from David Redondo ---
The lm-sensors information being is interesting and new to me. As I never heard
about or seen it in a flamegraph and very surprising as ksysguard or
plasma-systemmonitor dont interact with lmsensors themselbes but
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #49 from Mark ---
I don't consider it heated, contested or hostile at all...
Anyhow, the offer stands. If a return of KSysGuard is acceptable then I'm
willing to put in the time and effort to get that done.
It is not a long term solution, I
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #48 from David Redondo ---
As a general point of information the more rude the conversation in a bug
report the less likely developers are inclined to look at it and fix it. Nobody
wants to spend their (often free!) time reading a heated dis
https://bugs.kde.org/show_bug.cgi?id=434877
Ville Aakko changed:
What|Removed |Added
CC|ville.aa...@gmail.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #45 from Mark ---
(In reply to Nate Graham from comment #44)
> if you want to help, try to fix it. If you can't, then the most
> helpful thing you can do is avoid publicly complaining on the bug tracker.
Is a return of KSysGuard acceptable?
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #44 from Nate Graham ---
Bugzilla isn't a forum, it's a place for bugs to be tracked and discussed with
a bias towards getting them resolved. We know this is an issue; that's why it's
open and in the CONFIRMED state. Further criticisms don't
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #43 from Mark ---
I see no comment i'd consider spam. But i do see some being marked as such.
It's sad imho.
Much of the comments here are criticism but in a, in my opinion, fair manner.
I think it's oke to criticize a product where it's i
https://bugs.kde.org/show_bug.cgi?id=434877
postix changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=434877
postix changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #42 from Ville Aakko ---
I suspect from the comments (someone involved in the project correct me if I'm
wrong) that System Monitor will not be fixed. It's codebase seems too hairy,
no-one seems to actually know what the real issue is properl
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #41 from Steve Vialle ---
(In reply to David Redondo from comment #39)
> Just for the people ranting here: ksysguard and plasma-systemmonitor use the
> same code to gather data about processes
Just for the people defending systemmonitor her
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #40 from Riccardo Robecchi ---
(In reply to David Redondo from comment #39)
> Just for the people ranting here: ksysguard and plasma-systemmonitor use the
> same code to gather data about processes (libprocesscore from libksysguard)
It is,
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #39 from David Redondo ---
Just for the people ranting here: ksysguard and plasma-systemmonitor use the
same code to gather data about processes (libprocesscore from libksysguard)
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=434877
Steve Vialle changed:
What|Removed |Added
CC||stev...@runbox.com
--- Comment #38 from Steve Vi
https://bugs.kde.org/show_bug.cgi?id=434877
Robert G. Siebeck changed:
What|Removed |Added
CC||kde.bugzilla.2...@r123.de
--
You are recei
https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
CC||lainli...@gmail.com
--- Comment #37 from Nate Gra
https://bugs.kde.org/show_bug.cgi?id=434877
postix changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #36 from Mark ---
(In reply to Méven Car from comment #35)
> I think this shows we shouldn't use vmaps to compute memory usage.
> Albeit the best data we can get, we should either lower its frequency update
> or use another method altogether
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #35 from Méven Car ---
I think this shows we shouldn't use vmaps to compute memory usage.
Albeit the best data we can get, we should either lower its frequency update or
use another method altogether.
https://invent.kde.org/plasma/libksysgu
https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
Summary|High CPU usage |System Monitor has high
|
30 matches
Mail list logo
