Launchpad has imported 6 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=60827.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-02-14T08:55:54+00:00 Martin Pitt wrote: http://cgit.freedesktop.org/upower/commit/?id=95184593504bca5240ecd29 introduced support for Logitech unifying devices. However, with 0.9.19 their charge is shown as 0%: Device: /org/freedesktop/UPower/devices/mouse_input5 native-path: /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/input/input5 vendor: Logitech power supply: no updated: Thu Feb 14 03:54:12 2013 (34 seconds ago) has history: yes has statistics: no mouse present: yes rechargeable: yes state: discharging percentage: 0% Device: /org/freedesktop/UPower/devices/keyboard_input6 native-path: /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/input/input6 vendor: Logitech power supply: no updated: Thu Feb 14 03:54:12 2013 (34 seconds ago) has history: yes has statistics: no keyboard present: no rechargeable: yes state: unknown percentage: 0% This leads to confusing output in both gnome-power-statistics (https://launchpadlibrarian.net/129122895/power-settings-window.png) as well as indicators (https://launchpadlibrarian.net/129122931/indicators.png). I think as a defensive action we should not add a "percentage" property if we are unable to read the actual charge, i. e. if it is 0. Ideally we'd fix reading the charge, of course. Reply at: https://bugs.launchpad.net/ubuntu/+source/indicator- power/+bug/1103064/comments/20 ------------------------------------------------------------------------ On 2013-02-14T09:02:34+00:00 Julien Danjou wrote: That doesn't sound complicated to fix, though I'm not sure what's the best strategy in term of UPower handling of that case. Richard, do you have any hint, or you're comfortable enough to fix it? I can test a patch if you don't have the hardware. Reply at: https://bugs.launchpad.net/ubuntu/+source/indicator- power/+bug/1103064/comments/21 ------------------------------------------------------------------------ On 2013-02-14T09:16:13+00:00 Martin Pitt wrote: I'm now at a machine which has these devices attached. I can reproduce the bug with 0.9.19, but interestingly with git head I don't see the devices at all any more. There might be some regression in http://cgit.freedesktop.org/upower/commit/?id=b1f12feb1fd45, did you or Julien happen to try current master with such a device? The udev rule seems to work somewhat; it attaches the property to the USB HID device (not the input device); I assume that's intended? P: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/0003:046D:C52B.0005 E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/0003:046D:C5 2B.0005 E: DRIVER=logitech-djdevice E: HID_ID=0003:0000046D:0000C52B E: HID_NAME=Logitech Unifying Device. Wireless PID:1024 E: HID_PHYS=usb-0000:00:1a.0-1.5.1:1 E: MODALIAS=hid:b0003g0000v0000046Dp0000C52B E: SUBSYSTEM=hid E: UDEV_LOG=3 E: UPOWER_BATTERY_TYPE=unifying E: USEC_INITIALIZED=47249781752 P: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/0003:046D:C52B.0006 E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/0003:046D:C5 2B.0006 E: DRIVER=logitech-djdevice E: HID_ID=0003:0000046D:0000C52B E: HID_NAME=Logitech Unifying Device. Wireless PID:2011 E: HID_PHYS=usb-0000:00:1a.0-1.5.1:2 E: MODALIAS=hid:b0003g0000v0000046Dp0000C52B E: SUBSYSTEM=hid E: UDEV_LOG=3 E: UPOWER_BATTERY_TYPE=unifying E: USEC_INITIALIZED=47249782421 With that, the debugging output is TI:04:15:59 registering subsystem : hid TI:04:15:59 failed to coldplug /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.3/0003:046D:0A29.0001 TI:04:15:59 failed to coldplug /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.0/0003:046D:C52B.0002 TI:04:15:59 failed to coldplug /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.1/0003:046D:C52B.0003 TI:04:15:59 failed to coldplug /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004 TI:04:15:59 Using Unifying receiver hidraw device file: /dev/hidraw1 TI:04:15:59 Getting idx for feature GetDeviceNameType [05] TI:04:15:59 Failed to get feature idx: invalid response from device: 7 TI:04:15:59 Getting idx for feature BatteryLevelStatus [1000] TI:04:15:59 Failed to get feature idx: invalid response from device: 7 TI:04:15:59 Getting idx for feature SolarDashboard [4301] TI:04:15:59 Failed to get feature idx: invalid response from device: 7 TI:04:15:59 failed to coldplug unifying device: device is unreachable TI:04:15:59 failed to coldplug /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/0003:046D:C52B.0005 TI:04:15:59 Using Unifying receiver hidraw device file: /dev/hidraw1 TI:04:15:59 Getting idx for feature GetDeviceNameType [05] TI:04:15:59 Failed to get feature idx: invalid response from device: 7 TI:04:15:59 Getting idx for feature BatteryLevelStatus [1000] TI:04:15:59 Failed to get feature idx: invalid response from device: 7 TI:04:15:59 Getting idx for feature SolarDashboard [4301] TI:04:15:59 Failed to get feature idx: invalid response from device: 7 TI:04:15:59 failed to coldplug unifying device: device is unreachable TI:04:15:59 failed to coldplug /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/0003:046D:C52B.0006 Reply at: https://bugs.launchpad.net/ubuntu/+source/indicator- power/+bug/1103064/comments/22 ------------------------------------------------------------------------ On 2013-02-14T09:17:17+00:00 Martin Pitt wrote: Julien, FTR, I'm "pitti" on Freenode (hanging out in e. g. #udev) if you want to discuss/debug on IRC. Reply at: https://bugs.launchpad.net/ubuntu/+source/indicator- power/+bug/1103064/comments/23 ------------------------------------------------------------------------ On 2013-02-14T09:21:54+00:00 Martin Pitt wrote: On 0.9.19, the debug output is TI:04:19:37 invalid bitmask entry for /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/ 1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/input/input5 TI:04:19:37 Using Unifying receiver hidraw device file: /dev/hidraw1 TI:04:19:37 object path = /org/freedesktop/UPower/devices/mouse_input5 TI:04:19:37 Unifying device 1 is offline TI:04:19:37 added native-path: /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/input/input5 TI:04:19:37 using id: Logitech [...] TI:04:19:37 invalid bitmask entry for /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/input/input6 TI:04:19:37 Using Unifying receiver hidraw device file: /dev/hidraw1 TI:04:19:37 object path = /org/freedesktop/UPower/devices/keyboard_input6 TI:04:19:37 Unifying device 2 is offline TI:04:19:37 added native-path: /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.2/0003:046D:C52B.0004/input/input6 TI:04:19:37 using id: Logitech The "invalid bitmask" might be related to http://cgit.freedesktop.org/upower/commit/?id=35b0d25 ? Reply at: https://bugs.launchpad.net/ubuntu/+source/indicator- power/+bug/1103064/comments/24 ------------------------------------------------------------------------ On 2013-02-14T09:24:58+00:00 Martin Pitt wrote: With git reset to commit 35b0d25 I basically get the same output as with 0.9.19, so the "invalid bitmask" still remains with 35b0d25. Reply at: https://bugs.launchpad.net/ubuntu/+source/indicator- power/+bug/1103064/comments/25 ** Changed in: upower Status: Unknown => Confirmed ** Changed in: upower Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1103064 Title: power indicator shows Logitech wireless keyboard and mouse batteries with 0% Status in The Power Indicator: Invalid Status in Upower: Confirmed Status in “indicator-power” package in Ubuntu: Invalid Status in “upower” package in Ubuntu: In Progress Status in “indicator-power” source package in Raring: Invalid Status in “upower” source package in Raring: In Progress Bug description: I updated by raring installation and found that the power indicator now shows my wireless keyboard and mouse as (missing) and with extremely low power. Both the keyboard and mouse work (I'm using them to type this bug) and the low battery light on the respective devices do not show low power. Even switching to brand new batteries don't make the indicator change state. I've attached a screenshot of the indicator and a screen shot of the power setting dialog which seems to be in conflict with the indicator. I've reproduced this behavior with the 3.8.0-0-generic & vmlinuz-3.8.0-1-generic kernels. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily13.01.18-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Tue Jan 22 11:39:23 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: Upgraded to raring on 2013-01-18 (3 days ago) --- ApportVersion: 2.8-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: upower 0.9.19-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Tags: raring running-unity Uname: Linux 3.8.0-1-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-01-18 (4 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1103064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
