Bug 422130 - Process names with spaces in them are displayed incorrectly
Summary: Process names with spaces in them are displayed incorrectly
Status: RESOLVED UNMAINTAINED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: ksysguard (show other bugs)
Version: 5.18.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-27 09:48 UTC by torokati44
Modified: 2024-09-23 21:00 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description torokati44 2020-05-27 09:48:36 UTC
SUMMARY

Process names with spaces in them are displayed incorrectly

STEPS TO REPRODUCE

1. Open a Firefox browser with a few tabs
2. Open ksysguard
3. Observe the Name column of the process table

OBSERVED RESULT

There are a few running processes listed with the name "Web", but the tooltip for them shows "Web Content".
If the "Display command line options" setting is enabled, the full name of "Web Content" is shown in the table as well - but without the command line options.

EXPECTED RESULT

Both the table and the tooltip always correctly shows the name as "Web Content", regardless of state of the "Display command line options" setting. There is no "Display command line options" option, as it does not really make sense, given that the process name can be different than argv[0], and there is a Cmdline column as well in the table.

SOFTWARE/OS VERSIONS

Operating System: Fedora 32
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.13.2
Kernel Version: 5.6.13-300.fc32.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-3632QM CPU @ 2.20GHz
Memory: 15.5 GiB of RAM
Comment 1 Christoph Cullmann 2024-09-23 21:00:00 UTC
ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task.

If your issue still happens with the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!