Bug 107709 - Crash KSim with lm_sensors versions 2.7.0, 2.8.0 and 2.8.1
Summary: Crash KSim with lm_sensors versions 2.7.0, 2.8.0 and 2.8.1
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kdeutils
Version: rawhide
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-22 12:13 UTC by McMCC
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-26 17:16:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Fix problem in KSim with the new version lm_sensors (2.7.0 and is higher) (295 bytes, patch)
2003-10-22 12:19 UTC, McMCC
no flags Details | Diff

Description McMCC 2003-10-22 12:13:17 UTC
Description of problem: 
At a choice of an option lm_sensors in customizations KSim, leads to crash KSim. 
At usage lm_sensors versions 2.6.5 KSim works normal. 
 
How reproducible: 
Crash occurs because of distinctions of structure sensors_chip_name between versions  
lm_sensors 2.6.5 and 2.7.0 (or is higher), the plug-in ksim_sensors from kdeutils-3.1.4 works  
only with lm_sensors versions 2.6.5. For that that ksim_sensors would work with versions  
lm_sensors 2.7.0 and is higher, it is necessary to place this patch: 
 
--- 2/ksim/monitors/lm_sensors/sensorbase.h.orig        2003-05-07 15:49:05.000000000 
+0400 
+++ 2/ksim/monitors/lm_sensors/sensorbase.h     2003-10-22 12:19:38.000000000 +0400 
@@ -121,6 +121,7 @@ 
       char *prefix; 
       int bus; 
       int addr; 
+      char *busname; 
     }; 
 
     struct FeatureData

Comment 1 McMCC 2003-10-22 12:19:29 UTC
Created attachment 95380 [details]
Fix problem in KSim with the new version lm_sensors (2.7.0 and is higher)

Comment 2 Than Ngo 2004-10-26 17:16:43 UTC
it's already fixed in KDE upstream (KDE-3.3.x), which will be included
in FC3


Note You need to log in before you can comment on or make changes to this bug.