That will make it easy to globally identify runs, which might come
in handy especially if we synchronize runs into a central database.

On Apple hardware the sysfs directory for the mains power supply
is called ADPx and not ACx.

https://bugzilla.gnome.org/show_bug.cgi?id=777149

Before trying to take the inhibitor lock via logind we should
check we actually have the logind connection, because we are not
failing in init() if we could not get the logind proxy.

We force stop the test runner, so the epilogue does not get played,
because it is very likely that the screen has already been locked by
gnome-shell and we would play the epilogue on the lock-screen.

This will stop the player and skip the playing of the epilogue; the
idea is to use this in emergency situations, e.g. when we are going
to sleep or really running out of battery soon.

We pre-create the logfile in order to trigger an fsync in the
g_file_set_contents call, which will do that on an atomic replace
but not for new files.

We will acquire a delay lock from logind, immediately write the
log file when we get the sleep notification, and the write it
again when we get the callback from the runner that the test has
stopped. This is also when we release the lock. Since we 'only'
acquire a delay lock, not a block lock, we might actually not
finish the test in time.

We use logind for the sleep signal, and stop the run. If the run
is in the 'running' phase we write the log to disk as well.

When running on Wayland (i.e. non-X11) the attempt to setup the
stop-shortcut, using X11 specific functions, will lead to a crash.
Therefore this disables the setup of the shortcut on non-X11.

https://bugzilla.gnome.org/show_bug.cgi?id=775996

The autogen.sh called autoconf and friends in the current working
directory and therfore couldn't find the neccessary files.
Additionally for the proper generation of gnome-battery-bench.c
we need to include the actual source dir as an source directory.

https://bugzilla.gnome.org/show_bug.cgi?id=775995

P = Integral from Q1 to Q2 of V(Q)dQ

Use:

 (V1 + V2)/2 * (Q2 - Q1)

as the trapezoid rule approximation of this instead of:

 V2 * Q2 - V1 * Q1

which doesn't have a clear meaning. If V is constant, both are
the same, but for example, if we had a capacitor with V(Q) = Q/C,
then the old expression would over-estimate by a factor of 2,
while the new expression is asymptotically right for small changes.

https://bugzilla.gnome.org/show_bug.cgi?id=747370

If there are multiple batteries, it's not possible to compute an
overall "voltage_now" for the system, so just ignore it.

https://bugzilla.gnome.org/show_bug.cgi?id=747370

On systems that report battery capacity in amps, not watts, we can
approximate the power used by looking at the reported battery voltage.

https://bugzilla.gnome.org/show_bug.cgi?id=747370

Setting the resize mode of a GtkWidget has pretty unpredictable and
bad effects. The resize mode of a GtkGrid had accidentally been changed,
causing margins to not work properly.

https://bugzilla.gnome.org/show_bug.cgi?id=747370

gnome-autogen.sh is being removed along with the rest of gnome-common.
Instead use boilerplate from https://wiki.gnome.org/Projects/GnomeCommon/Migration

Because the wrong field was checked, when battery levels were reported
in mAh not mWh, battery life computation was skipped entirely.

Fix from Ettl Martin

https://bugzilla.gnome.org/show_bug.cgi?id=743228

https://bugzilla.gnome.org/show_bug.cgi?id=743728

die() should be called with a format string, not a variable string.

Roughly correspond to the current GNOME release.

X button 5 (down) corresponds to an evdev "value" of -1. Fix in the
record code and in the existing tests.

If we can't open /dev/uinput, store a reason in a GError, and pass
that back over D-Bus to the client.

This prevents mysterious problems where, if /dev/uinput doesn't exist,
the helper simply exits on CreatePlayer.

The conditional check for asciidoc wasn't working correctly - it was not
set correctly and the conditional was actually used in doc/Makefile.am.