~3v1n0/ubuntu/+source/glib2.0:ubuntu/bionic

Last commit made on 2018-08-28
Get this branch:
git clone -b ubuntu/bionic https://git.launchpad.net/~3v1n0/ubuntu/+source/glib2.0
Only Marco Trevisan (Treviño) can upload to this branch. If you are Marco Trevisan (Treviño) please log in for upload directions.

Branch merges

Branch information

Name:
ubuntu/bionic
Repository:
lp:~3v1n0/ubuntu/+source/glib2.0

Recent commits

798ceb2... by Marco Trevisan (Treviño)

Finalise changelog

0d906d1... by Marco Trevisan (Treviño)

debian/patches: rebase on new version

a0b4131... by Marco Trevisan (Treviño)

debian/changelog: new upstream release 2.56.2

b9f965f... by Marco Trevisan (Treviño)

Merge with 'upstream/2.56.2'

Upstream version 2.56.2

193ebc0... by Marco Trevisan (Treviño)

debian/{gbp,control}: update vcs references for bionic

Moved to ubuntu/bionic as cosmic is already on 2.57

9a88e65... by Simon McVittie

New upstream version 2.56.2

d4b6039... by Matthias Clasen <email address hidden>

2.56.2

d0f6a59... by Matthias Clasen <email address hidden>

network monitor portal: update properties initially

With version 2, we need to query the values explicitly.
The properties made this automatic.

7ddd1de... by Matthias Clasen <email address hidden>

network monitor: Update portal implementation

The network monitor portal interface is changing.
Version 2 is no longer using properties, but getters
instead (this lets the portal apply access control
and avoid sending information to non-networked
sandboxes).

To support both version 1 and 2 of the interface,
we stop using generated code and instead deal with
the api differences in our own code, which is not
too difficult.

Support version 1 as well

edcce31... by Milan Crha <email address hidden>

gnetworkmonitor: Fix use-after-free when using from another thread

When using g_network_monitor_get_default() from another thread, it’s
possible for network-changed events to be processed after an instance of
GNetworkMonitor has been disposed, causing use-after-free problems.

Fix that by moving some of the initialisation into the GInitable.init()
chain, rather than in a main context idle callback.

This includes a unit test which probabilistically reproduces the bug
(but can’t do so deterministically due to it being a race condition).

Commit amended by Philip Withnall <email address hidden> before
pushing.

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