Description of problem: Mageia 3 and KDE on a MacBook Pro (2009 model) fully updated. Battery is fine when using OSX. When using Mageia, battery indicator will randomly plunge to a single digit percentage throwing the system into hibernation. Current way of getting around this is closing the laptop lid (putting the OS to sleep) and then reopen the laptop. After this, the battery indicator shows the right value for the battery.This appears to be related to upower as discussed here: https://bugs.kde.org/show_bug.cgi?id=318868. Version-Release number of selected component (if applicable): upower 0.9.15-2.mga2 How reproducible: problem occurs randomly Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
This is the commit that fixed it in upower: http://cgit.freedesktop.org/upower/commit/?id=07b95b8e27e7c488828c46a28df96f1c83b185c8
URL: https://bugs.kde.org/show_bug.cgi?id=318868 => https://bugs.freedesktop.org/show_bug.cgi?id=60214CC: (none) => doktor5000
CC: (none) => luigiwalser
(In reply to steve daniewicz from comment #0) > Description of problem: > Mageia 3 and KDE on a MacBook Pro (2009 model) fully updated. [...] > Version-Release number of selected component (if applicable): > upower 0.9.15-2.mga2 Uhmm, something's wrong here. The package version is from Mageia 2, Mageia 3 has 0.9.19-3.mga3 but you mention Mageia 3 fully updated ... ? Can you please clarify? I'ved added a patch for Mageia 3 in svn, but this will not be fixed for Mageia 2 as it's already EOL.
Keywords: (none) => PATCHStatus: NEW => ASSIGNEDAssignee: bugsquad => doktor5000
Got confirmation from reporter via mail that it's about upower-0.9.19-3.mga3.src.rpm. I've submitted upower-0.9.19-3.1.mga3 and sent this to updates_testing, it should appear on your mirror soon. Suggested advisory: I have uploaded a patched/updated package for Mageia 3. You can test this by installing upower and checking that energy management still works as before, and the reported problems from https://bugs.kde.org/show_bug.cgi?id=318868 and https://bugs.freedesktop.org/show_bug.cgi?id=60214 do not occur anymore. (This can probably only be tested by the reporter) Suggested advisory: ======================== Updated upower package fixes battery state of batteries which report capacity, but not energy/charge information correctly. ======================== Updated packages in core/updates_testing: ======================== lib(64)upower-gir1.0-0.9.19-3.mga3.x86_64.rpm lib(64)upower-glib-devel-0.9.19-3.mga3.x86_64.rpm lib(64)upower-glib1-0.9.19-3.mga3.x86_64.rpm upower-0.9.19-3.mga3.x86_64.rpm Source RPMs: upower-0.9.19-3.1.mga3.src.rpm
Keywords: PATCH => (none)Assignee: doktor5000 => qa-bugsSource RPM: upower 0.9.15-2.mga2 => upower-0.9.19-3.mga3.src.rpm
I will looking for the update in the mirrors. Thanks. (In reply to Florian Hubold from comment #3) > Got confirmation from reporter via mail that it's about > upower-0.9.19-3.mga3.src.rpm. > > I've submitted upower-0.9.19-3.1.mga3 and sent this to updates_testing, it > should appear on your mirror soon. > > > > Suggested advisory: > > > I have uploaded a patched/updated package for Mageia 3. > > You can test this by installing upower and checking that energy management > still works as before, and the reported problems from > https://bugs.kde.org/show_bug.cgi?id=318868 and > https://bugs.freedesktop.org/show_bug.cgi?id=60214 do not occur anymore. > > (This can probably only be tested by the reporter) > > > Suggested advisory: > ======================== > > Updated upower package fixes battery state of batteries which report > capacity, but not energy/charge information correctly. > > ======================== > > Updated packages in core/updates_testing: > ======================== > lib(64)upower-gir1.0-0.9.19-3.mga3.x86_64.rpm > lib(64)upower-glib-devel-0.9.19-3.mga3.x86_64.rpm > lib(64)upower-glib1-0.9.19-3.mga3.x86_64.rpm > upower-0.9.19-3.mga3.x86_64.rpm > > Source RPMs: > upower-0.9.19-3.1.mga3.src.rpm
Hi steve, any progress regarding your tests?
CC: (none) => stormi
(In reply to Samuel VERSCHELDE from comment #5) > Hi steve, any progress regarding your tests? I have not seen the update in the mirrors yet.
(In reply to steve daniewicz from comment #6) > (In reply to Samuel VERSCHELDE from comment #5) > > Hi steve, any progress regarding your tests? > > I have not seen the update in the mirrors yet. Things propagate to the mirrors fairly quickly, but updates are not pushed to the updates media until they are tested, so this update candidate is currently in the updates_testing media, which is not enabled by default. See the wiki about this: https://wiki.mageia.org/en/Enabling_the_Testing_media
(In reply to David Walser from comment #7) > (In reply to steve daniewicz from comment #6) > > (In reply to Samuel VERSCHELDE from comment #5) > > > Hi steve, any progress regarding your tests? > > > > I have not seen the update in the mirrors yet. > > Things propagate to the mirrors fairly quickly, but updates are not pushed > to the updates media until they are tested, so this update candidate is > currently in the updates_testing media, which is not enabled by default. > See the wiki about this: > https://wiki.mageia.org/en/Enabling_the_Testing_media I have the following mirrors enabled and have not yet seen a upower update: core updates testing core backports testing Do I need to enable more?
Core updates_testing should be sufficient. The packages are there: http://mageia.c3sl.ufpr.br/distrib/3/i586/media/core/updates_testing/
On my system the core updates_testing is set to: http://mirrors.kernel.org/mageia/distrib/3/x86/media/core/updates_testing still no upower updates yet
The correct URLs are: http://mirrors.kernel.org/mageia/distrib/3/x86_64/media/core/updates_testing/ http://mirrors.kernel.org/mageia/distrib/3/i586/media/core/updates_testing/ and the upower packages are indeed there. mirrors.kernel.org is always one of the first to be up to date; it syncs every hour.
Since my link is slightly different than yours I deleted all of my media and reloaded. Each enabled URL is now listed as $MIRRORLIST. Hmmm... Mirror list Core Updates Testing (distrib5) is enabled but still no new updates listed as available.
Depending on the method you're using to install the packages, you may also need to mark the testing media as an "updates" source.
(In reply to David Walser from comment #13) > Depending on the method you're using to install the packages, you may also > need to mark the testing media as an "updates" source. I have resolved my mirror issues. I now have upower 0.9.19-3.1.mga3 and lib64upower-glib1 0.9.19-3.1.mga3 installed. I was unable to find a 3.1 version of lib64upower-gir1.0 and I am unable to install lib64upower-gir1.0 0.9.19-3.mga3. I will run the laptop hard for a few days and report back.
(In reply to steve daniewicz from comment #14) > I now have upower 0.9.19-3.1.mga3 and lib64upower-glib1 0.9.19-3.1.mga3 > installed. I was unable to find a 3.1 version of lib64upower-gir1.0 and I am > unable to install lib64upower-gir1.0 0.9.19-3.mga3. http://mirrors.kernel.org/mageia/distrib/3/x86_64/media/core/updates_testing/lib64upower-gir1.0-0.9.19-3.1.mga3.x86_64.rpm You might want to install it manually, just in case.
(In reply to David Walser from comment #15) > (In reply to steve daniewicz from comment #14) > > I now have upower 0.9.19-3.1.mga3 and lib64upower-glib1 0.9.19-3.1.mga3 > > installed. I was unable to find a 3.1 version of lib64upower-gir1.0 and I am > > unable to install lib64upower-gir1.0 0.9.19-3.mga3. > > http://mirrors.kernel.org/mageia/distrib/3/x86_64/media/core/updates_testing/ > lib64upower-gir1.0-0.9.19-3.1.mga3.x86_64.rpm > > You might want to install it manually, just in case. OK. Manual installation completed for lib64upower-gir1.0-0.9.19-3.1.mga3. Let the testing begin!
It has been several days and I am happy to report that I have had none of the power management issues originally reported. Before the upower update I could expect several (3-5) occurrences of the issue per day. The laptop has been working flawlessly. I want to thank all of you for the quick work on this bug report.
Steve, thanks for the report, and for your testing and feedback. Since the reporter has tested and reported the issue resolved, just basic testing on i586 should be enough to get this validated.
Whiteboard: (none) => MGA3-64-OK
Can this be pushed then as there seem to be no regressions for i586?
(In reply to Florian Hubold from comment #19) > Can this be pushed then as there seem to be no regressions for i586? Sure, we just need someone to do a quick test on i586. Unfortunately the QA policy is that the packager doesn't count as one of the testers, but hopefully someone else well get to this soon.
i586 ok. Update validated. Advisory uploaded. Please push to 3/core/updates.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugsWhiteboard: MGA3-64-OK => MGA3-64-OK MGA3-32-OK
Whiteboard: MGA3-64-OK MGA3-32-OK => MGA3-64-OK MGA3-32-OK advisory
Update pushed: http://advisories.mageia.org/MGAA-2014-0015.html
Status: ASSIGNED => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED