This second version is a bolder step, but I think it's the right thing to do. It's a little more risky than the first one, but I (and the test suite) are fairly convinced that it's correct.
Pro: addresses this kind of problem for all device types under Linux, and avoids D-BUS signalling device removals/additions from upower where the device itself did not really go away, just the parental USB/bluetooth tree structure changed Con: More intrusive, could theoretically cause regressions (but I have no idea how, as upower already only uses the device name for building object names) Both patches have detailled commit messages which explain their rationale. @Richard: I recommend the second patch, but I posted both to get you a chance to compare. ** Patch added: "patch V2: generic solution" https://bugs.launchpad.net/upower/+bug/1112907/+attachment/3843905/+files/0001-linux-Track-power_supply-devices-by-name-only-instea.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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
