It's either a bug in libimobiledevice, or our use of it. I cannot reproduce the problem locally, and the last bug dates back from 2012. As nothing changed on the UPower side, it's likely a problem lower down the stack.
It's either a bug in libimobiledevice, or our use of it. I cannot reproduce the problem locally, and the last bug dates back from 2012. As nothing changed on the UPower side, it's likely a problem lower down the stack.