Thanks for the two monitor logs. They indeed seem to confirm my
suspicion: The device bluetooth mouse battery gets add/change events
several times, but it never gets a remove event. On top of that, the add
events have different device paths, which causes the already existing
"treat add event as change" check to not work.That's a kernel bug, but
we need to make upower more robust against that.
Thanks to the logs I was able to complete my test case which now nicely
reproduces this crash.
** Changed in: upower (Ubuntu)
Status: Incomplete => In Progress
** Changed in: upower (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: upower (Ubuntu)
Milestone: None => ubuntu-13.09
--
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/upower/+bug/1112907/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
