powerd crashed with SIGABRT in ua_sensors_proximity_new()

[Karma Dorje]

 This is an automated report, after reinstalling this package I get the same effect.

lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04

apt-cache policy powerd
powerd:
  Installed: 0.16+15.04.20150116-0ubuntu1
  Candidate: 0.16+15.04.20150116-0ubuntu1
  Version table:
 *** 0.16+15.04.20150116-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ vivid-proposed/universe amd64 Packages
        100 /var/lib/dpkg/status
     0.16+15.04.20141031.2-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
     0.16+14.10.20141007-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: powerd 0.16+15.04.20150116-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic x86_64
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
Date: Sat Jan 17 00:07:41 2015
ExecutablePath: /usr/bin/powerd
InstallationDate: Installed on 2014-05-29 (231 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: /usr/bin/powerd
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
Signal: 6
SourcePackage: powerd
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
 ua_sensors_proximity_new () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
 powerd_sensors_init() ()
 main ()
Title: powerd crashed with SIGABRT in ua_sensors_proximity_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1351314, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.