Comment 38 for bug 1546641

I sent patches to the upstream upower bug that improve the behaviour when connecting to upowerd on D-Bus fails. However, libupower already behaved in the current way forever, so this is nothing new in Xenial. Thus the patches will also only help so far: they should avoid the segfault, but you'll still get invalid data presented in the UI as the client/the library never reconnects to upowerd.

The root cause here is that upowerd takes very long to start as it gets blocked reading some kernel attributes. This needs to be fixed in the kernel to truly solve this bug.