| Summary: | Network speed graph y axis range changes to 0 - 2^64 after sleep | ||
|---|---|---|---|
| Product: | [Applications] plasma-systemmonitor | Reporter: | Mark Bolhuis <mark> |
| Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | minor | CC: | ahiemstra, nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Mark Bolhuis
2025-02-20 20:58:28 UTC
Assuming you have the graph set to "automatic" for its data range, the range is actually calculated based upon the data points in the graph, since there is no natural "maximum" for data rates. This implies there's a data point of 2^64 B/s in the graph, which likely happens due to time deltas jumping after restoring from sleep. Are you using Network Manager for network connections? . (In reply to Arjen Hiemstra from comment #1) > Assuming you have the graph set to "automatic" for its data range, the range > is actually calculated based upon the data points in the graph, since there > is no natural "maximum" for data rates. This implies there's a data point of > 2^64 B/s in the graph, which likely happens due to time deltas jumping after > restoring from sleep. Are you using Network Manager for network connections? Yes I am using NetworkManager, and the graph is set to automatic. At the time I reported this there weren't any visible data points on the graph. It stayed blank. I have checked again and after logging back in the graph y-axis does still change to 0-2^64 but now see some data points that would cause that. So your assessment is probably correct. ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! ๐๐งน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |