Bug 179812 - After longer period ksysguard stop monitoring and say: Connection to localhost has been lost
Summary: After longer period ksysguard stop monitoring and say: Connection to localhos...
Status: RESOLVED WORKSFORME
Alias: None
Product: ksysguard
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-06 16:41 UTC by Milan Krivda
Modified: 2022-12-15 05:14 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Krivda 2009-01-06 16:41:50 UTC
Version:           4 (using 4.1.87 (KDE 4.1.87 (KDE 4.2 >= 20090101)) "release 1.1", KDE:KDE4:UNSTABLE:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.7-9-default

After longer period of using ksysguard stop monitoring, draw random numbers in sensors and say: Connection to localhost has been lost.

Screenshots are in this gallery: http://picasaweb.google.com/milan.krivda/KDE4Bugs#

On first screenshot is ksysguard normally running.

On second is ksysguard with error message.

On third is ksysguard after connection refused and with random sensors values.
Comment 1 Dario Andres 2009-05-17 02:43:17 UTC
This reminds me bug 154356
Comment 2 Sebastien Martel 2009-07-18 23:03:11 UTC
Could you tell me how long on average you have to wait before this happens?
Comment 3 Julian Steinmann 2018-02-22 10:33:36 UTC
Is this still a problem (theoretically it should have been fixed together with bug 154356)? If yes, how long do you need to wait to trigger the bug?
Comment 4 Justin Zobel 2022-11-15 22:58:25 UTC
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!
Comment 5 Bug Janitor Service 2022-11-30 05:14:18 UTC
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!
Comment 6 Bug Janitor Service 2022-12-15 05:14:29 UTC
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!