Red Hat Bugzilla – Bug 848521
UPS handling seems broken in recent kernels (3.5+)
Last modified: 2013-01-22 20:28:03 EST
I have a UPS attached to my system, with apcupsd correctly configured and running. With F17, GNOME Shell saw the UPS - I had a battery icon with a charging indicator just like on my laptop, and I could click it and get some basic status info and set some preferences.
Since updating to F18, GNOME seems not to see the UPS at all any more. There is no such icon in the 'tray' and the 'Power' preferences window has nothing at all about my UPS (just a single option for inactive suspend timeout).
Moving to upower, which seems more likely.
[root@adam kernel (f18 *%)]# upower --enumerate
[root@adam kernel (f18 *%)]#
so yeah, that seems right. I'd expect that to print something if upower was seeing the UPS. It prints out a couple of things (one for AC, one for battery) on my laptop.
Also affects F17.
UPower client version 0.9.17
UPower daemon version 0.9.17
well, I explicitly said in my first comment that it *didn't* affect F17. this was working fine in F17 for me back then. of course, I don't know if it is with current F17 packages.
It /did/ work on F17 right before the kernel was updated to 3.6.x
I'm still investigating whether upower was updated around the same time.
Same here. I'm still on f17 and it crapped out with the 3.6.x kernels. Hasn't worked since kernel 3.5.x back in September. Kernel issue I believe.
seems we have a new suspect here. kernel folks, what can we get you that would help with this?
Since it may be important now we're down to this being a kernel issue, my UPS is a CyberPower 1500AVR.
Created attachment 644904 [details]
Paste of lsusb -v
Just snipet of my APC issue.
Not sure if it's part of the same problem, but I just had an outage here, and my desktop - F18 - restarted when the outage hit, but my VM host / server box - F17 - kept trucking. The vmhost is still booted on kernel 3.3.0-1. I'm a bit scared to reboot it now...
adjusting summary, this seems more general that GNOME.
FYI, none of the kernel updates to f18 over the several months have fixed the problem. Is anyone in dev looking at this?
I'm not interested in this bug anymore. Given up hope it will be addressed.
Work around, run NUT in fedora.... at least Nut Monitor is gui and works!
Committed upstream in upower:
Author: Peter Hurley <firstname.lastname@example.org>
Date: Sun Dec 23 15:45:01 2012 -0500
Fix device matching for recent kernels
In recent kernels, hiddev* devices now have class "usbmisc", rather
than "usb" (see http://www.spinics.net/lists/linux-usb/msg62276.html).
This change translates into a change in SUBSYSTEM matching for hiddev*
devices. This fix addresses this for recent kernels while retaining
Technically this is a kernel ABI break IMHO.
(In reply to comment #14)
> Committed upstream in upower:
> commit 9f31068707fc79744961cea7258b0eb262effbf1
> Author: Peter Hurley <email@example.com>
> Date: Sun Dec 23 15:45:01 2012 -0500
> Fix device matching for recent kernels
> In recent kernels, hiddev* devices now have class "usbmisc", rather
> than "usb" (see http://www.spinics.net/lists/linux-usb/msg62276.html).
> This change translates into a change in SUBSYSTEM matching for hiddev*
> devices. This fix addresses this for recent kernels while retaining
> existing behavior.
> Technically this is a kernel ABI break IMHO.
Will this fix make it into F17?
> Will this fix make it into F17?
Yes, I'm just prepping the update for F18 and F17.
upower-0.9.19-1.fc18 has been submitted as an update for Fedora 18.
upower-0.9.19-1.fc17 has been submitted as an update for Fedora 17.
(In reply to comment #16)
> > Will this fix make it into F17?
> Yes, I'm just prepping the update for F18 and F17.
(In reply to comment #18)
> upower-0.9.19-1.fc17 has been submitted as an update for Fedora 17.
Tested, fixes the long-standing bug. Many thanks for this.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing upower-0.9.19-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
"Technically this is a kernel ABI break IMHO."
Maybe you should let Linus know, so he can incinerate the unfortunate responsible party =)
*** Bug 871147 has been marked as a duplicate of this bug. ***
upower-0.9.19-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
upower-0.9.19-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.