Comment 27 for bug 1112907

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.