| Summary: | ksysguard can display the wrong process name, etc. | ||
|---|---|---|---|
| Product: | [Unmaintained] ksysguard | Reporter: | kdebugs |
| Component: | ksysguard | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | sstewartgallus00 |
| Priority: | NOR | ||
| Version First Reported In: | 4.11.3 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | screenshot | ||
|
Description
kdebugs
2014-02-06 07:14:00 UTC
Created attachment 85019 [details]
screenshot
I think I have a similar problem. When one uses the fexecve library call (which is emulated by GLibc by execveing a file in /proc/self/fd) one gets the file descriptor number for the name of the process (which is silly). I suspect ksysguard uses the value of Name: in the status file and I believe ksysguard should use the name of the file that the exe symlink in the proc directory points to or the first value in cmdline. Steven, comment #2 sounds like you could be qualified to check the ksysguard code and propose a patch? :) Sure I'd love to take a look at the source. I'm having trouble finding the homepage and source of it though. Steven, thanks for your offer. ksysguard is part of the KDE Workspaces, so there is no separate homepage. The source for the Qt4-based version is here: https://projects.kde.org/projects/kde/kde-workspace/repository/show?rev=KDE%2F4.11 (ksysguard is split, you will find its files in "ksysguard" and "libs/ksysguard") I could forward port the patch to the Qt5-based version. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. 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. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |