There's always a typo: "pm-power" in my second paragraph above should of course read "pm-powersave".

We switched to systemd as of Mageia 2, but it took over pm stuff from pm-utils in Mageia 4.

CC: (none) => mageia

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Created attachment 7026 [details]
pm-powersave invocation workaround


Yes, in Mageia 5 the issue remains.

Apologies for never getting back with more info, but I found a simple workaround ages ago and completely forgot I reported this bug.

WORKAROUND: for each Power-State Tab in KDE System Settings > Power Management activate the Run Script check box; in the Script field add "pm-powersave"; and lastly set the Run Script drop down to "On Profile Load".

See also the my attached screen capture.

(In reply to John ten Wolde from comment #4)
> WORKAROUND: for each Power-State Tab in KDE System Settings > Power
> Management activate the Run Script check box; in the Script field add
> "pm-powersave"; and lastly set the Run Script drop down to "On Profile Load".

Thanks for your reply. I was also using this workaround for a while, now your information got to me. So I submitted a upower with deprecated config option to MGA5 testing.

Please test an report if this fixes to bug (of course you will have to disable the workaround).

Status: NEW => ASSIGNED

I could try this on a laptop, but it did not change the situation. But I have found what seems the real solution : a udev rule to trigger pm-powersave on power events.

The fix is commited in pm-utils-1.4.1-9.1.mga5. It worked for me, please test by yourself.

Suggested advisory:
========================

With systemd, the pm-powersave scripts were not launched anymore on laptops when ac-power starts and stops.

This updated pm-utils brings an udev rule to start powersave on battery, on stop it on AC.

========================

Updated packages in core/updates_testing:
========================
pm-utils-1.4.1-9.1.mga5.i586.rpm
pm-utils-devel-1.4.1-9.1.mga5.i586.rpm


Source RPMs: 
pm-utils-1.4.1-9.1.mga5.src.rpm


Sysadmins, please remove from updates testing upower related rpms :
- libupower-glib3-0.99.2-1.1.mga5.i586
- upower-0.99.2-1.1.mga5.i586
- lib64upower-glib-devel-0.99.2-1.1
- libupower-gir1.0-0.99.2-1.1

Assignee: lists.jjorge => qa-bugs
Source RPM: upower-0.9.23-1.1.mga4 => pm-utils

PROCEDURE  to test : use the command 

ls -l /var/log/pm*

to see at what time pm-powersave was launched. When you unplug the AC, this file should be changed, but it does not.
After installing the updated pm-utils, it will change.

CC: (none) => lists.jjorge

(In reply to José Jorge from comment #6)
> The fix is commited in pm-utils-1.4.1-9.1.mga5. It worked for me, please
> test by yourself.

Hi José.  OP here.  I just took your test package for a spin, and yes indeed it works for me too! Thank you!

You've also supported my personal experience that there's always a typo.  In your suggested advisory, last clause of the second paragraph, you wrote: "on stop it on AC".  I believe you meant: "and stop it on AC". ;-)

In any case, thank you again for looking into this matter and providing a more robust (and elegant) fix.  I've never been party to the finalization of a bug resolution before.  Should we mark this bug as resolved or wait for more confirmations?

@José: Sadly, I just just discovered something your fix doesn't address any better than my workaround.  When plugging in an external HDD, pm-powersave fails to fire automatically.

In the pre Mageia 4 days, at the time KDE's Plasma Notifier popped up (i.e. when the system detected a new device had been added) pm-powersave would set the new drive according to the active AC profile.  I'm not sure how it did it, but I'm sure that it did.  Over the last 2 years, even with my workaround, I've been hitting up pm-powersave via KRunner (ALT+F2) every time I plugged in an external HDD.

Here are the results of my test.  Note that I do my testing not by watching for changes to /var/log/pm, but as root using "hdparm -B /dev/sdx" where 'x' is whatever HDD I'm checking.

As expected, if I unplug the AC cord, your fix kicks in and pm-powersave fires (same as it did while logged into KDE with my workaround):

After first plugging it in, the external HDD starts at the default power save level:
# hdparm -B /dev/sdc

/dev/sdc:
 APM_level      = 128

After pulling the AC cord your script kicks the HDD down to aggressive power save:
# hdparm -B /dev/sdc

/dev/sdc:
 APM_level      = 1

Plugging the AC cord back in causes your script to kick the HDD up to full power:
# hdparm -B /dev/sdc

/dev/sdc:
 APM_level      = 254


Your fix is definitely a step forward, but if you could figure out what tripped pm-powersave to fire in the days prior to 2014 (without pulling out the AC cord), that would really be golden.

Thanks again for your efforts.

Grr!  I botched the last paragraph in Comment 10.  It should read:

Your fix is definitely a step forward, but if you could figure out what tripped pm-powersave to fire *upon device detection* in the days prior to 2014 (without pulling out the AC cord), that would really be golden.

Then again, maybe that counts as a whole separate bug... :-(

(In reply to John ten Wolde from comment #11)
Yes a trigger of pm-powersave (true or false?) when you plug an external drive is an unexpected behaviour, let's forget it.

About closing this bug, please indicate if you tested with 32 or 64 bits, then QA team will publish an advisory, and the bug will be closed when to update is pushed to core/updates.

(In reply to José Jorge from comment #12)
I wasn't saying that pm-powersave did trigger; I was suggesting that it *should* trigger.

Anyway, my tests were conducted on an x86_64 laptop.

Ok, tests are also good on another i586 laptop.

Whiteboard: (none) => has_procedure MGA5-32-OK MGA5-64-OK

Thanks to John & José for their tests. Validating, Advisory uploaded.

Keywords: (none) => validated_update
Whiteboard: has_procedure MGA5-32-OK MGA5-64-OK => has_procedure MGA5-32-OK MGA5-64-OK advisory
CC: (none) => lewyssmith, sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2016-0135.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED