| Summary: | Connection to localhost has been lost! | ||
|---|---|---|---|
| Product: | [Unmaintained] ksysguard | Reporter: | Peter Bruley <pbruley> |
| Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | michael_maennel |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Peter Bruley
2003-01-30 17:32:49 UTC
After looking at a different system I noticed that when ksysguard is started it is supposed to notice that ksysguardd is not running and kick it over. Apparently my ksysguardd was not starting automatically. I got ksysguard to work properly again by doing this: 1) make sure that /opt/kde/bin was in my PATH. 2) rm -f ~/.kde/share/config/ksysguardrc 3) rm -r ~/.kde/share/apps/ksysguard ksysguardd should be installed in the same PATH like the frontend, so ksysguard should normaly work Yes you are correct ksysguard was found in my path and ksysgaurdd is in the same path so I guess it was just removing the files in step 2 & 3 above that was the true fix. I have the same error. But, removing the files above don't help. I tried running ksysguardd seperatly, and it segfaults. bt: Program received signal SIGSEGV, Segmentation fault. 0x40026bc1 in sensors_get_all_features () from /usr/lib/libsensors.so.1 (gdb) bt #0 0x40026bc1 in sensors_get_all_features () from /usr/lib/libsensors.so.1 #1 0x08050ba6 in initLmSensors () #2 0x0804aceb in initModules () #3 0x0804ad75 in main () #4 0x4005c9f1 in __libc_start_main () from /lib/libc.so.6 I have Kernel 2.4.19 installed, On Debian Cid, with newest stable i2c and lm_sensors stuff. I run RedHat Linux 8.0, vanilla kernel 2.4.18, I2C & lm_sensors versions 2.7.0, and KDE version 3.1.0. I have also noticed that KSysGuard (version 1.2.0) does NOT work with lm_sensors - I get the message "Connection to localhost has been lost". Also, starting ksysguardd causes a segmentation fault. This problem isn't directly related to the lmsensors library, but to the actual kernel modules - if you remove them from memory using rmmod KSysGuard works fine again. make same fixes like number 2&3. now ksysguard runns, but cannot open *.sgrd files. the diagrams page is simply build, but how can i create a new process table? I have the same problem. ksysguardd causes a segmentation fault right away and ksysguard errors out with "Connection lost to localhost". I have tried several times to remove the files in ~/.kde/apps/share and config, but to no avail. I also do not have lm_sensors installed on my system, so I do not believe that is the problem (or is there some other modules I need to unload). Are there any other known causes of this problem? I (from comment #8) found the cause of my problem. My laptop does stupid things with APM (I think it has something do with the BIOS, I'm sure I've heard of it other places). I removed the APM (and lm_sensors, just in case) from the list of sensors in /etc/ksysguarddrc and everything seems to work fine. This behaviour still seems like a bug to me . . . ksysguardd really should be robust enough to handle malfunctioning sensors. |