Bug 134173 - Temperature actions written with wrong configuration variables in scheme config
Summary: Temperature actions written with wrong configuration variables in scheme config
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Alpha 3
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-17 13:38 UTC by Holger Macht
Modified: 2005-12-02 09:48 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Macht 2005-11-17 13:38:42 UTC 
When editing the default actions for "Overheat Temperature Action" and "Critical Temperature Action", the written config variables to a scheme config file (e.g. /etc/sysconfig/powersave/scheme_powersave) are wrong:

  THERMAL_CRITICAL=""
  THERMAL_HOT_ACTION=""

These must be (like in /etc/sysconfig/powersave/events)

  EVENT_TEMPERATURE_CRITICAL=""
  EVENT_TEMPERATURE_HOT=""

I don't know whether they were renamed some time ago or it never worked. But until know, nobody noticed ;-)
Comment 1 Jiri Srain 2005-12-02 09:48:24 UTC 
Fixed in SVN for 10.1.