It turns out that this was indeed a bug in upower and is resolved in arch linux package upower version 0.9.23-2
The upstream report for this is at https://bugs.freedesktop.org/show_bug.cgi?id=70952
So this I believe is now fully resolved with the latest upower version.
It turns out that this was indeed a bug in upower and is resolved in arch linux package upower version 0.9.23-2
The upstream report for this is at https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 70952
So this I believe is now fully resolved with the latest upower version.