See http://lists.freedesktop.org/archives/devkit-devel/2014-December/001653.html
for the list of changes (lots of memleaks fixed, update display device
when battery is removed, etc..)
xfce4-power-manager seems happy with it, upower -d reports correct
values, and gnome-power-statistics still display a nice graph.
Reminded by ajacoutot@
acpibat sensor reporting the 'design capacity' of the battery. Fixes a
wrong notification about having a broken battery in KDE4.
From Fabian Raetz, thanks!
there will be some fallout due to major API changes, but they will be dealt with
today as the offenders (gnome-related) will be updated.
ok landry@ (MAINTAINER), aja@
- use --enable-deprecated instead of passing -DENABLE_DEPRECATED via the
configure env, and add a comment explaining that it is about
deprecated featureset (the linux implem now uses logind APIs for
suspend/hibernate calls), nothing related to the G*DEPRECATED macros.
From ajacoutot@, also prodded by giovanni@ a while ago.
- backport upstream 7933b0e55234fca86809dad1dee53f0d8e2b96ec,
g_type_init() is deprecated with glib 2.36.
- use g_thread_try_new instead of deprecated g_thread_create (prodded by
ajacoutot@ too)
- include config.h in up-backend.h to reach ENABLE_DEPRECATED #define
The two last patches reported upstream in bug #70071
- Recognize a battery not being present (and reset various metrics accordingly)
- Recognize a fully charged battery
as discussed with and OK landry@ (MAINTAINER), aja@
The situation is this: even when we --disable-gtk-doc, if gtk-doc is
actually installed at configure stage, tools like gtkdoc-rebase will be
picked up and run during the install target. That is bad because the
gtk-doc package may have been removed by then, especially during dpb(1)
bulks (we explicitely disable support for it so why should it stay...).
So for now, let's add the following env to configure whenever we use
--disable-gtk-doc, until a bettersolution is found...
CONFIGURE_ENV +=ac_cv_path_GTKDOC_CHECK="" \
ac_cv_path_GTKDOC_REBASE="" \
ac_cv_path_GTKDOC_MKPDF=""
Note that now by default, upowerd will run apm -C when running
on battery and apm -A when on AC, this can be disabled by setting
RunPowersaveCommand to false in etc/UPower/UPower.conf.
ok ajacoutot@
- remove history dir patches merged upstream
- fix deps wrt gettext module, update plist accordingly
- fix rate value, was wrong since last commit to acpibat.c
ok ajacoutot@
- don't try to fetch from dev/apm if the fd isn't available yet (to be
discussed with upstream)
- use var/db/upower to store history files
Fixes graphs in gnome-power-statistics...
UPower is an abstraction for enumerating power devices, listening to
device events and querying history and statistics. Any application or
service on the system can access the org.freedesktop.UPower service
via the DBUS system message bus.
OpenBSD specific backend written by yours truly with help from upstream
developer. So far, battery levels and ac status works, using either apm
or acpibat/acpiac if available.
As a sidenote, if udev, udisks and friends were designed with the same
clear separation between os-specific and generic parts, porting to
'alternative OSes' would be much simpler. UPower is a nice example of
'how to design a portable service'.
with a patch for glib version check, tweaks and ok ajacoutot@
