FS#39872 - [batti] Neither UPower nor DeviceKit.Power could be initialized

Attached to Project: Community Packages
Opened by Richard Schwab (Nothing4You) - Tuesday, 15 April 2014, 11:50 GMT
Last edited by Alexander F. Rødseth (xyproto) - Tuesday, 15 April 2014, 17:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jan de Groot (JGC)
Alexander F. Rødseth (xyproto)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Hi,

suddenly batti doesn't start anymore with the following error:

Neither UPower nor DeviceKit.Power could be initialized!
This can have multiple reasons.
Here is the error for UPower:

org.freedesktop.DBus.Error.InvalidArgs: No such property CanSuspend

And this is the error for DeviceKit.Power:

org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.DeviceKit.Power was not provided by any .service files

I updated a ton of packages today before rebooting (it already didn't show up after the reboot), pacman.log attached.


Additional info:
* package version(s): batti 0.3.8-3


Steps to reproduce:
`batti` in a terminal
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Tuesday, 15 April 2014, 17:46 GMT
Reason for closing:  Fixed
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 15 April 2014, 16:22 GMT
Hi,

Thanks for reporting.

I'm able to reproduce the problem on a computer without a battery (haven't tried on a laptop yet). I get the exact same error message.
Comment by Jan de Groot (JGC) - Tuesday, 15 April 2014, 16:58 GMT
This is because upower 0.99.x doesn't provide the deprecated interfaces anymore. Batti hasn't been maintained upstream since 2011, so I don't think there will be any official patch for this.
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 15 April 2014, 17:44 GMT
Balló György had a patch for this. Applying and pushing. The updated package should appear in [community] shortly.

Please re-open if this should still be a problem.
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 15 April 2014, 17:46 GMT
If there should be further problems with batti, and no further upstream development, moving it to AUR sound like a sensible "next action" to me.