Bug 183840

Summary:	ksysguard pops up "connection to localhost as been lost" on start up, not showing any info on CPU, network and memory history
Product:	[Applications] ksysguard	Reporter:	Maurizio <mrzfbb>
Component:	general	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	johnflux, lotusom-dev, mail, richard.llom
Priority:	NOR
Version:	4.7 and older
Target Milestone:	---
Platform:	unspecified
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=179812
Latest Commit:		Version Fixed In:
Attachments:	snapshot of pop-up window snapshot of system load tab snapshot of system load tab

Description Maurizio 2009-02-09 21:55:14 UTC

Version:           4 (using 4.2.00 (KDE 4.2.0), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.28-0.slh.2-sidux-amd64

when I start ksysguard, a pop-up window appears whit this message:
"connection to localhost as been lost"
when I open the "system load" tab, nothing is showed in the sensors fields
here is two snapshots
http://www.imgx.org/public/viewset/6298

Comment 1 Maurizio 2009-02-09 22:08:06 UTC

Created attachment 31164 [details]
snapshot of pop-up window

Comment 2 Maurizio 2009-02-09 22:09:13 UTC

Created attachment 31165 [details]
snapshot of system load tab

Comment 3 Maurizio 2009-02-09 22:10:22 UTC

Created attachment 31166 [details]
snapshot of system load tab

Comment 4 John Tapsell 2009-02-10 04:37:57 UTC

Hi Maurizo,

  Could you try closing ksysguard, then moving 
~/.kde/share/apps/ksysguard/*  and 
~/.kde/share/config/ksysguardrc

to somewhere else, and running ksysguard again?  Do you still get the problem?

Comment 5 Maurizio 2009-02-10 22:16:38 UTC

Hi John, thank you for your reply
I removed those files, but the problem persists

Comment 6 Sebastien Martel 2009-07-21 16:20:17 UTC

Hi Maurizio,

Is this still an issue, if it is could you issue the command "ksysguardd" and then when the prompt appear "monitors" and post the result.

Comment 7 Julian Steinmann 2018-02-22 12:47:53 UTC

Is this still a problem? Will close otherwise.

Comment 8 Richard Llom 2019-03-12 20:20:22 UTC

Closing as no user feedback since 2009.