diff options
| author | Philip Withnall <philip.withnall@collabora.co.uk> | 2013-11-15 11:27:23 +0000 |
|---|---|---|
| committer | Philip Withnall <philip@tecnocode.co.uk> | 2014-02-16 23:52:31 +0000 |
| commit | 0f398ab516bb662727242a753f7fd0ac4a6eb123 (patch) | |
| tree | 408528d0500b32c9cd01ca15691f2bfc40794004 | |
| parent | e054d029bec2af3f1e744cd407ea073df627fe32 (diff) | |
bluez: Correctly handle OBEX transfers which take zero time
If an OBEX transfer takes zero time (say, in an ideal world or, perhaps,
in a unit test) the transfer Status property will start out as
‘complete’ and never change. Previously, completed transfers were only
detected on receipt of a property change notification which, in this
situation, never came. Now, the initial value of the Status property is
also checked.
https://bugzilla.gnome.org/show_bug.cgi?id=712274
| -rw-r--r-- | backends/bluez/bluez-persona-store.vala | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/backends/bluez/bluez-persona-store.vala b/backends/bluez/bluez-persona-store.vala index 42a7fff6..af341afe 100644 --- a/backends/bluez/bluez-persona-store.vala +++ b/backends/bluez/bluez-persona-store.vala @@ -593,6 +593,10 @@ public class Folks.Backends.BlueZ.PersonaStore : Folks.PersonaStore ulong signal_id; ulong cancellable_id = 0; + /* Find the initial status, if it’s already been set. Otherwise it’ll + * be null. */ + transfer_status = transfer.status; + /* Set up the cancellable. */ if (cancellable != null) { |