Bug 447294 - Network speed statistics shown incorrectly when 2 connections are active
Summary: Network speed statistics shown incorrectly when 2 connections are active
Status: RESOLVED DUPLICATE of bug 481130
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: 5.23.4
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-20 16:20 UTC by boklutche
Modified: 2024-06-07 11:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Image of one interface with about 135Mb/s traffic and another with no traffic. (1.76 MB, image/gif)
2021-12-20 16:20 UTC, boklutche
Details

Note You need to log in before you can comment on or make changes to this bug.
Description boklutche 2021-12-20 16:20:02 UTC
Created attachment 144721 [details]
Image of one interface with about 135Mb/s traffic and another with no traffic.

SUMMARY
I have two wired connections active and one of them usually has no active traffic. I've configured a widget to show the composite upload/download statistics and the widget seems to cycle between the two connections when showing the traffic rather than add the traffic together. It also seem like the traffic is doubled. In attached image the actual Downstream traffic was 134 Mb/s.
The sensors used are Network Devices->All Network Devices->Download Rate and Network Devices->All Network Devices->Upload Rate

STEPS TO REPRODUCE
1. Add second active interface 

OBSERVED RESULT
Network traffic bounding between actual traffic and zero.

EXPECTED RESULT
Showing combined traffic.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  Debian testing
(available in About System)
KDE Plasma Version: 5.23.4 
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Arjen Hiemstra 2022-01-31 11:36:33 UTC
Are you using network manager?
Comment 2 boklutche 2022-01-31 14:49:54 UTC
Yes.
Comment 3 Arjen Hiemstra 2024-06-07 11:51:43 UTC
*** This bug has been marked as a duplicate of bug 481130 ***