GDBusWorker: if a read was cancelled it means we closed the connection
authorSimon McVittie <simon.mcvittie@collabora.co.uk>
Wed, 19 Oct 2011 09:49:56 +0000 (10:49 +0100)
committerSimon McVittie <simon.mcvittie@collabora.co.uk>
Wed, 19 Oct 2011 09:49:56 +0000 (10:49 +0100)
commit5e0492da509aad12b93b732c449dae1a016367c1
treebcbb8b67216872b306aad46df6bd557797ba0f53
parent6c33e1cd9d9e247b8b2aa95e9617904a317b78c6
GDBusWorker: if a read was cancelled it means we closed the connection

This was a regression caused by my previous work on GDBusWorker thread-safety
(Bug #651268). The symptom is that if you disconnect a GDBusConnection
locally, the default implementation of GDBusConnection::closed
terminates your process, even though it shouldn't do that for
locally-closed connections; this is because GDBusWorker didn't think a
cancelled read was a local close.

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=662100
Bug-NB: NB#287088
Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Reviewed-by: David Zeuthen <davidz@redhat.com>
gio/gdbusprivate.c