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 Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1112907 Title: abort with wireless HID devices: A handler is already registered for <battery> Status in The Linux Kernel: Unknown Status in Upower: Unknown Status in “upower” package in Ubuntu: In Progress Bug description: . ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: upower 0.9.19-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-216.23-omap4 3.5.7.1 Uname: Linux 3.5.0-216-omap4 armv7l ApportVersion: 2.8-0ubuntu3 Architecture: armhf Date: Fri Feb 1 22:25:19 2013 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2013-01-17 (15 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha armhf+omap4 (20130116) MarkForUpload: True ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: Signal: 5 SourcePackage: upower StacktraceTop: dbus_g_connection_register_g_object () from /usr/lib/arm-linux-gnueabihf/libdbus-glib-1.so.2 ?? () ?? () Title: upowerd crashed with signal 5 in dbus_g_connection_register_g_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1112907/+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
