Package: upower / 0.99.1-3.2

Metadata

Package Version Patches format
upower 0.99.1-3.2 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
git tests without session bus.patch | (download)

src/linux/integration-test | 5 4 + 1 - 0 !
1 file changed, 4 insertions(+), 1 deletion(-)

 [patch] linux integration tests: fix crash if there is no session
 D-BUS

This can happen in CI environments without a desktop session.

git tests py3.4.patch | (download)

src/linux/integration-test | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 [patch 1/2] linux integration tests: fix error handling for python
 3.4

Python 3.4 changed the TestCase._outcome semantics, adjust accordingly.

git split tests.patch | (download)

src/linux/integration-test | 70 51 + 19 - 0 !
1 file changed, 51 insertions(+), 19 deletions(-)

 [patch 2/2] linux integration tests: split big tests into several
 smaller ones

This is better design to catching regressions and problems in a more
pin-pointed fashion. This also avoids having to restart the umockdev testbed
due to changing the environment variables with stop/start_daemon().

git fix memleak.patch | (download)

src/up-daemon.c | 20 18 + 2 - 0 !
1 file changed, 18 insertions(+), 2 deletions(-)

 daemon: properly disconnect signals, stop memleak

Whenever the daemon is polling on a device, a new signal is connected to
the object. This signal was not disconnected when polling stops which
resulted in a memory leak. Furthermore, whenever the "warning-level"
property is updated, the signal would result in an exponentially raising
call count (this happens when the battery percentage changes for
example).

https://bugs.freedesktop.org/show_bug.cgi?id=82659

Reported-by: Alexander Jesner <alexander@jesner.eu>
Signed-off-by: Peter Wu <peter@lekensteyn.nl>

null init pointers.patch | (download)

libupower-glib/up-device.c | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 null-initialize two pointers, avoid crash