* tests/test_dbus.py: Don't call GTK from multiple processes. We started
seeing software-properties tests failing with fatal X errors after GTK
3.22.24 was uploaded. I think what happened was:
- the testsuite imports GTK (via GI)
- this import itself initialises GTK, retrieving the value of a load of
X atoms
- it forks to start software-properties-dbus in a separate process
- this process then accesses another X atom after we ask it to do stuff
- X doesn't like that and kills us
The testsuite is now rewritten to not fork. We start a separate *thread*
to run the D-Bus service in. A benefit of this is that we're more
asynchronous than we were before, so some of the tests are slightly
refactored to not run their own main loop but instead check that the
signal emission they're interested in has happened. (LP: #1721828)
-- Iain Lane <email address hidden> Tue, 17 Oct 2017 14:05:25 +0100
This bug was fixed in the package software-properties - 0.96.24.17
---------------
software-properties (0.96.24.17) artful; urgency=medium
* tests/test_dbus.py: Don't call GTK from multiple processes. We started properties- dbus in a separate process
seeing software-properties tests failing with fatal X errors after GTK
3.22.24 was uploaded. I think what happened was:
- the testsuite imports GTK (via GI)
- this import itself initialises GTK, retrieving the value of a load of
X atoms
- it forks to start software-
- this process then accesses another X atom after we ask it to do stuff
- X doesn't like that and kills us
The testsuite is now rewritten to not fork. We start a separate *thread*
to run the D-Bus service in. A benefit of this is that we're more
asynchronous than we were before, so some of the tests are slightly
refactored to not run their own main loop but instead check that the
signal emission they're interested in has happened. (LP: #1721828)
-- Iain Lane <email address hidden> Tue, 17 Oct 2017 14:05:25 +0100