| Summary: | crash when selecting sensor for modified tab | ||
|---|---|---|---|
| Product: | [Unmaintained] ksysguard | Reporter: | spam_detect |
| Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
spam_detect
2013-09-24 08:59:17 UTC
I cannot reproduce. When I create the second row, a "Drop Sensors Here" appears, but I cannot right-click it. If you find exact steps to reproduce, please add them. (In reply to comment #1) > I cannot reproduce. When I create the second row, a "Drop Sensors Here" > appears, but I cannot right-click it. If you find exact steps to reproduce, > please add them. I just tried, and you are correct. I was not able to reproduce this either. I probably right-clicked the existing, populated, 1st row - not the empty second row. I wasn't taking notes, of course, when this happened, as it wasn't planned. So I might have right-clicked the 2nd row. Then I would have selected Properties, and then Sensors. Sorry I am not sure even if this is what exactly happened. I do know I was trying to add another sensor, and i wanted a new row, but first accidentally added a column and then deleted it, then added a row. There was already a new 2nd sensor added to the top 1st row, so it had 2 sensors. Somewhere in this process of adding or moving the 2nd sensor from the top row to the empty bottom row, the crash occurred. I wouldn't rule out even moving another sensor from the list of available ones. I know this isn't the most helpful information, but it's the best I have. Also, the top (1st row) sensor was temperature, and the one I was adding was from Disk Throughput; probably Read Data (float), as I recall. The KDE version is 4.8.5, running on Ubuntu 12.04. 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 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! |