Bug 11296 - Update request: lm_sensors 3.3.3
Summary: Update request: lm_sensors 3.3.3
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: High critical
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: mga2-64-ok mga2-32-ok
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2013-09-26 21:29 CEST by Thomas Backlund
Modified: 2013-10-05 20:00 CEST (History)
2 users (show)

See Also:
Source RPM: lm_sensors
CVE:
Status comment:

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

Description Thomas Backlund 2013-09-26 21:29:21 CEST 
Quoting http://lm-sensors.org/


September 5th, 2013:
Hardware breakage reported Over the past few months, we had several reports of sensors-detect causing serious trouble on recent hardware (most notably laptops.) We still don't know what exactly is happening, and while it might be reversible, we don't know how, so in practice this is equivalent to the hardware itself being broken. The symptoms are that the display starts misbehaving ( wrong resolution or  wrong gamma factor.) We have mitigated the risk by changing the default behavior of sensors-detect to no longer touch EDID EEPROMs and then to no longer probe graphics adapters at all unless the user asks for it. We urge maintainers to backport changesets r6040 and r6084 to all Linux distributions which are still shipping lm-sensors 3.3.2 or older. Versions 3.3.3 and newer are not affected.


mga3 has 3.3.3 and cauldron has 3.3.4 so they are ok.

So I've pushed lm_sensors 3.3.3 from mga3 to mga2 updates_testing to resolve the issue there too

Reproducible: 

Steps to Reproduce:
Comment 1 Thomas Backlund 2013-09-26 21:33:27 CEST 
i586:
lm_sensors-3.3.3-1.mga2.i586.rpm
liblm_sensors4-3.3.3-1.mga2.i586.rpm
liblm_sensors-devel-3.3.3-1.mga2.i586.rpm
liblm_sensors-static-devel-3.3.3-1.mga2.i586.rpm
lm_sensors-debug-3.3.3-1.mga2.i586.rpm

x86_64:
lm_sensors-3.3.3-1.mga2.x86_64.rpm
lib64lm_sensors4-3.3.3-1.mga2.x86_64.rpm
lib64lm_sensors-devel-3.3.3-1.mga2.x86_64.rpm
lib64lm_sensors-static-devel-3.3.3-1.mga2.x86_64.rpm
lm_sensors-debug-3.3.3-1.mga2.x86_64.rpm

srpm:
lm_sensors-3.3.3-1.mga2.src.rpm

Priority: Normal => High

Comment 2 Zoltan Balaton 2013-10-02 22:52:55 CEST 
Tested on mga2 x86_64 by updating lm_sensors from Testing repo and verifying that sensord and sensors still provide measurements. Everything seems to be working after update but I have no access to hardware affected by the original problem and did not try to rerun sensors_detect.

CC: (none) => balaton

Comment 3 claire robinson 2013-10-03 15:47:44 CEST 
Thankyou Zoltan!

Whiteboard: (none) => mga2-64-ok

Comment 4 claire robinson 2013-10-03 15:49:06 CEST 
Testing mga2 32, ancient hardware though so not able (or wanting) to reproduce.
Comment 5 claire robinson 2013-10-03 16:02:39 CEST 
Testing complete mga2 32. 

sensors-detect found no sensors but the scan had no ill effect.

Whiteboard: mga2-64-ok => mga2-64-ok mga2-32-ok

Comment 6 claire robinson 2013-10-03 16:30:53 CEST 
Validating. Advisory uploaded.

Could sysadmin please push from 2 core/updates_testing to updates

Thanks!

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 7 Thomas Backlund 2013-10-05 20:00:32 CEST 
Update pushed:
http://advisories.mageia.org/MGAA-2013-0117.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.