| Summary: | USB mouse suspends every two seconds when powertop package is installed | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | José Jorge <lists.jjorge> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | lists.jjorge, sysadmin-bugs, tmb |
| Version: | 6 | Keywords: | advisory, validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA6-64-OK MGA6-32-OK | ||
| Source RPM: | powertop | CVE: | |
| Status comment: | |||
|
Description
José Jorge
2018-06-05 15:09:19 CEST
Suggested advisory : When installed, powertop service autotunes the system at boot to get a very interesting maximum powersave. Unfortunately, the default suspend time for an USB mouse was too short with only 2 seconds. This update gives 180 seconds before one has to click to awake the mouse. This update also upgrades the tool to bugfix version 2.9 which brings better support for latest hardware. Ref: https://01.org/powertop/downloads/powertop-v2.9 Only RPM: powertop-2.9-2.mga6.*.[s]rpm CC:
(none) =>
lists.jjorge Not a good fix. The value for DELAY should not be hardcoded in a shell script. It should be defined in something like /etc/sysconfig/powertop and sourced from there so it's admin defineable without losing the config every time one updates powertop... and not everyone will be happy with 3 minutes either... So it can still default to 3 minutes but give final power to the admin CC:
(none) =>
tmb (In reply to Thomas Backlund from comment #2) > Not a good fix. You are right, done better in -4. Sot the version to test is : powertop-2.9-.mga6.*.[s]rpm Keywords:
feedback =>
(none) Tested by myself powertop-2.9-4.mga6.x86_64, and the script failed on some systems. So now version powertop-2.9-5 is pushed to testing. Whiteboard:
(none) =>
MGA6-64-OK MGA6-32-OK Validating from Jose's tests, just this once. Advisoried. Keywords:
(none) =>
advisory, validated_update An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2018-0121.html Status:
ASSIGNED =>
RESOLVED |