Bug 32300 - Plasma systemmonitor: helper is blocked from monitoring network speed
Summary: Plasma systemmonitor: helper is blocked from monitoring network speed
Status: REOPENED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-17 23:27 CEST by Morgan Leijström
Modified: 2023-09-18 00:11 CEST (History)
1 user (show)

See Also:
Source RPM: plasma-workspace-5.27.5-5.mga9.src.rpm
CVE:
Status comment:


Attachments

Description Morgan Leijström 2023-09-17 23:27:12 CEST
Launching /usr/bin/systemmonitor (directly or by CTRL-ESC)
I have added columns for uppload and download speed.
In those columns no results for any process, despite real activity on my ethernet port (surfing, files sync, bittorrent...)

This was working in Mageia 8.

Launching it in terminal, output:

org.kde.ksysguard.plugin.network: Helper process terminated abnormally: "The process doesn't have permission to open the capture source"


Version-Release number of selected component (if applicable):
plasma-workspace-5.27.5-5.mga9
Comment 1 Dave Hodgins 2023-09-17 23:50:57 CEST
The package dumpcap (used by wireshark) must be installed and the user must
be a member of the wireshark group to access the network traffic for analysis.
Don't forget to logout/in or reboot after adding the user to the group.

CC: (none) => davidwhodgins
Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 2 Dave Hodgins 2023-09-18 00:07:34 CEST
Reopening. With the user in the wireshark group it shows the network rates
in the overview, but not in the Applications table. It also doesn't show
the network activity in the processes table.

Resolution: INVALID => (none)
Status: RESOLVED => REOPENED

Comment 3 Morgan Leijström 2023-09-18 00:11:22 CEST
No special fiddling was needed in mga8.
This is just speed monitoring, which works in i.e gkrellm.

Note You need to log in before you can comment on or make changes to this bug.