Bug 830046
Summary: | Mouse's battery taken as computer's battery | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mikel P. <mikeloco14> |
Component: | upower | Assignee: | Richard Hughes <hughsient> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | beland, dantti12, hughsient, ikke |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-20 20:22:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mikel P.
2012-06-08 04:52:30 UTC
It seems the problem went away. I updated some packages (among them was the kernel) but I didn't pay attention to it after I rebooted into the new kernel. Guessing it was fixed in kernel 3.4.0, I'd say it's fixed... no it's not: I get the very same on fedora 17 on my PC. I believe it's caused by incorrect polling of the apple bt keyboard and bt touchpad (tragic mackpad) mouse. It's trashing the logs with this: [349847.631435] power_supply hid-7C:C3:A1:XX:XX:XX-battery: driver failed to report `capacity' property: -5 [349877.481202] power_supply hid-7C:C3:A1:XX:XX:XX-battery: driver failed to report `capacity' property: -5 [349907.431923] power_supply hid-7C:C3:A1:XX:XX:XX-battery: driver failed to report `capacity' property: -5 upower-0.9.17-1.fc17.x86_64 kernel-3.6.2-4.fc17.x86_64 It seems there are several tickets open related to the same issue. At least: 812625, 830046, 845770, 806295, 863524 No kernel 3.4 can actually fix his problem, at that version was added an option to tell the battery is now a power supply. @Ilkka your problem is not correctly getting the battery status. This bug should be closed. *** This bug has been marked as a duplicate of bug 816775 *** |