Hey Lee,
I got some sysfs/udev dumps from you and another reporter, from these I could
create an emulated mouse/keyboard in the test suite and reproduce the bug:
http://cgit.freedesktop.org/upower/commit/?id=09d41eb7
I committed your fix (which makes these new tests succeed) with a few minor
a
Hi,
On Tue, Sep 3, 2013 at 4:15 PM, Martin Pitt wrote:
> I would like to create a test case for this to verify the fix and
> ensure it stays working in the future. For this we need the sysfs
> contents for these devices. Do you have such a device? I asked for it
> in http://pad.lv/1153488, i. e.
Hey Shih-Yuan,
for the record, the Launchpad bugs have various upower --dump outputs
which are relevant for this:
http://pad.lv/1069075 attachment →
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1069075/+attachment/3405886/+files/UPowerDump.txt
http://pad.pv/1086746 (inli
From: "Shih-Yuan Lee (FourDollars)"
First, checking the device path. If it contains 'bluetooth', it is a bluetooth
devices. Second, checking if there is an input folder. If there is mouse
folder under the input folder, it is a mouse device. Otherwise, it is a
keyboard device.
---
src/linux/up-de
