https://bugs.kde.org/show_bug.cgi?id=404119
Richard Llom <richard.l...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO |WORKSFORME
--- Comment #4 from Richard Llom <richard.l...@gmail.com> ---
(In reply to naroyce from comment #3)
> That reply would've been more helpful sooner rather than over 1 month.
>
> I ended up updating my system which also required a reboot and I haven't had
> the issue.
>
> That was the ONLY time I've ever noticed the issue which is why time was
> important in getting it debugged to figure out the cause.
>
If you need urgent help, the bugtracker is *really* not the place to go. KDE
provides a forum, MLs, IRC and matrix channels - and archlinux as well. Which
are actually intended for live support, whereas the bugtracker is not.
> I don't recall if I had done the "new tab" in ksysmon, but given that the
> sensor widget also reflected the same issue, I'm led to believe the issue
> lay with whatever data source they got their information from... and THAT is
> what I'd like to know.
>
You can find a link to the source here:
https://kde.org/applications/system/ksysguard/
(under Development Information)
For further assistance please use one of the support channels mentioned above.
--
You are receiving this mail because:
You are watching all bug changes.
