I made two patches which both address this problem. The first one is a direct workaround for this particular bluetooth HID issue where the kernel creates new native sysfs devices for those after each nap. This would even still be relevant if the kernel gets fixed to actually do send out remove events properly, as we don't really want upower to signal device removals/additions all the time.
Pro: unintrusive as it does not change behaviour for all other kinds of devices, suitable for a stable release update Con: rather hackish, and does not guard against similar problems with other device types ** Patch added: "patch V1: less intrusive, hackish" https://bugs.launchpad.net/upower/+bug/1112907/+attachment/3843896/+files/0001-linux-Work-around-unstable-sysfs-names-for-bluetooth.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1112907 Title: abort with wireless HID devices: A handler is already registered for <battery> To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1112907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
